ПРОЕКТЫ 


  АРХИВ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 


  СТАТЬИ 


  ПЕРСОНАЛЬНОЕ 


  ПРОГРАММЫ 



ПИШИТЕ
ПИСЬМА












     АРХИВ :: nginx-ru
Nginx-ru mailing list archive (nginx-ru@sysoev.ru)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nginx-0.8.16



Здравствуйте, Igor.

Nginx 0.8.15, скомпилирован под 32 бита, работает на Solaris 10 x64,
uname: SunOS xxx.yyyyyy.ru 5.10 Generic_127128-11 i86pc i386 i86pc

После переконфигурирования (kill -HUP) в логе появляются такие
сообщения:
2009/09/23 23:54:35 [notice] 20867#0: signal 1 (SIGHUP) received, reconfiguring
2009/09/23 23:54:35 [notice] 20867#0: reconfiguring
2009/09/23 23:54:35 [notice] 20867#0: using the "/dev/poll" event method
2009/09/23 23:54:35 [notice] 20867#0: start worker processes
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4681
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4682
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4683
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4684
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4685
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4686
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4687
2009/09/23 23:54:35 [notice] 20867#0: start worker process 4688
2009/09/23 23:54:35 [notice] 20869#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20868#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20871#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20870#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20873#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20875#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20874#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20872#0: gracefully shutting down
2009/09/23 23:54:35 [notice] 20868#0: exiting
2009/09/23 23:54:35 [notice] 20868#0: exit
2009/09/23 23:54:35 [notice] 20875#0: exiting
2009/09/23 23:54:35 [notice] 20875#0: exit
2009/09/23 23:54:35 [notice] 20870#0: exiting
2009/09/23 23:54:35 [alert] 20870#0: open socket #96 left in connection 130
2009/09/23 23:54:35 [alert] 20870#0: aborting
2009/09/23 23:54:35 [notice] 20870#0: exit
2009/09/23 23:54:35 [notice] 20872#0: exiting
2009/09/23 23:54:35 [alert] 20872#0: open socket #152 left in connection 172
2009/09/23 23:54:35 [alert] 20872#0: aborting
2009/09/23 23:54:35 [notice] 20872#0: exit
2009/09/23 23:54:35 [notice] 20871#0: exiting
2009/09/23 23:54:35 [alert] 20871#0: open socket #113 left in connection 301
2009/09/23 23:54:35 [alert] 20871#0: aborting
2009/09/23 23:54:35 [notice] 20871#0: exit
2009/09/23 23:54:35 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:35 [notice] 20867#0: worker process 20875 exited with code 0
2009/09/23 23:54:35 [notice] 20867#0: worker process 20868 exited with code 0
2009/09/23 23:54:35 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:35 [notice] 20867#0: worker process 20872 exited with code 0
2009/09/23 23:54:35 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:35 [notice] 20867#0: worker process 20871 exited with code 0
2009/09/23 23:54:35 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:35 [notice] 20867#0: worker process 20870 exited with code 0
2009/09/23 23:54:35 [notice] 20874#0: exiting
2009/09/23 23:54:35 [alert] 20874#0: open socket #107 left in connection 46
2009/09/23 23:54:35 [alert] 20874#0: aborting
2009/09/23 23:54:35 [notice] 20874#0: exit
2009/09/23 23:54:35 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:35 [notice] 20867#0: worker process 20874 exited with code 0
2009/09/23 23:54:36 [notice] 20869#0: exiting
2009/09/23 23:54:36 [alert] 20869#0: open socket #237 left in connection 101
2009/09/23 23:54:36 [alert] 20869#0: open socket #165 left in connection 334
2009/09/23 23:54:36 [alert] 20869#0: aborting
2009/09/23 23:54:36 [notice] 20869#0: exit
2009/09/23 23:54:36 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:36 [notice] 20867#0: worker process 20869 exited with code 0
2009/09/23 23:54:47 [notice] 20873#0: exiting
2009/09/23 23:54:47 [alert] 20873#0: open socket #122 left in connection 157
2009/09/23 23:54:47 [alert] 20873#0: aborting
2009/09/23 23:54:47 [notice] 20873#0: exit
2009/09/23 23:54:47 [notice] 20867#0: signal 18 (SIGCHLD) received
2009/09/23 23:54:47 [notice] 20867#0: worker process 20873 exited with code 0

Это признак какой-то проблемы?
Я сейчас добавил в конфиг "debug_points abort", но дампов пока не
получал. Не подскажите как они включаются и где их искать?

Вы писали 25 сентября 2009 г., 20:03:14:

> On Thu, Sep 24, 2009 at 07:50:29PM +0400, jchannelx wrote:

>> >    *) Исправление: ошибки при использовании post_action; ошибка появилась
>> >       в 0.8.11.
>> >       Спасибо Игорю Артемьеву.
>> >
>> 
>> ок, обновился, writes всё равно растет. Откачусь на 0.8.7 пожалуй.

> Откатится можно к 0.8.10 (с патчем VU#180065, разумеется).

> Но лучше попытаться найти ошибку. Если по завершении работы воркер
> находит незакрытые соединения он пишет в лог примерно следующее:

> 2009/09/24 13:53:08 [alert] 53296#0: open socket #7205 left in connection 2991
> 2009/09/24 13:53:08 [alert] 53296#0: open socket #9863 left in connection 3543
> 2009/09/24 13:53:08 [alert] 53296#0: open socket #16078 left in connection 
> 6668
> 2009/09/24 13:53:08 [alert] 53296#0: open socket #14637 left in connection 
> 11750
> 2009/09/24 13:53:08 [alert] 53296#0: open socket #9718 left in connection 
> 13532
> 2009/09/24 13:53:08 [alert] 53296#0: aborting

> Для того, чтобы "aborting" действительно случился, нужно

> 1) nginx должен быть собран и установлен с отладочной информацией (не
> путать с --with-debug), по умолчанию он так и собирается (ключ gcc -g), если
> только в пакете что-то не поменяли.

> 2) добавить в nginx.conf:

> debug_points abort;

> 3) разрешить создание coredumps.

> Ну а потом будем рассматривать корку.




-- 
С уважением,
 Den                          mailto:dsdiv@xxxxxxxxxx




 




Copyright © Lexa Software, 1996-2009.