vagrant-puppet-nginx-uwsgi-flask icon indicating copy to clipboard operation
vagrant-puppet-nginx-uwsgi-flask copied to clipboard

Internal server error after vagrant reload

Open pestrov opened this issue 9 years ago • 3 comments

Everything runs just fine until you try to reload the machine. Any ideas why this could happen?

pestrov avatar Oct 06 '15 23:10 pestrov

What's the error?

linssen avatar Oct 14 '15 10:10 linssen

I'm having the same issue. Here's the uwsgi log showing the first successful load, and the second unsuccessful load after a vagrant halt && vagrant up.

This doesn't happen when I just suspend the machine.

Edit: If I run the uwsgi init command manually or service uwsgi restart it works.

JFreegman avatar Mar 11 '16 23:03 JFreegman

Sorry for the late response, I've not looked at this for a year or so. Looks to me like upstart isn't automatically starting / restarting uwsgi. I'd suggest having fiddle with the manifest about here. If you have any success, a pull request is always very welcome.

Thanks for the logs and report, @JFreegman. Let us know how you get on.

linssen avatar Mar 14 '16 21:03 linssen