> Hi, > due to changes in an application we have memory issues and therefore > workers killed by the oom-killer. What uWSGI logs is: > > DAMN ! worker 1 (pid: 2428) died, killed by signal 9 :( trying respawn ... > > > Is there a way to log the request path that the worker was processing when > killed? It would be very helpful to easily spot problems without a > profiler. > > Thanks >
Hi, this is a pretty extreme condition, but as the master is still alive it has access to current request infos: https://github.com/unbit/uwsgi/blob/master/core/master.c#L1047 like we do here: https://github.com/unbit/uwsgi/blob/master/core/uwsgi.c#L1549 -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
