Il giorno 21/gen/2011, alle ore 09.46, Maxim Sloyko ha scritto: > Hi all! > > Just wanted to report the error I encountered with uWSGI. > > When I send HUP or TERM signal to the master process, uWSGI dies with > the following error (flom the log): > > ...gracefully killing workers... > Gracefully killing worker 1426... > Gracefully killing worker 1427... > Gracefully killing worker 1428... > Gracefully killing worker 1429... > binary reloading uWSGI... > closing all fds > 2 (_SC_OPEN_MAX = 64512)... > running uwsgi > execve(): No such file or directory [uwsgi.c line 1411] >
This is caused by your binary path changing after startup. For example you start uwsgi with ./uwsgi in directory /tmp than you chdir to something else. When uWSGI restarts ./uwsgi is no more valid. There are other cases but they are all fixed in the patch 0966_0967 that you will find in the list archives, or you can wait til tomorrow when uwsgi-0.9.6.7 will be released. Another quick fix is specifying the uwsgi binary path using the --binary-path option -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
