[NGINX] cache process manager consume a lot of CPU at reload and has to be restarted

[Jérôme Loyet]

Hello,

I had an issue last night with a 0.8.54 nginx instance. Around 1AM, a HUP
signal is sent to log rotation. This nginx instance is set up as a reverse
proxy to an apache/php and it does some cache. Here is the proxy_cache
related conf I've set up.

proxy_cache_path /CACHE levels=1:2:2 keys_zone=cache:256m inactive=1d
max_size=20g;
proxy_cache cache;

Last night, the cache process manager has restarted well, but it has
consumed all CPU available on the server. Moreover, the SAR command
indicates that it did not seek, read or write on the disks (as the disk
usage remains almost null). Our exploitation team had to restart nginx 40
minutes later and it solves the problem.

Has someone already experience such an issue ? Do you know why this could
happened ?

Thx you
++ Jerome

PS: here is the related error_log:

2011/04/01 01:04:55 [notice] 25206#0: signal 1 (SIGHUP) received,
reconfiguring
2011/04/01 01:04:55 [notice] 25206#0: reconfiguring
2011/04/01 01:04:55 [notice] 25206#0: using the "epoll" event method
2011/04/01 01:04:55 [notice] 25206#0: start worker processes
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10450
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10451
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10452
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10453
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10454
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10455
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10456
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10457
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10458
2011/04/01 01:04:55 [notice] 25206#0: start worker process 10459
2011/04/01 01:04:55 [notice] 25206#0: start cache manager process 10460
2011/04/01 01:04:55 [notice] 25206#0: signal 17 (SIGCHLD) received
2011/04/01 01:04:55 [notice] 25206#0: worker process 7164 exited with code 0
2011/04/01 01:04:55 [notice] 25206#0: worker process 7166 exited with code 0
2011/04/01 01:04:55 [notice] 25206#0: worker process 30018 exited with code
0
2011/04/01 01:04:55 [notice] 25206#0: signal 17 (SIGCHLD) received
2011/04/01 01:04:55 [notice] 25206#0: worker process 7168 exited with code 0
2011/04/01 01:04:55 [notice] 25206#0: worker process 7170 exited with code 0
2011/04/01 01:04:55 [notice] 25206#0: worker process 7171 exited with code 0
2011/04/01 01:04:56 [notice] 25206#0: signal 29 (SIGIO) received
2011/04/01 01:04:56 [notice] 25206#0: signal 29 (SIGIO) received
2011/04/01 01:05:26 [notice] 25206#0: signal 17 (SIGCHLD) received
2011/04/01 01:05:26 [notice] 25206#0: worker process 7165 exited with code 0
2011/04/01 01:05:26 [notice] 25206#0: signal 29 (SIGIO) received
2011/04/01 01:45:55 [notice] 25206#0: signal 15 (SIGTERM) received, exiting
2011/04/01 01:45:55 [notice] 25206#0: signal 14 (SIGALRM) received
2011/04/01 01:45:55 [notice] 25206#0: signal 14 (SIGALRM) received
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20110401/f8896aca/attachment.html>