Hi all
i was trying to install sentry on-premise on the first time
the only change i made is to add the company proxy to get out
got error Error: Configuration file does not exist. Use ‘sentry init’ to initialize the file.
the default configuration files are exist in sentry folder.
and when i try to run sentry.init - command not found
any idea?
errors in the log:
Reading state information…
Get:2 h ttp://deb.debian.org/debian buster/main amd64 lsb-base all 10.2019051400 [28.4 kB]
Get:2 h ttp://deb.debian.org/debian buster/main amd64 cron amd64 3.0pl1-134+deb10u1 [99.0 kB]
Suggested packages:
anacron logrotate checksecurity
Recommended packages:
exim4 | postfix | mail-transport-agent
The following NEW packages will be installed:
cron
Get:3 h ttp://deb.debian.org/debian buster/main amd64 cron amd64 3.0pl1-134+deb10u1 [99.0 kB]
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 95.4 kB of archives.
After this operation, 257 kB of additional disk space will be used.
Get:1 h ttp://deb.debian.org/debian stretch/main amd64 cron amd64 3.0pl1-128+deb9u1 [95.4 kB]
debconf: delaying package configuration, since apt-utils is not installed
debconf: delaying package configuration, since apt-utils is not installed
Fetched 115 kB in 0s (480 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sensible-utils.
Fetched 143 kB in 0s (512 kB/s)
(Reading database … 6849 files and directories currently installed.)
Preparing to unpack …/sensible-utils_0.0.12_all.deb …
Unpacking sensible-utils (0.0.12) …
Fetched 95.4 kB in 0s (2449 kB/s)
Selecting previously unselected package sensible-utils.
Selecting previously unselected package cron.
(Reading database … 11918 files and directories currently installed.)
Preparing to unpack …/sensible-utils_0.0.12_all.deb …
Unpacking sensible-utils (0.0.12) …
(Reading database … 6684 files and directories currently installed.)
Preparing to unpack …/cron_3.0pl1-128+deb9u1_amd64.deb …
Unpacking cron (3.0pl1-128+deb9u1) …
Selecting previously unselected package cron.
Preparing to unpack …/cron_3.0pl1-134+deb10u1_amd64.deb …
Unpacking cron (3.0pl1-134+deb10u1) …
Selecting previously unselected package lsb-base.
Preparing to unpack …/lsb-base_10.2019051400_all.deb …
Unpacking lsb-base (10.2019051400) …
Setting up cron (3.0pl1-128+deb9u1) …
Setting up sensible-utils (0.0.12) …
Setting up cron (3.0pl1-134+deb10u1) …
Selecting previously unselected package cron.
Preparing to unpack …/cron_3.0pl1-134+deb10u1_amd64.deb …
Unpacking cron (3.0pl1-134+deb10u1) …
Setting up lsb-base (10.2019051400) …
Setting up sensible-utils (0.0.12) …
Setting up cron (3.0pl1-134+deb10u1) …
Adding group crontab' (GID 101) ... Adding group crontab’ (GID 101) …
Done.
Done.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Adding group `crontab’ (GID 101) …
Done.
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Removing intermediate container 56395cd76052
—> f7e8e9ac3a8b
Step 7/8 : COPY entrypoint.sh /entrypoint.sh
Removing intermediate container b25c6b92b027
—> ddba3e65b2e2
Step 7/8 : COPY entrypoint.sh /entrypoint.sh
—> cecdb8c1bc76
Step 8/8 : ENTRYPOINT ["/entrypoint.sh"]
Removing intermediate container c455b360cb02
—> 515fe5946bee
Step 7/8 : COPY entrypoint.sh /entrypoint.sh
—> Running in f817f2d7859b
—> d52354b2896f
Step 8/8 : ENTRYPOINT ["/entrypoint.sh"]
Removing intermediate container f817f2d7859b
—> abb63b691ccf
Then
Bootstrapping Snuba…
Creating network “sentry_onpremise_default” with the default driver
Creating volume “sentry_onpremise_sentry-secrets” with default driver
Creating volume “sentry_onpremise_sentry-smtp” with default driver
Creating volume “sentry_onpremise_sentry-zookeeper-log” with default driver
Creating volume “sentry_onpremise_sentry-kafka-log” with default driver
Creating volume “sentry_onpremise_sentry-smtp-log” with default driver
Creating sentry_onpremise_zookeeper_1 …
Creating sentry_onpremise_clickhouse_1 …
Creating sentry_onpremise_redis_1 …
Creating sentry_onpremise_zookeeper_1 … done
Creating sentry_onpremise_kafka_1 …
Creating sentry_onpremise_redis_1 … done
Creating sentry_onpremise_clickhouse_1 … done
Creating sentry_onpremise_kafka_1 … done
`+ ‘[’ b = - ‘]’
- snuba bootstrap --help
- set – snuba bootstrap --force
- set gosu snuba snuba bootstrap --force
- exec gosu snuba snuba bootstrap --force
2020-03-30 13:59:49,068 Connection to Kafka failed (attempt 0)
Traceback (most recent call last):
File “/usr/src/snuba/snuba/cli/bootstrap.py”, line 55, in bootstrap
client.list_topics(timeout=1)
cimpl.KafkaException: KafkaError{code=_TRANSPORT,val=-195,str=“Failed to get metadata: Local: Broker transport failure”}
Finally
Setting up database…
Creating sentry_onpremise_smtp_1 …
Starting sentry_onpremise_redis_1 …
Starting sentry_onpremise_redis_1 … done
Creating sentry_onpremise_postgres_1 …
Creating sentry_onpremise_memcached_1 …
Starting sentry_onpremise_clickhouse_1 …
Starting sentry_onpremise_clickhouse_1 … done
Creating sentry_onpremise_symbolicator_1 …
Starting sentry_onpremise_zookeeper_1 …
Starting sentry_onpremise_zookeeper_1 … done
Starting sentry_onpremise_kafka_1 …
Starting sentry_onpremise_kafka_1 … done
Creating sentry_onpremise_snuba-api_1 …
Creating sentry_onpremise_snuba-consumer_1 …
Creating sentry_onpremise_snuba-replacer_1 …
Creating sentry_onpremise_snuba-api_1 … done
Creating sentry_onpremise_memcached_1 … done
Creating sentry_onpremise_snuba-replacer_1 … done
Creating sentry_onpremise_postgres_1 … done
Creating sentry_onpremise_snuba-consumer_1 … done
Creating sentry_onpremise_symbolicator_1 … done
Creating sentry_onpremise_smtp_1 … done
Error: Configuration file does not exist. Use ‘sentry init’ to initialize the file.