I am trying to install of Sentry On Premis 20.12.1 in Ubuntu 18.04 virtual box.
When I run the install.sh script, I faced the following issue -
Error
ERROR: for snuba-cleanup UnixHTTPConnectionPool(host='localhost', port=None): Pool is closed.
Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
An error occurred, caught SIGERR on line 227
Cleaning up...
Configuration:
I also didn’t get what to put in db password and db port sentry.conf.py file
The recommended way to customize your configuration is using the files below, in that order:
* `config.yml`
* `sentry.conf.py`
* `.env` w/ environment variables
So I put sentry.conf.py, conf.yml file with .env but after running the script, it generates new sentry.conf.py, conf.yml in sentry folder.
There is another observation - getting error from Docker pull “You have reached your pull rate limit”
Also I got - Docker: Having issues installing apt-utils
Can anyone please help me how to setup the configuration and setup sentry on premise.
@Alexander
I saw those option. But not able to come out the situations.
What would be the db configuration?
I set in the console export DOCKER_HOST=127.0.0.1:2375 and run using sudo . That’s working now. But now I have 502 Bad Gateway
one of the following container is exited - sentry_onpremise_geoipupdate_1 /usr/bin/geoipupdate -d /s ... Exit 1
Log of that container -
sudo docker logs sentry_onpremise_geoipupdate_1 ⏎
error loading configuration file /sentry/GeoIP.conf: error opening file: open /sentry/GeoIP.conf: no such file or directory
The DB configuration is already set so you should not need to change anything. Once you skip the default admin user creation, you can do what we do in our test script to create a user:
docker-compose run --rm web createuser --superuser --email $TEST_USER --password $TEST_PASS
@BYK
So I installed the Self-Hosted in AWS EC2 . All the containers are up. While I am trying to access Sentry url using the EC2 public IP, Like http://aws_public_ip and The site is not reachable - This site can’t be reached.
I didn’t edit any configuration in nginx.conf or anywhere and I am not using any domain as well.
@Alexander
Yes, might be but I am not able to reach the sentry.
After installing I tried from aws instance to the http://public_ip:9000 . It’s not working.