9: Bad file number - страшно?

[Alexander Popkov]

Приветствую!

В error.log от nginx строка:
[alert] 6877#0: close() failed (9: Bad file number)
это страшно?

Изменил в конфиге параметр proxy_read_timeout с 300 на 30
после сделал kill -HUP мастер процессу, в логе вот что:
--------------------------------------------
2004/11/19 16:34:07 [info] 29034#0: signal 1 (SIGHUP) received, reconfiguring
2004/11/19 16:34:07 [info] 29034#0: reconfiguring
2004/11/19 16:34:07 [info] 29034#0: start worker processes
2004/11/19 16:34:07 [info] 6877#0: gracefully shutting down
2004/11/19 16:34:07 [info] 6887#0: gracefully shutting down
2004/11/19 16:34:07 [info] 6886#0: gracefully shutting down
2004/11/19 16:34:07 [info] 6879#0: gracefully shutting down
2004/11/19 16:34:07 [info] 6879#0: exiting
2004/11/19 16:34:07 [info] 6907#0: gracefully shutting down
2004/11/19 16:34:07 [info] 29034#0: signal 18 (SIGCHLD) received
2004/11/19 16:34:07 [info] 29034#0: worker process 6879 exited with code 0
2004/11/19 16:34:07 [alert] 6877#0: close() failed (9: Bad file number)
2004/11/19 16:34:56 [info] 6877#0: *271244 client x.x.x.x closed keepalive connection (131: Connection reset by peer)
2004/11/19 16:34:56 [info] 6877#0: exiting
--------------------------------------------

-- 
Best regards,
 Alexander