Hello!

On Thu, May 02, 2019 at 08:51:41PM +1000, Mathew Heard wrote:

> Got a little bit further and confirmed this is definitely to do with the
> binary upgrade.
>
> www-data 988 99.9 0.7 365124 122784 ? R Jan30 131740:46 nginx:
> worker process
> root 2800 0.0 1.0 361828 165044 ? Ss Jan05 27:54 nginx:
> master process /usr/sbin/nginx -g daemon on; master_process on;
>
> 2800 is nginx.old, also (nginx/1.15.8) as we did 2 builds with slightly
> different compile options.
>
> The processes do not respond to nice kill signals, only a -9 was able to
> kill it.

So, as previously suggested, there is another problem elsewhere.

And, if I'm reading "131740:46" correctly, the worker was eating
CPU for about 90 days now. Looking into debugger where it spins
might be helpful.

Also make sure to take a look at the exact compile options (as
shown by "nginx.old -V"), as well as any patches and/or modules
loaded, and the configuration used.

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel