Yes, that's correct. Once a vassal gets into the "broken" state,
whenever it tries to start, it hits an error and dies... touching its
.ini file just makes it try again, and die again.
--
Harry Percival
Developer
[email protected]
PythonAnywhere - a fully browser-based Python development and hosting
environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
On 10/03/14 15:26, Roberto De Ioris wrote:
it's hard to tell whether it's the kill error, because the logs in the
main log don't say which vassal it's for, but those vassals are then
failing to start up correctly, at least that's how it looks from their
individual logs:
2014-03-10 15:08:06 chdir(): No such file or directory [core/uwsgi.c line
1472]
2014-03-10 15:08:06 VACUUM: unix socket
/var/sockets/project003.pythonanywhere.com/socket removed.
Hmm, wait this is another problem, during vacuum uWSGI tries to set-back
the cwd that was set during startup. As you are under chroot this is not
possibile (the error is harmful).
So, you see this error and then the vassal is not started back ?
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
