Open mhkeller opened 8 years ago
Does the API still come up though? This is weird because it looks from the logs like it actually is restarting...
msg: Stopping supervisor: supervisord.
Starting supervisor:
im not sure since i figured if vagrant fails, none of the changes go into
effect? or maybe that's not true. what would be a good way to test that it
was restarted correctly and not just the old process that's running without
having been restarted. i put on the VAGRANT_INFO=info
env variable for
more logging. i could send that or are you getting the error as well?
On Mon, Oct 12, 2015 at 4:40 PM, Brian Abelson notifications@github.com wrote:
Does the API still come up though? This is weird because it looks from the logs like it actually is restarting...
msg: Stopping supervisor: supervisord. Starting supervisor:
— Reply to this email directly or view it on GitHub https://github.com/newslynx/opportunities/issues/169#issuecomment-147513823 .
@mhkeller mhkeller.com
In automation, Supervisor throws the following error. The following is from running it locally in virtual box but i've also seen this on aws.