Errors in Unit logs and CPU 100%
Valentin V. Bartenev
vbart at nginx.com
Thu May 23 11:54:05 UTC 2019
On Thursday 23 May 2019 12:23:20 Peter TKATCHENKO wrote:
> I had the problem of CPU again this morning, it seems that the situation
> degrades :(
> I could attach the debugger to get the backtrace:
> #0 0x0000000800dfe81a in _kevent () from /lib/libc.so.7
> #1 0x0000000800a9bcc2 in ?? () from /lib/libthr.so.3
> #2 0x00000000004238c1 in nxt_kqueue_poll (engine=0x801416500,
> timeout=<optimized out>) at src/nxt_kqueue_engine.c:692
> #3 0x0000000000412bb0 in nxt_event_engine_start (engine=0x801416500) at
> #4 0x0000000000406c47 in main (argc=<optimized out>, argv=<optimized
> out>) at src/nxt_main.c:35
> If I kill the process - a new one is created and takes again 100% of
> CPU. And if I restart the service - it's OK.
> Please, help!
Unfortunately, this particular backtrace is useless, because it's from
different thread (not the one eats CPU).
Could you reproduce the issue with debug log enabled?
See for details: http://unit.nginx.org/troubleshooting/#debug-log
wbr, Valentin V. Bartenev
More information about the unit