[uWSGI] restarting uwsgi with HUP occasionally gives bad fd
l.mierzwa at gmail.com
Tue Apr 15 10:59:38 CEST 2014
AFAIR this did show up if one was using alarm framework.
2014-04-15 6:27 GMT+02:00 Roberto De Ioris <roberto at unbit.it>:
> > I have an init.d script that I use to restart my uwsgi instance by
> > a HUP signal to the process. In the past I've had no issues and it
> > usually
> > restarts the instance in a nice way. Recently I've occasionally gotten
> > the
> > following in my logs:
> > worker 1 buried after 2 seconds
> > worker 2 buried after 3 seconds
> > binary reloading uWSGI...
> > chdir() to /
> > closing all non-uwsgi socket fds > 2 (max_fd = 1024)...
> > found fd 3 mapped to socket 0 (/var/run/uwsgi/metrics_dev.sock)
> > running /sites/metrics_dev/env/bin/uwsgi
> > Bad file descriptor (epoll.cpp:144)
> this file (epoll.cpp) is not part of uWSGI sources, so i find this error
> pretty strange. (Could it be zeromq ?)
> Can you paste the whole config ?
> Roberto De Ioris
> uWSGI mailing list
> uWSGI at lists.unbit.it
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the uWSGI