The docker container is up.
My best guess is that the unicorn process is the issue:
Here is the bottom of docker logs, followed immediately by a ps -ef|grep unicorn
ok: run: redis: (pid 47) 688s
ok: run: postgres: (pid 44) 688s
supervisor pid: 3743 unicorn pid: 3748
config/unicorn_launcher: line 44: kill: (3748) - No such process
config/unicorn_launcher: line 10: kill: (3748) - No such process
exiting
ok: run: redis: (pid 47) 695s
ok: run: postgres: (pid 44) 695s
supervisor pid: 3782 unicorn pid: 3787
config/unicorn_launcher: line 44: kill: (3787) - No such process
config/unicorn_launcher: line 10: kill: (3787) - No such process
exiting
ok: run: redis: (pid 47) 702s
ok: run: postgres: (pid 44) 702s
supervisor pid: 3822 unicorn pid: 3827
root@ip-172-31-29-7:/var/discourse/shared/standalone# ps -ef|grep unicorn
root 402 400 0 13:41 ? 00:00:00 runsv unicorn
ubuntu 4837 402 6 13:53 ? 00:00:00 /bin/bash config/unicorn_launcher -E production -c config/unicorn.conf.rb
ubuntu 4842 4837 67 13:53 ? 00:00:01 ruby /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn -E production -c config/unicorn.conf.rb
I’ve done a(nother) ./launcher rebuild app, as well as a reboot in the meantime.
Could it be that the unicorn is falling over on it’s own before the start tries to kill it off and restart it, and the pids are getting out of sync?