> 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 ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
