Test log in on-premise worked but when called from my application logs are not written into hosted on-premise

1

Test log in on-premise worked but when called from my application logs are not written into hosted on-premise with same code if i try to log to sentry.io it works fine but not on to sentry-on-premise can anyone help me out to know what i’m missing up

have generated authToken and included it into application.

only things is while installing relay credentials was not been created in the file except taht all configuration and rest all things are setup correctly on my machine

2

Hi,

Can you share some logs as it is impossible to figure out what’s happening from your message?

Also, I’m assuming you are updating the DSN properly when switching between sentry.io and your on-premise installation?

3

Stopping sentry_onpremise_symbolicator-cleanup_1 … done

Stopping sentry_onpremise_sentry-cleanup_1 … done

Stopping sentry_onpremise_snuba-cleanup_1 … done

Stopping sentry_onpremise_post-process-forwarder_1 … done

Stopping sentry_onpremise_nginx_1 … done

Stopping sentry_onpremise_relay_1 … done

Stopping sentry_onpremise_cron_1 … done

Stopping sentry_onpremise_ingest-consumer_1 … done

Stopping sentry_onpremise_web_1 … done

Stopping sentry_onpremise_worker_1 … done

Stopping sentry_onpremise_memcached_1 … done

Stopping sentry_onpremise_smtp_1 … done

Stopping sentry_onpremise_postgres_1 … done

Stopping sentry_onpremise_snuba-sessions-consumer_1 … done

Stopping sentry_onpremise_symbolicator_1 … done

Stopping sentry_onpremise_snuba-outcomes-consumer_1 … done

Stopping sentry_onpremise_snuba-consumer_1 … done

Stopping sentry_onpremise_snuba-replacer_1 … done

Stopping sentry_onpremise_snuba-api_1 … done

Stopping sentry_onpremise_redis_1 … done

Stopping sentry_onpremise_clickhouse_1 … done

Stopping sentry_onpremise_kafka_1 … done

Stopping sentry_onpremise_zookeeper_1 … done

Removing sentry_onpremise_nginx_1 …

Removing sentry_onpremise_ingest-consumer_1 …

Removing sentry_onpremise_post-process-forwarder_1 …

Removing sentry_onpremise_cron_1 …

Removing sentry_onpremise_worker_1 …

Removing sentry_onpremise_web_1 …

Removing sentry_onpremise_sentry-cleanup_1 …

Removing sentry_onpremise_relay_1 …

Removing sentry_onpremise_snuba-api_1 …

Removing sentry_onpremise_snuba-cleanup_1 …

Removing sentry_onpremise_snuba-outcomes-consumer_1 …

Removing sentry_onpremise_snuba-sessions-consumer_1 …

Removing sentry_onpremise_snuba-consumer_1 …

Removing sentry_onpremise_snuba-replacer_1 …

Removing sentry_onpremise_kafka_1 …

Removing sentry_onpremise_symbolicator_1 …

Removing sentry_onpremise_postgres_1 …

Removing sentry_onpremise_zookeeper_1 …

Removing sentry_onpremise_redis_1 …

Removing sentry_onpremise_symbolicator-cleanup_1 …

Removing sentry_onpremise_memcached_1 …

Removing sentry_onpremise_smtp_1 …

Removing sentry_onpremise_clickhouse_1 …

Removing sentry_onpremise_ingest-consumer_1 … done

Removing sentry_onpremise_relay_1 … done

Removing sentry_onpremise_postgres_1 … done

Removing sentry_onpremise_post-process-forwarder_1 … done

Removing sentry_onpremise_snuba-sessions-consumer_1 … done

Removing sentry_onpremise_symbolicator-cleanup_1 … done

Removing sentry_onpremise_sentry-cleanup_1 … done

Removing sentry_onpremise_kafka_1 … done

Removing sentry_onpremise_smtp_1 … done

Removing sentry_onpremise_redis_1 … done

Removing sentry_onpremise_zookeeper_1 … done

