Initial Sentry fails at the beginning

On-Premise
1

Hi, I’ve downloaded the official installation from github and I run the install.sh but I get this error somewhere in the middle of the process and it crashes here:

▶ Bootstrapping and migrating Snuba ...
Creating sentry_onpremise_zookeeper_1 ... 
Creating sentry_onpremise_clickhouse_1 ... 
Creating sentry_onpremise_redis_1      ... 
Creating sentry_onpremise_zookeeper_1  ... done
Creating sentry_onpremise_redis_1      ... done
Creating sentry_onpremise_clickhouse_1 ... done
Creating sentry_onpremise_kafka_1      ... 
Creating sentry_onpremise_kafka_1      ... done
Creating sentry_onpremise_snuba-api_run ... 
Creating sentry_onpremise_snuba-api_run ... done
"-":2: bad minute
errors in crontab file, can't install.
no crontab for root

I did not change anything at docker-compose.yml or install directory.
What is that all about ?
Thank you

2

Can you share your Docker version? Also what operating system are you on?

3

@BYK
Docker version 19.03.13
docker-compose version 1.29.2
CentOS Linux release 7.8.2003 (Core)
I’ve noticed there is a cron directory in git repo that inside that directory there is a Dockerfile but it can’t build on CentOS, So I’ve build the required images on Ubuntu 20 and copied them on CentOS machine. I guess it’s about CentOS, as far as I remember Sentry is pretty much fine with Ubuntu, isn’t it ?!!

4

@BYK
it’s silly but after spending a lot of searching I’ve changed the official entrypoint.sh to this and now it’s working:

#!/usr/bin/env bash
if [ "$(ls -A /usr/local/share/ca-certificates/)" ]; then
  update-ca-certificates
fi
declare -p | grep -Ev 'BASHOPTS|BASH_VERSINFO|EUID|PPID|SHELLOPTS|UID' > /container.env

SHELL=/bin/bash
BASH_ENV=/container.env

{ for cron_job in "$@"; do echo ${cron_job} | crontab - ; done}

crontab -l
exec cron -f -l -L 15

I still don’t know what was the problem at the first place.

1 Like
5

May be you can propose that as a PR in the repo and we’ll see if it still works on Ubuntu (then we may incorporate your fix).

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.