Installation problems running the default install.sh script

Hello,

I’m trying to set up on-premise. After running the install.sh script and docker-compose up the relay process keeps on restarting. I figured out that the credentials.json file wasn’t generated during installation. The file only contains:

error: could not open config file (file /work/C:/Users/****/AppData/Local/Temp/config.yml)
caused by: No such file or directory (os error 2)

The installation log shows some Kafka errors and warnings. I’m not sure if they affect the relay process or can I ignore them?

Checking minimum requirements...

Creating volumes for persistent storage...
Created sentry-data.
Created sentry-postgres.
Created sentry-redis.
Created sentry-zookeeper.
Created sentry-kafka.
Created sentry-clickhouse.
Created sentry-symbolicator.

Creating sentry/sentry.conf.py...
Creating sentry/config.yml...
Creating sentry/requirements.txt...
Creating symbolicator/config.yml...
Creating relay/config.yml...

Generating secret key...
Secret key written to sentry/config.yml

Fetching and updating Docker images...

Some service image(s) must be built from source by running:
    docker-compose build ingest-consumer post-process-forwarder sentry-cleanup web snuba-cleanup worker cron symbolicator-cleanup
20.8.0: Pulling from getsentry/sentry
8d691f585fa8: Already exists
3fd6980f9df6: Already exists
c4f890363b98: Already exists
b8cfb9853b0a: Already exists
eb82833faede: Pulling fs layer
bb30ddde69f1: Pulling fs layer
190f2138791e: Pulling fs layer
bc183caa6183: Pulling fs layer
9a401e10f48e: Pulling fs layer
e085a6ea85c8: Pulling fs layer
241b6752556c: Pulling fs layer
f34865970a79: Pulling fs layer
61352381f344: Pulling fs layer
d5293b01c142: Pulling fs layer
f34865970a79: Waiting
61352381f344: Waiting
d5293b01c142: Waiting
9a401e10f48e: Waiting
241b6752556c: Waiting
e085a6ea85c8: Waiting
bc183caa6183: Waiting
190f2138791e: Verifying Checksum
190f2138791e: Download complete
bb30ddde69f1: Verifying Checksum
bb30ddde69f1: Download complete
eb82833faede: Download complete
eb82833faede: Pull complete
bb30ddde69f1: Pull complete
190f2138791e: Pull complete
9a401e10f48e: Verifying Checksum
9a401e10f48e: Download complete
241b6752556c: Verifying Checksum
241b6752556c: Download complete
f34865970a79: Verifying Checksum
f34865970a79: Download complete
61352381f344: Download complete
d5293b01c142: Verifying Checksum
d5293b01c142: Download complete
e085a6ea85c8: Verifying Checksum
e085a6ea85c8: Download complete
bc183caa6183: Verifying Checksum
bc183caa6183: Download complete
bc183caa6183: Pull complete
9a401e10f48e: Pull complete
e085a6ea85c8: Pull complete
241b6752556c: Pull complete
f34865970a79: Pull complete
61352381f344: Pull complete
d5293b01c142: Pull complete
Digest: sha256:f425037c32492dbf31a52bd9c00e597b7fe6a085509095d0272d5e3c50b2f474
Status: Downloaded newer image for getsentry/sentry:20.8.0
docker.io/getsentry/sentry:20.8.0

Building and tagging Docker images...

    Building web
    Step 1/4 : ARG SENTRY_IMAGE
    Step 2/4 : FROM ${SENTRY_IMAGE}
     ---> 61c52fc84ac9
    Step 3/4 : COPY . /usr/src/sentry
 ---> 2bed800f1aa1
Step 4/4 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
 ---> Running in 031f65e54688