Removing sentry_onpremise_snuba-consumer_1 … done

Removing sentry_onpremise_web_1 … done

Removing sentry_onpremise_symbolicator_1 … done

Removing sentry_onpremise_nginx_1 … done

Removing sentry_onpremise_worker_1 … done

Removing sentry_onpremise_snuba-replacer_1 … done

Removing sentry_onpremise_cron_1 … done

Removing sentry_onpremise_snuba-outcomes-consumer_1 … done

Removing sentry_onpremise_clickhouse_1 … done

Removing sentry_onpremise_snuba-api_1 … done

Removing sentry_onpremise_memcached_1 … done

Removing sentry_onpremise_snuba-cleanup_1 … done

Removing network sentry_onpremise_default

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.

sentry/sentry.conf.py already exists, skipped creation.
sentry/config.yml already exists, skipped creation.
sentry/requirements.txt already exists, skipped creation.

Fetching and updating Docker images…

ERROR: for kafka Get https://registry-1.docker.io/v2/: EOF

ERROR: for snuba-outcomes-consumer Get https://registry-1.docker.io/v2/: EOF

ERROR: for snuba-sessions-consumer Get https://registry-1.docker.io/v2/: EOF

ERROR: for snuba-consumer Get https://registry-1.docker.io/v2/: EOF

ERROR: for symbolicator Get https://registry-1.docker.io/v2/: EOF
Some service image(s) must be built from source by running:
docker-compose build worker snuba-cleanup ingest-consumer web sentry-cleanup post-process-forwarder cron symbolicator-cleanup
Get https://registry-1.docker.io/v2/: EOF
Get https://registry-1.docker.io/v2/: EOF
Get https://registry-1.docker.io/v2/: EOF
Get https://registry-1.docker.io/v2/: EOF
Get https://registry-1.docker.io/v2/: EOF
latest: Pulling from getsentry/sentry
8d691f585fa8: Already exists
3fd6980f9df6: Already exists
c4f890363b98: Already exists
b8cfb9853b0a: Already exists
2e3afb0715d5: Already exists
ca404508dac6: Already exists
df0b021b74a9: Already exists
351f9a7b0722: Already exists
1c44cd19707b: Pulling fs layer
10521c3d0318: Pulling fs layer
49d013cdc388: Pulling fs layer
298b66758d94: Pulling fs layer
3a05e0b855f7: Pulling fs layer
955a7eeb37e1: Pulling fs layer
298b66758d94: Waiting
3a05e0b855f7: Waiting
955a7eeb37e1: Waiting
49d013cdc388: Verifying Checksum
49d013cdc388: Download complete
298b66758d94: Verifying Checksum
298b66758d94: Download complete
3a05e0b855f7: Verifying Checksum
3a05e0b855f7: Download complete
955a7eeb37e1: Verifying Checksum
955a7eeb37e1: Download complete
10521c3d0318: Verifying Checksum
10521c3d0318: Download complete
1c44cd19707b: Verifying Checksum
1c44cd19707b: Download complete
1c44cd19707b: Pull complete
10521c3d0318: Pull complete
49d013cdc388: Pull complete
298b66758d94: Pull complete
3a05e0b855f7: Pull complete
955a7eeb37e1: Pull complete
Digest: sha256:ca37968ec074bb44237d8069d4d9f2506456db7c6d235f935b65af5189b37b77
Status: Downloaded newer image for getsentry/sentry:latest
docker.io/getsentry/sentry:latest

Building and tagging Docker images…

