Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Docker gunicorn process correctly starts up but doesn't run the app

See original GitHub issue

Not sure if clone of #150.

I have local AWS credentials (in ~/.aws) and the configuration variables passed to Docker via a CLI arg but nothing shows up when I navigate to the app’s address. In addition, tables aren’t created/there’s nothing that indicates a running process. I run:

> docker run --env-file DOCKER_CONFIG -t lyft/confidant

What I see when I navigate to http://0.0.0.0:80:

Do the KMS master or auth keys have to be created manually in AWS’ IAM in order to get this running?

Thank you!

Issue Analytics

State:
Created 6 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

3reactions

philipbjorgecommented, Oct 26, 2017

@arjunblj – how’d you resolve this?

0reactions

arjunbljcommented, Sep 20, 2017

Full log for docker-compose up

> ~ docker-compose up
Starting confidant_dynamo_1 ...
Starting confidant_redis_1 ...
Starting confidant_dynamo_1
Starting confidant_redis_1 ... done
Starting confidant_confidant_1 ...
Starting confidant_confidant_1 ... done
Attaching to confidant_dynamo_1, confidant_redis_1, confidant_confidant_1
dynamo_1     | Initializing DynamoDB Local with the following configuration:
dynamo_1     | Port:	7777
dynamo_1     | InMemory:	false
dynamo_1     | DbPath:	/mnt/dynamo
dynamo_1     | SharedDb:	false
dynamo_1     | shouldDelayTransientStatuses:	false
dynamo_1     | CorsParams:	*
dynamo_1     |
redis_1      | 1:C 20 Sep 20:23:04.154 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1      | 1:C 20 Sep 20:23:04.154 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1      | 1:C 20 Sep 20:23:04.154 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1      | 1:M 20 Sep 20:23:04.159 * Running mode=standalone, port=6379.
redis_1      | 1:M 20 Sep 20:23:04.159 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1      | 1:M 20 Sep 20:23:04.159 # Server initialized
redis_1      | 1:M 20 Sep 20:23:04.161 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1      | 1:M 20 Sep 20:23:04.163 * DB loaded from disk: 0.002 seconds
redis_1      | 1:M 20 Sep 20:23:04.163 * Ready to accept connections
confidant_1  | [2017-09-20 20:23:05 +0000] [1] [INFO] Starting gunicorn 19.7.1
confidant_1  | [2017-09-20 20:23:05 +0000] [1] [INFO] Listening at: http://0.0.0.0:80 (1)
confidant_1  | [2017-09-20 20:23:05 +0000] [1] [INFO] Using worker: gevent
confidant_1  | [2017-09-20 20:23:05 +0000] [9] [INFO] Booting worker with pid: 9
confidant_1  | [2017-09-20 20:23:05 +0000] [10] [INFO] Booting worker with pid: 10
confidant_1  | 172.17.0.1 - - [20/Sep/2017:20:23:21 +0000] "GET / HTTP/1.1" 302 243 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36"

service.env has my real env variables and Google Auth is set up correctly. I’ve also added logging to the gunicorn task with --log-level set to debug, but nothing additional is logged out.