Re: exited on signal 11

[proforg <proforg@xxxxxxxxxxxx>]

хм, у меня в логах по утрам  пишет 
2005/12/05 08:18:46 [notice] 22005#0: signal 17 (SIGCHLD) received
2005/12/05 08:18:46 [alert] 22005#0: worker process 11598 exited on signal 6 (core dumped)
2005/12/05 08:18:46 [notice] 22005#0: signal 29 (SIGIO) received

(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7bb0691 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7bb1f5b in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0x080916f5 in ngx_worker_process_exit.133 (cycle=0x916f500) at ngx_process_cycle.c:952
#4  0x08053ec8 in ngx_worker_process_cycle.133 (cycle=0x0, data="" at ngx_process_cycle.c:733
#5  0x0804ded5 in ngx_spawn_process (cycle=0x0, proc=0x6,
data="" name=0x83f42a0 "HM?\b\200B?\bдL?\bдL?\b", respawn=0) at
ngx_process.c:187
#6  0x0804d4bd in ngx_master_process_cycle (cycle=0x0) at ngx_process_cycle.c:219
#7  0x0804a9f1 in main (argc=138366148, argv=0x83f4cc4) at nginx.c:295

хотя может это и нормально :)

 Профорг

On 12/5/05, Igor Sysoev <is@xxxxxxxxxxxxx> wrote:

On Mon, 5 Dec 2005, Alexey Polyakov wrote:

> On 12/5/05, Igor Sysoev <is@xxxxxxxxxxxxx> wrote:
>>
>> Нет, обидная. Такого быть не должно. Нужны core файлы.
>
> А как их разрешить делать?

sysctl kern.sugid_coredump=1
sysctl kern.corefile=/spool/core/%N.core.%P

Пользователь, под которым работают worler'ы nginx'а, должен иметь
право записи в /spool/core/.


Игорь Сысоев
http://sysoev.ru