Hi Roberto, Thanks for the short term fix, if there's anything I can do to assist with getting a long term solution put in place (testing or code assist etc), just let me know.
Cheers Cal On Mon, May 14, 2012 at 7:27 AM, Roberto De Ioris <[email protected]> wrote: > > > Hi Roberto, > > > > It would seem that if New Relic becomes unavailable for whatever reason, > > all UWSGI processes will hang and fail. > > > > Please see the following logs. > > > > Any suggestions?? > > > > Cheers > > Newrelic spawns a thread in every process, so each problem (with uWSGI > itself or newrelic) will be propagated for sure. > > I am not quite sure to understand what is happening here (i need to talk > with Graham Dumpleton), but if workers are leaved in inconsistent state > after NewRelic failure you may want to auto-reload them with > "reload-on-exception" facility: > > --reload-on-exception-value "metric_data failed: status code 415" > > I will improve the answer as soon as possible > > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