e[91m/usr/local/lib/python2.7/site-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
e[0me[91mDEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
e[0mRemoving intermediate container 031f65e54688
 ---> dccbbecd41fc

Successfully built dccbbecd41fc
Successfully tagged sentry-onpremise-local:latest
smtp uses an image, skipping
memcached uses an image, skipping
redis uses an image, skipping
postgres uses an image, skipping
zookeeper uses an image, skipping
kafka uses an image, skipping
clickhouse uses an image, skipping
snuba-api uses an image, skipping
snuba-consumer uses an image, skipping
snuba-outcomes-consumer uses an image, skipping
snuba-sessions-consumer uses an image, skipping
snuba-transactions-consumer uses an image, skipping
snuba-replacer uses an image, skipping
symbolicator uses an image, skipping
relay uses an image, skipping
nginx uses an image, skipping
Building snuba-cleanup          ... 

Building symbolicator-cleanup   ... 

Building web                    ... 

Building cron                   ... 

Building worker                 ... 

Building ingest-consumer        ... 

Building post-process-forwarder ... 

Building sentry-cleanup         ... 

Building snuba-cleanup
Building web
Building post-process-forwarder
Building worker
Building symbolicator-cleanup
Step 1/5 : ARG BASE_IMAGE
Step 2/5 : FROM ${BASE_IMAGE}
 ---> 64aba5c1f3ea
Step 3/5 : RUN apt-get update && apt-get install -y --no-install-recommends cron &&     rm -r /var/lib/apt/lists/*
Step 1/4 : ARG SENTRY_IMAGE
Step 2/4 : FROM ${SENTRY_IMAGE}
 ---> 61c52fc84ac9
Step 3/4 : COPY . /usr/src/sentry
 ---> Using cache
 ---> 2bed800f1aa1
Step 4/4 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
 ---> Using cache
 ---> dccbbecd41fc

Successfully built dccbbecd41fc
Step 1/4 : ARG SENTRY_IMAGE
Step 2/4 : FROM ${SENTRY_IMAGE}
Step 1/5 : ARG BASE_IMAGE
Step 2/5 : FROM ${BASE_IMAGE}
Step 1/4 : ARG SENTRY_IMAGE
Step 2/4 : FROM ${SENTRY_IMAGE}
 ---> 61c52fc84ac9
 ---> 830bb6024b62
Step 3/4 : COPY . /usr/src/sentryStep 3/5 : RUN apt-get update && apt-get install -y --no-install-recommends cron &&     rm -r /var/lib/apt/lists/*

 ---> Using cache
 ---> 2bed800f1aa1
 ---> 61c52fc84ac9
Step 4/4 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fiStep 3/4 : COPY . /usr/src/sentry

 ---> Using cache
 ---> 2bed800f1aa1
Step 4/4 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
 ---> Using cache
 ---> dccbbecd41fc

Successfully tagged sentry-onpremise-local:latest
 ---> Using cache
 ---> dccbbecd41fc

Successfully built dccbbecd41fc
Successfully built dccbbecd41fc
Building worker                 ... done

Building cron
Successfully tagged sentry-onpremise-local:latest
Building web                    ... done

Successfully tagged sentry-onpremise-local:latest
Building ingest-consumer
Building post-process-forwarder ... done

Building sentry-cleanup
 ---> Running in 7ed855e94d5d
 ---> Running in 77bdc9226f87
Step 1/4 : ARG SENTRY_IMAGE
Step 2/4 : FROM ${SENTRY_IMAGE}
 ---> 61c52fc84ac9
Step 3/4 : COPY . /usr/src/sentry
 ---> Using cache
 ---> 2bed800f1aa1
Step 4/4 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
 ---> Using cache
 ---> dccbbecd41fc

Successfully built dccbbecd41fc
Successfully tagged sentry-onpremise-local:latest
Building cron                   ... done

Step 1/4 : ARG SENTRY_IMAGE
Step 2/4 : FROM ${SENTRY_IMAGE}
 ---> 61c52fc84ac9
Step 3/4 : COPY . /usr/src/sentry
 ---> Using cache
 ---> 2bed800f1aa1
Step 4/4 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
 ---> Using cache
 ---> dccbbecd41fc

Successfully built dccbbecd41fc
Step 1/5 : ARG BASE_IMAGE
Step 2/5 : FROM ${BASE_IMAGE}
 ---> dccbbecd41fc
Step 3/5 : RUN apt-get update && apt-get install -y --no-install-recommends cron &&     rm -r /var/lib/apt/lists/*
Successfully tagged sentry-onpremise-local:latest
Building ingest-consumer        ... done

 ---> Running in 94b5c01ae192
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [53.0 kB]
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Get:3 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://deb.debian.org/debian stretch Release.gpg [2410 B]
Get:2 http://security.debian.org/debian-security buster/updates/main amd64 Packages [226 kB]
Get:6 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [564 kB]
Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [226 kB]
Get:7 http://deb.debian.org/debian stretch-updates/main amd64 Packages [2596 B]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7906 kB]
Get:8 http://deb.debian.org/debian stretch/main amd64 Packages [7080 kB]
Get:3 http://deb.debian.org/debian buster InRelease [122 kB]
Get:4 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [7868 B]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7906 kB]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [7868 B]
Fetched 7913 kB in 2s (3363 kB/s)
Reading package lists...Fetched 8379 kB in 2s (3491 kB/s)
Reading package lists...
Fetched 8379 kB in 3s (2758 kB/s)
Reading package lists...Reading package lists...
Reading package lists...

Building dependency tree...Reading package lists...
Reading state information...

Building dependency tree...Suggested packages:
  anacron logrotate checksecurity
Recommended packages:
  exim4 | postfix | mail-transport-agent
The following NEW packages will be installed:
  cron
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 http://deb.debian.org/debian stretch/main amd64 cron amd64 3.0pl1-128+deb9u1 [95.4 kB]

Reading state information...
The following additional packages will be installed:
  lsb-base sensible-utils
Suggested packages:
  anacron logrotate checksecurity
Recommended packages:
  default-mta | mail-transport-agent
e[91mdebconf: delaying package configuration, since apt-utils is not installed
e[0mThe following NEW packages will be installed:
  cron lsb-base sensible-utils
Fetched 95.4 kB in 0s (1088 kB/s)
Selecting previously unselected package cron.

(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
0 upgraded, 3 newly installed, 0 to remove and 16 not upgraded.
Need to get 143 kB of archives.
After this operation, 383 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 sensible-utils all 0.0.12 [15.8 kB]
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 6661 files and directories currently installed.)

Preparing to unpack .../cron_3.0pl1-128+deb9u1_amd64.deb ...

Unpacking cron (3.0pl1-128+deb9u1) ...

Get:2 http://deb.debian.org/debian buster/main amd64 lsb-base all 10.2019051400 [28.4 kB]
Get:3 http://deb.debian.org/debian buster/main amd64 cron amd64 3.0pl1-134+deb10u1 [99.0 kB]

Building dependency tree...Setting up cron (3.0pl1-128+deb9u1) ...

e[91mdebconf: delaying package configuration, since apt-utils is not installed
e[0m
Reading state information...
Fetched 143 kB in 0s (966 kB/s)
Selecting previously unselected package sensible-utils.

(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 11918 files and directories currently installed.)

Preparing to unpack .../sensible-utils_0.0.12_all.deb ...

Unpacking sensible-utils (0.0.12) ...

Adding group `crontab' (GID 101) ...

The following additional packages will be installed:
  sensible-utils
Suggested packages:
  anacron logrotate checksecurity
Recommended packages:
  default-mta | mail-transport-agent
Done.

Selecting previously unselected package lsb-base.

Preparing to unpack .../lsb-base_10.2019051400_all.deb ...

The following NEW packages will be installed:
  cron sensible-utils
Unpacking lsb-base (10.2019051400) ...

0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 115 kB of archives.
After this operation, 333 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 sensible-utils all 0.0.12 [15.8 kB]
Get:2 http://deb.debian.org/debian buster/main amd64 cron amd64 3.0pl1-134+deb10u1 [99.0 kB]
Selecting previously unselected package cron.

Preparing to unpack .../cron_3.0pl1-134+deb10u1_amd64.deb ...

Unpacking cron (3.0pl1-134+deb10u1) ...

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.

Setting up lsb-base (10.2019051400) ...

e[91mdebconf: delaying package configuration, since apt-utils is not installed
e[0mFetched 115 kB in 0s (903 kB/s)
Setting up sensible-utils (0.0.12) ...

Selecting previously unselected package sensible-utils.

(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 6838 files and directories currently installed.)

Preparing to unpack .../sensible-utils_0.0.12_all.deb ...

Setting up cron (3.0pl1-134+deb10u1) ...

Unpacking sensible-utils (0.0.12) ...

Selecting previously unselected package cron.

Preparing to unpack .../cron_3.0pl1-134+deb10u1_amd64.deb ...

Unpacking cron (3.0pl1-134+deb10u1) ...

Adding group `crontab' (GID 101) ...

Removing intermediate container 77bdc9226f87
 ---> a9b61c9e05bc
Step 4/5 : COPY entrypoint.sh /entrypoint.sh
Done.

Setting up sensible-utils (0.0.12) ...

invoke-rc.d: could not determine current runlevel

invoke-rc.d: policy-rc.d denied execution of start.

Setting up cron (3.0pl1-134+deb10u1) ...

 ---> 7a3605b37b87
Step 5/5 : ENTRYPOINT ["/entrypoint.sh"]
 ---> Running in f277ba746a70
Adding group `crontab' (GID 101) ...

Done.

Removing intermediate container f277ba746a70
 ---> 4e9741ec263e

Successfully built 4e9741ec263e
invoke-rc.d: could not determine current runlevel

Successfully tagged symbolicator-cleanup-onpremise-local:latest
Building symbolicator-cleanup   ... done

invoke-rc.d: policy-rc.d denied execution of start.

Removing intermediate container 94b5c01ae192
 ---> 04db8d2db449
Step 4/5 : COPY entrypoint.sh /entrypoint.sh
 ---> c56bf5eaa91f
Step 5/5 : ENTRYPOINT ["/entrypoint.sh"]
 ---> Running in 4f932be67e1b
Removing intermediate container 7ed855e94d5d
 ---> a31e68ce96e1
Step 4/5 : COPY entrypoint.sh /entrypoint.sh
Removing intermediate container 4f932be67e1b
 ---> 819592f3f9ff

Successfully built 819592f3f9ff
Successfully tagged sentry-cleanup-onpremise-local:latest
Building sentry-cleanup         ... done

 ---> 9f6419e78709
Step 5/5 : ENTRYPOINT ["/entrypoint.sh"]
 ---> Running in 240f0429ac6d
Removing intermediate container 240f0429ac6d
 ---> dd183ba2fd81

Successfully built dd183ba2fd81
Successfully tagged snuba-cleanup-onpremise-local:latest
Building snuba-cleanup          ... done


Docker images built.
Removing network onpremise_default
Network onpremise_default not found.
Removing network sentry_onpremise_default
Network sentry_onpremise_default not found.
Creating network "sentry_onpremise_default" with the default driver
Creating sentry_onpremise_clickhouse_1 ... 

Creating sentry_onpremise_clickhouse_1 ... done

Bootstrapping and migrating Snuba...
Starting sentry_onpremise_clickhouse_1 ... 

Creating sentry_onpremise_zookeeper_1  ... 

Starting sentry_onpremise_clickhouse_1 ... done

Creating sentry_onpremise_redis_1      ... 

Creating sentry_onpremise_redis_1      ... done

Creating sentry_onpremise_zookeeper_1  ... done

Creating sentry_onpremise_kafka_1      ... 

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
%3|1599468711.196|FAIL|rdkafka#producer-1| [thrd:kafka:9092/bootstrap]: kafka:9092/bootstrap: Connect to ipv4#192.168.32.5:9092 failed: Connection refused (after 1ms in state CONNECT)
%3|1599468712.195|FAIL|rdkafka#producer-1| [thrd:kafka:9092/bootstrap]: kafka:9092/bootstrap: Connect to ipv4#192.168.32.5:9092 failed: Connection refused (after 0ms in state CONNECT, 1 identical error(s) suppressed)
2020-09-07 08:51:52,196 Connection to Kafka failed (attempt 0)
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 56, in bootstrap
    client.list_topics(timeout=1)
cimpl.KafkaException: KafkaError{code=_TRANSPORT,val=-195,str="Failed to get metadata: Local: Broker transport failure"}
%3|1599468713.199|FAIL|rdkafka#producer-2| [thrd:kafka:9092/bootstrap]: kafka:9092/bootstrap: Connect to ipv4#192.168.32.5:9092 failed: Connection refused (after 0ms in state CONNECT)
%3|1599468714.198|FAIL|rdkafka#producer-2| [thrd:kafka:9092/bootstrap]: kafka:9092/bootstrap: Connect to ipv4#192.168.32.5:9092 failed: Connection refused (after 0ms in state CONNECT, 1 identical error(s) suppressed)
2020-09-07 08:51:54,199 Connection to Kafka failed (attempt 1)
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 56, in bootstrap
    client.list_topics(timeout=1)
cimpl.KafkaException: KafkaError{code=_TRANSPORT,val=-195,str="Failed to get metadata: Local: Broker transport failure"}
%3|1599468715.202|FAIL|rdkafka#producer-3| [thrd:kafka:9092/bootstrap]: kafka:9092/bootstrap: Connect to ipv4#192.168.32.5:9092 failed: Connection refused (after 0ms in state CONNECT)
2020-09-07 08:51:56,202 Connection to Kafka failed (attempt 2)
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 56, in bootstrap
    client.list_topics(timeout=1)
cimpl.KafkaException: KafkaError{code=_TRANSPORT,val=-195,str="Failed to get metadata: Local: Broker transport failure"}
2020-09-07 08:51:57,314 Failed to create topic cdc
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 439, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'cdc' already exists."}
2020-09-07 08:51:57,315 Failed to create topic events
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'events' already exists."}
2020-09-07 08:51:57,315 Failed to create topic ingest-sessions
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'ingest-sessions' already exists."}
2020-09-07 08:51:57,315 Failed to create topic event-replacements
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'event-replacements' already exists."}
2020-09-07 08:51:57,316 Failed to create topic snuba-commit-log
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'snuba-commit-log' already exists."}
2020-09-07 08:51:57,316 Failed to create topic outcomes
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'outcomes' already exists."}
2020-09-07 08:51:57,316 Failed to create topic errors-replacements
Traceback (most recent call last):
  File "/usr/src/snuba/snuba/cli/bootstrap.py", line 92, in bootstrap
    future.result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/usr/local/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str="Topic 'errors-replacements' already exists."}
2020-09-07 08:51:57,332 Creating tables for storage events
2020-09-07 08:51:57,339 Migrating storage events
2020-09-07 08:51:57,364 Creating tables for storage errors
2020-09-07 08:51:57,369 Migrating storage errors
2020-09-07 08:51:57,389 Column 'http_method' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,389 Column 'http_referer' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,390 Creating tables for storage groupedmessages
2020-09-07 08:51:57,391 Migrating storage groupedmessages
2020-09-07 08:51:57,397 Creating tables for storage groupassignees
2020-09-07 08:51:57,399 Migrating storage groupassignees
2020-09-07 08:51:57,403 Creating tables for storage outcomes_raw
2020-09-07 08:51:57,406 Migrating storage outcomes_raw
2020-09-07 08:51:57,410 Column 'size' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,411 Creating tables for storage outcomes_hourly
2020-09-07 08:51:57,413 Migrating storage outcomes_hourly
2020-09-07 08:51:57,417 Creating tables for storage sessions_raw
2020-09-07 08:51:57,418 Migrating storage sessions_raw
2020-09-07 08:51:57,423 Creating tables for storage sessions_hourly
2020-09-07 08:51:57,425 Migrating storage sessions_hourly
2020-09-07 08:51:57,435 Creating tables for storage transactions
2020-09-07 08:51:57,438 Migrating storage transactions
2020-09-07 08:51:57,450 Column '_start_date' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,450 Column '_finish_date' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,450 Column 'http_method' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,450 Column 'http_referer' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,450 Column 'measurements.key' exists in local ClickHouse but not in schema!
2020-09-07 08:51:57,450 Column 'measurements.value' exists in local ClickHouse but not in schema!


Setting up database...
Starting sentry_onpremise_zookeeper_1 ... 

Starting sentry_onpremise_zookeeper_1 ... done

Creating sentry_onpremise_postgres_1  ... 

Creating sentry_onpremise_memcached_1 ... 

Starting sentry_onpremise_redis_1     ... 

Creating sentry_onpremise_symbolicator_1 ... 

Starting sentry_onpremise_redis_1        ... done

Starting sentry_onpremise_clickhouse_1   ... 

Starting sentry_onpremise_kafka_1        ... 

Starting sentry_onpremise_clickhouse_1   ... done

Starting sentry_onpremise_kafka_1        ... done

Creating sentry_onpremise_smtp_1         ... 

Creating sentry_onpremise_snuba-consumer_1 ... 

Creating sentry_onpremise_snuba-transactions-consumer_1 ... 

Creating sentry_onpremise_snuba-sessions-consumer_1     ... 

Creating sentry_onpremise_snuba-outcomes-consumer_1     ... 

Creating sentry_onpremise_snuba-replacer_1              ... 

Creating sentry_onpremise_snuba-api_1                   ... 

Creating sentry_onpremise_memcached_1                   ... done

Creating sentry_onpremise_symbolicator_1                ... done

Creating sentry_onpremise_postgres_1                    ... done

Creating sentry_onpremise_smtp_1                        ... done

Creating sentry_onpremise_snuba-transactions-consumer_1 ... done

Creating sentry_onpremise_snuba-consumer_1              ... done

Creating sentry_onpremise_snuba-outcomes-consumer_1     ... done

Creating sentry_onpremise_snuba-sessions-consumer_1     ... done

Creating sentry_onpremise_snuba-replacer_1              ... done

Creating sentry_onpremise_snuba-api_1                   ... done

08:52:06 [WARNING] sentry.utils.geo: settings.GEOIP_PATH_MMDB not configured.
/usr/local/lib/python2.7/site-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
08:52:11 [INFO] sentry.plugins.github: apps-not-configured
e[36;1mOperations to perform:e[0m
e[1m  Apply all migrations: e[0madmin, auth, contenttypes, jira_ac, nodestore, sentry, sessions, sites, social_auth
e[36;1mRunning migrations:e[0m
  No migrations to apply.
Creating missing DSNs
Correcting Group.num_comments counter

Generating Relay credentials...
An error occurred, caught SIGERR on line 286
Cleaning up...

Seems like you are using Windows. Are you running the script under WSL or git-bash or cygwin?

Yes, I’m using Windows. I’m running the script under git-bash.

Can you try using WSL as we don’t support git-bash for the install script?

Using WSL worked fine. Thank you!

1 Like

Hi,I have the same problem, but my machine OS is windows server., so I can’t use WSL.
I also see the same issue #705, but I don’t konw how to download the relay binary and generated the credentials manually by myself, can you tell me the detailed steps ?

You can find all relevant info on setting up relay on our docs: Getting Started | Sentry Documentation

Yes, it work for me! Thank you!

1 Like