> Hi, > > Thank you for your quick reply roberto. > > Unfortunately, it seems it don't works on my computer. When I send a > SIGURG signal to my emperor, I see a line "Fri Jan 8 14:43:23 2016 - > [uwsgi-emperor] cleaning up blacklist ..." appear in my logs but then > if I reload the emperor stat page, the vassal is still blacklisted and > the attempt number hasn't changed. > > On http://uwsgi-docs.readthedocs.org/en/latest/Emperor.html, I see > nothing about this feature either. > > But now I know that my vassal is blacklisted, the appropriate section > gave me a solution for the first problem I had. > > The second problem I mentioned in the issue is the freeze we had once, > but I'll come back to you if we succeed in reproducing it. > > This issue is solved for now but I discovered two problems : > - The feature you mentioned seems to be undocumented or isn't easy to > find > - The same feature seems broken > > I would have thought I need to enable an option for the feature to > work but since I got the log message, it should be working as is. I'll > open an issue for this. > > Thank you for your help, > >
Hi, this is the relevant part of the code: https://github.com/unbit/uwsgi/blob/uwsgi-2.0/core/emperor.c#L1637 maybe you can try debugging it. Oh and yes, Emperor SIGURG is not documented :( -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
