> Hi, > > I'm using uWSGI 0.9.7.2 on MacOS 10.6.7. When I try to gracefully reload > the > code of my workers using SIGHUP, I get the following output from uWSGI: > <some output snipped> > binary reloading uWSGI... > closing all non-uwsgi socket fds > 2 (_SC_OPEN_MAX = 2560)... > found fd 18 mapped to socket 0 (/tmp/audish/uwsgi.sock) > <no more output beyond this point> > > ...and then the process hangs. In /var/log/system.log, these lines appear: > Apr 10 18:47:38 host /usr/local/bin/uwsgi[25911]: BUG in libdispatch: > 10J869 - 1986 - 0x4 Apr 10 18:47:40 host ReportCrash[25939]: Saved > crash > report for uwsgi[25911] version ??? (???) to > /Users/user/Library/Logs/DiagnosticReports/uwsgi_2011-04-10-184740_host.crash > > And in > /Users/user/Library/Logs/DiagnosticReports/uwsgi_2011-04-10-184740_host.crash, > the most important line (I believe) is: > Application Specific Information: > BUG IN CLIENT OF LIBDISPATCH: Do not close random Unix descriptors > I'm fairly convinced that the socket closing code in master.py should be > modified so as not to upset libdispatch, but I'm still not entirely sure > how > to go about doing it (maybe I'll play with it more and see if I can find a > patch later today). > > Is this a known bug? Is there a known workaround? How can I assist in > producing a fix? > > Cheers, > - Yaniv >
It looks your uWSGI is linked with libdispatch (and this is funny, as uWSGI does not support it [for now]). Have you compiled it directly from XCode ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