Building web
Step 1/5 : ARG SENTRY_VERSION=latest
Step 2/5 : ARG SENTRY_IMAGE
Step 3/5 : FROM ${SENTRY_IMAGE:-getsentry/sentry:$SENTRY_VERSION}
—> 1f006c54ff15
Step 4/5 : COPY . /usr/src/sentry
—> d4e5896119f3
Step 5/5 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
—> Running in 83b4a8e26949
e[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 83b4a8e26949
—> 9cc393f5153c

Successfully built 9cc393f5153c
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-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 web
Building worker
Building post-process-forwarder
Building symbolicator-cleanup
Building sentry-cleanup
Step 1/5 : ARG SENTRY_VERSION=latest
Step 2/5 : ARG SENTRY_IMAGE
Step 3/5 : FROM ${SENTRY_IMAGE:-getsentry/sentry:$SENTRY_VERSION}
—> 1f006c54ff15
Step 4/5 : COPY . /usr/src/sentry
—> Using cache
—> d4e5896119f3
Step 5/5 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
—> Using cache
—> 9cc393f5153c

Successfully built 9cc393f5153c
Successfully tagged sentry-onpremise-local:latest
Building web … done

Building snuba-cleanup
Step 1/5 : ARG SENTRY_VERSION=latest
Step 2/5 : ARG SENTRY_IMAGE
Step 3/5 : FROM ${SENTRY_IMAGE:-getsentry/sentry:$SENTRY_VERSION}
—> 1f006c54ff15
Step 4/5 : COPY . /usr/src/sentry
—> Using cache
—> d4e5896119f3
Step 5/5 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
—> Using cache
—> 9cc393f5153c

Successfully built 9cc393f5153c
Step 1/5 : ARG BASE_IMAGE
Step 2/5 : FROM ${BASE_IMAGE}
—> d6cf0be44380
Step 3/5 : RUN apt-get update && apt-get install -y --no-install-recommends cron && rm -r /var/lib/apt/lists/*
—> Using cache
—> ffed92e15ba2
Step 4/5 : COPY entrypoint.sh /entrypoint.sh
—> Using cache
—> 16ac65915fe6
Step 5/5 : ENTRYPOINT ["/entrypoint.sh"]
—> Using cache
—> d578b386e40e

Successfully tagged sentry-onpremise-local:latest
Building post-process-forwarder … done

Building ingest-consumer
Successfully built d578b386e40e
Step 1/5 : ARG BASE_IMAGE
Step 2/5 : FROM {BASE_IMAGE} Step 1/5 : ARG SENTRY_VERSION=latest Step 2/5 : ARG SENTRY_IMAGE Step 3/5 : FROM {SENTRY_IMAGE:-getsentry/sentry:$SENTRY_VERSION}
—> 9cc393f5153c
Step 3/5 : RUN apt-get update && apt-get install -y --no-install-recommends cron && rm -r /var/lib/apt/lists/*
—> 1f006c54ff15
Step 4/5 : COPY . /usr/src/sentry
—> Using cache
—> d4e5896119f3
Step 5/5 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
—> Using cache
—> 9cc393f5153c

Successfully built 9cc393f5153c
Successfully tagged symbolicator-cleanup-onpremise-local:latest
Building symbolicator-cleanup … done

Building cron
Successfully tagged sentry-onpremise-local:latest
Building worker … done

—> Running in 63249eb38a37
Get:1 http://deb.debian.org/debian buster InRelease [121 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [203 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7905 kB]
Step 1/5 : ARG SENTRY_VERSION=latest
Step 2/5 : ARG SENTRY_IMAGE
Step 3/5 : FROM ${SENTRY_IMAGE:-getsentry/sentry:$SENTRY_VERSION}
—> 1f006c54ff15
Step 4/5 : COPY . /usr/src/sentry
—> Using cache
—> d4e5896119f3
Step 5/5 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
—> Using cache
—> 9cc393f5153c

Successfully built 9cc393f5153c
Successfully tagged sentry-onpremise-local:latest
Building ingest-consumer … done

Step 1/5 : ARG SENTRY_VERSION=latest
Step 2/5 : ARG SENTRY_IMAGE
Step 3/5 : FROM ${SENTRY_IMAGE:-getsentry/sentry:$SENTRY_VERSION}
—> 1f006c54ff15
Step 4/5 : COPY . /usr/src/sentry
—> Using cache
—> d4e5896119f3
Step 5/5 : RUN if [ -s /usr/src/sentry/requirements.txt ]; then pip install -r /usr/src/sentry/requirements.txt; fi
—> Using cache
—> 9cc393f5153c

Successfully built 9cc393f5153c
Step 1/5 : ARG BASE_IMAGE
Step 2/5 : FROM ${BASE_IMAGE}
—> ded3ba7835ca
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 cron … done

—> Running in 77dec084c572
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 http://deb.debian.org/debian buster InRelease [121 kB]
Get:3 http://security.debian.org/debian-security buster/updates/main amd64 Packages [203 kB]
Get:4 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7905 kB]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [7868 B]
Fetched 8355 kB in 10s (852 kB/s)
Reading package lists…
Reading package lists…
Building dependency tree…
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
The following NEW packages will be installed:
cron lsb-base sensible-utils
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]
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]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [7868 B]
e[91mdebconf: delaying package configuration, since apt-utils is not installed
e[0mFetched 143 kB in 1s (155 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) …

Selecting previously unselected package lsb-base.

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

Unpacking lsb-base (10.2019051400) …

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) …

Done.

invoke-rc.d: could not determine current runlevel

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

Removing intermediate container 63249eb38a37
—> b95035516445
Step 4/5 : COPY entrypoint.sh /entrypoint.sh
—> a2ec0f5d273d
Step 5/5 : ENTRYPOINT ["/entrypoint.sh"]
—> Running in 73353dee34b6
Removing intermediate container 73353dee34b6
—> ca23d0c4d9cd

Successfully built ca23d0c4d9cd
Successfully tagged sentry-cleanup-onpremise-local:latest
Building sentry-cleanup … done

Fetched 8355 kB in 11s (730 kB/s)
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
The following additional packages will be installed:
sensible-utils
Suggested packages:
anacron logrotate checksecurity
Recommended packages:
default-mta | mail-transport-agent
The following NEW packages will be installed:
cron sensible-utils
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]
e[91mdebconf: delaying package configuration, since apt-utils is not installed
e[0mFetched 115 kB in 1s (201 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 … 6838 files and directories currently installed.)

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

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) …

Setting up sensible-utils (0.0.12) …

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

Adding group `crontab’ (GID 101) …

Done.

invoke-rc.d: could not determine current runlevel

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

Removing intermediate container 77dec084c572
—> 10507106ac6d
Step 4/5 : COPY entrypoint.sh /entrypoint.sh
—> 98787b5e1eb3
Step 5/5 : ENTRYPOINT ["/entrypoint.sh"]
—> Running in 6f6b254753f0
Removing intermediate container 6f6b254753f0
—> 8c8d9ccf458f

Successfully built 8c8d9ccf458f
Successfully tagged snuba-cleanup-onpremise-local:latest
Building snuba-cleanup … done

Docker images built.
Creating network “sentry_onpremise_default” with the default driver
Bootstrapping and migrating Snuba…
Creating sentry_onpremise_zookeeper_1 …

Creating sentry_onpremise_clickhouse_1 …

Creating sentry_onpremise_redis_1 …

Creating sentry_onpremise_clickhouse_1 … done

Creating sentry_onpremise_zookeeper_1 … done

Creating sentry_onpremise_redis_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
    2020-06-16 10:52:34,327 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”}
    2020-06-16 10:52:36,330 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”}
    2020-06-16 10:52:38,222 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.7/concurrent/futures/_base.py”, line 435, in result
    return self.__get_result()
    File “/usr/local/lib/python3.7/concurrent/futures/_base.py”, line 384, in __get_result
    raise self._exception
    cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str=“Topic ‘outcomes’ already exists.”}
    2020-06-16 10:52:38,224 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.7/concurrent/futures/_base.py”, line 428, in result
    return self.__get_result()
    File “/usr/local/lib/python3.7/concurrent/futures/_base.py”, line 384, in __get_result
    raise self._exception
    cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str=“Topic ‘events’ already exists.”}
    2020-06-16 10:52:38,225 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.7/concurrent/futures/_base.py”, line 428, in result
    return self.__get_result()
    File “/usr/local/lib/python3.7/concurrent/futures/_base.py”, line 384, in __get_result
    raise self._exception
    cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str=“Topic ‘event-replacements’ already exists.”}
    2020-06-16 10:52:38,225 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.7/concurrent/futures/_base.py”, line 428, in result
    return self.__get_result()
    File “/usr/local/lib/python3.7/concurrent/futures/_base.py”, line 384, in __get_result
    raise self._exception
    cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str=“Topic ‘snuba-commit-log’ already exists.”}
    2020-06-16 10:52:38,225 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.7/concurrent/futures/_base.py”, line 428, in result
    return self.__get_result()
    File “/usr/local/lib/python3.7/concurrent/futures/_base.py”, line 384, in __get_result
    raise self._exception
    cimpl.KafkaException: KafkaError{code=TOPIC_ALREADY_EXISTS,val=36,str=“Topic ‘ingest-sessions’ already exists.”}
    2020-06-16 10:52:38,226 Topic errors-replacements created
    2020-06-16 10:52:38,226 Topic cdc created
    2020-06-16 10:52:38,249 Creating tables for storage events
    2020-06-16 10:52:38,265 Migrating storage events
    2020-06-16 10:52:38,323 Creating tables for storage errors
    2020-06-16 10:52:38,360 Migrating storage errors
    2020-06-16 10:52:38,399 Creating tables for storage groupedmessages
    2020-06-16 10:52:38,404 Migrating storage groupedmessages
    2020-06-16 10:52:38,414 Creating tables for storage groupassignees
    2020-06-16 10:52:38,419 Migrating storage groupassignees
    2020-06-16 10:52:38,427 Creating tables for storage outcomes_raw
    2020-06-16 10:52:38,432 Migrating storage outcomes_raw
    2020-06-16 10:52:38,440 Creating tables for storage outcomes_hourly
    2020-06-16 10:52:38,450 Migrating storage outcomes_hourly
    2020-06-16 10:52:38,455 Creating tables for storage sessions_raw
    2020-06-16 10:52:38,462 Migrating storage sessions_raw
    2020-06-16 10:52:38,471 Creating tables for storage sessions_hourly
    2020-06-16 10:52:38,489 Migrating storage sessions_hourly
    2020-06-16 10:52:38,500 Creating tables for storage transactions
    2020-06-16 10:52:38,508 Migrating storage transactions

Setting up database…
Starting sentry_onpremise_clickhouse_1 …

Starting sentry_onpremise_clickhouse_1 … done

Creating sentry_onpremise_smtp_1 …

Creating sentry_onpremise_symbolicator_1 …

Starting sentry_onpremise_zookeeper_1 …

Starting sentry_onpremise_zookeeper_1 … done

Starting sentry_onpremise_redis_1 …

Creating sentry_onpremise_postgres_1 …

Starting sentry_onpremise_redis_1 … done

Creating sentry_onpremise_memcached_1 …

Starting sentry_onpremise_kafka_1 …

Starting sentry_onpremise_kafka_1 … done

Creating sentry_onpremise_snuba-replacer_1 …

Creating sentry_onpremise_snuba-consumer_1 …

Creating sentry_onpremise_snuba-sessions-consumer_1 …

Creating sentry_onpremise_snuba-outcomes-consumer_1 …

Creating sentry_onpremise_snuba-api_1 …

Creating sentry_onpremise_postgres_1 … done

Creating sentry_onpremise_symbolicator_1 … done

Creating sentry_onpremise_memcached_1 … done

Creating sentry_onpremise_snuba-outcomes-consumer_1 … done

Creating sentry_onpremise_snuba-api_1 … done

Creating sentry_onpremise_snuba-consumer_1 … done

Creating sentry_onpremise_smtp_1 … done

Creating sentry_onpremise_snuba-replacer_1 … done

Creating sentry_onpremise_snuba-sessions-consumer_1 … done

10:52:56 [WARNING] sentry.utils.geo: settings.GEOIP_PATH_MMDB not configured.
10:52:59 [INFO] sentry.plugins.github: apps-not-configured
Operations to perform:
Apply all migrations: admin, auth, contenttypes, jira_ac, nodestore, sentry, sessions, sites, social_auth
Running migrations:
Applying sentry.0001_initial… OK
Applying contenttypes.0001_initial… OK
Applying admin.0001_initial… OK
Applying admin.0002_logentry_remove_auto_add… OK
Applying contenttypes.0002_remove_content_type_name… OK
Applying auth.0001_initial… OK
Applying auth.0002_alter_permission_name_max_length… OK
Applying auth.0003_alter_user_email_max_length… OK
Applying auth.0004_alter_user_username_opts… OK
Applying auth.0005_alter_user_last_login_null… OK
Applying auth.0006_require_contenttypes_0002… OK
Applying auth.0007_alter_validators_add_error_messages… OK
Applying auth.0008_alter_user_username_max_length… OK
Applying jira_ac.0001_initial… OK
Applying nodestore.0001_initial… OK
Applying sentry.0002_912_to_recent… OK
Applying sentry.0003_auto_20191022_0122… OK
Applying sentry.0004_bitfieldtestmodel_blankjsonfieldtestmodel_callabledefaultmodel_jsonfieldtestmodel_jsonfieldwithdefau… OK
Applying sentry.0005_fix_content_types… OK
Applying sentry.0006_sentryapp_date_published… OK
Applying sentry.0007_auto_20191029_0131… OK
Applying sentry.0008_auto_20191030_0016… OK
Applying sentry.0009_auto_20191101_1608… OK
Applying sentry.0010_auto_20191104_1641… OK
Applying sentry.0011_remove_pagerdutyservice_service_id_from_state… OK
Applying sentry.0012_remove_pagerdutyservice_service_id… OK
Applying sentry.0013_auto_20191111_1829… OK
Applying sentry.0014_delete_sentryappwebhookerror… OK
Applying sentry.0015_delete_sentryappwebhookerror_db… OK
Applying sentry.0016_delete_alert_rule_deprecated_fields… OK
Applying sentry.0017_incident_aggregation… OK
Applying sentry.0018_discoversavedquery_version… OK
Applying sentry.0019_auto_20191114_2040… OK
Applying sentry.0020_auto_20191125_1420… OK
Applying sentry.0021_auto_20191203_1803… OK
Applying sentry.0021_auto_20191202_1716… OK
Applying sentry.0022_merge… OK
Applying sentry.0023_hide_environment_none_20191126… OK
Applying sentry.0024_auto_20191230_2052…Nothing to do, skipping migration.

OK
Applying sentry.0025_organizationaccessrequest_requester… OK
Applying sentry.0026_delete_event… OK
Applying sentry.0027_exporteddata… OK
Applying sentry.0028_user_reports… OK
Applying sentry.0029_discover_query_upgrade… OK
Applying sentry.0030_auto_20200201_0039… OK
Applying sentry.0031_delete_alert_rules_and_incidents… OK
Applying sentry.0032_delete_alert_email… OK
Applying sentry.0033_auto_20200210_2137… OK
Applying sentry.0034_auto_20200210_2311… OK
Applying sentry.0035_auto_20200127_1711… OK
Applying sentry.0036_auto_20200213_0106… OK
Applying sentry.0037_auto_20200213_0140… OK
Applying sentry.0038_auto_20200213_1904… OK
Applying sentry.0039_delete_incidentsuspectcommit… OK
Applying sentry.0040_remove_incidentsuspectcommittable… OK
Applying sentry.0041_incidenttrigger_date_modified… OK
Applying sentry.0042_auto_20200214_1607… OK
Applying sentry.0043_auto_20200218_1903… OK
Applying sentry.0044_auto_20200219_0018… OK
Applying sentry.0045_remove_incidentactivity_event_stats_snapshot… OK
Applying sentry.0046_auto_20200221_1735… OK
Applying sentry.0047_auto_20200224_2319… OK
Applying sentry.0048_auto_20200302_1825… OK
Applying sentry.0049_auto_20200304_0254… OK
Applying sentry.0050_auto_20200306_2346… OK
Applying sentry.0051_fix_auditlog_pickled_data… OK
Applying sentry.0052_organizationonboardingtask_completion_seen… OK
Applying sentry.0053_migrate_alert_task_onboarding… OK
Applying sentry.0054_create_key_transaction… OK
Applying sentry.0055_query_subscription_status… OK
Applying sentry.0056_remove_old_functions… OK
Applying sentry.0057_remove_unused_project_flag… OK
Applying sentry.0058_project_issue_alerts_targeting… OK
Applying sentry.0059_add_new_sentry_app_features… OK
Applying sentry.0060_add_file_eventattachment_index… OK
Applying sentry.0061_alertrule_partial_index… OK
Applying sentry.0062_key_transactions_unique_with_owner… OK
Applying sentry.0063_drop_alertrule_constraint… OK
Applying sentry.0064_project_has_transactions… OK
Applying sentry.0065_add_incident_status_method… OK
Applying sentry.0066_alertrule_manager… OK
Applying sentry.0067_migrate_rules_alert_targeting… OK
Applying sentry.0068_project_default_flags… OK
Applying sentry.0069_remove_tracked_superusers… OK
Applying sentry.0070_incident_snapshot_support… OK
Applying sentry.0071_add_default_fields_model_subclass… OK
Applying sentry.0072_alert_rules_query_changes… OK
Applying sentry.0073_migrate_alert_query_model… OK
Applying sentry.0074_add_metric_alert_feature… OK
Applying sentry.0075_metric_alerts_fix_releases… OK
Applying sentry.0076_alert_rules_disable_constraints… OK
Applying sentry.0077_alert_query_col_drop_state… OK
Applying sentry.0078_incident_field_updates… OK
Applying sentry.0079_incidents_remove_query_field_state… OK
Applying sentry.0080_alert_rules_drop_unused_tables_cols… OK
Applying sentry.0081_add_integraiton_upgrade_audit_log… OK
Applying sentry.0082_alert_rules_threshold_float… OK
Applying sentry.0083_add_max_length_webhook_url… OK
Applying sentry.0084_exported_data_blobs… OK
Applying sentry.0085_fix_error_rate_snuba_query… OK
Applying sessions.0001_initial… OK
Applying sites.0001_initial… OK
Applying sites.0002_alter_domain_unique… OK
Applying social_auth.0001_initial… OK
10:54:23 [WARNING] sentry: Cannot initiate onboarding for organization (1) due to missing owners
Created internal Sentry project (slug=internal, id=1)

Would you like to create a user account now? [Y/n]: Email: Password: /usr/local/lib/python2.7/getpass.py:83: GetPassWarning: Can not control echo on the terminal.
passwd = fallback_getpass(prompt, stream)
Warning: Password input may be echoed.

Repeat for confirmation: Warning: Password input may be echoed.

User created: poojap@in.unibiz.com
Added to organization: sentry
Creating missing DSNs
Correcting Group.num_comments counter
FAIL: Cannot read credentials back from relay/credentials.json.
Please ensure this file is readable and contains valid credentials.

4

Above mentioned is part of log starting some 50lines is excluded due to size limit

Issues 1: the relay credentials is not getting generated
Note Im using sentry 10

Issue 2: Sentry Logger [Log]: Failed to get device context from native: TypeError: RNSentry.deviceContexts is not a function

5

Your logs suggest connection issues to Docker Hub preventing a bunch of updates and operations. Once you resolve that issue, can you try again and see what happens?