I just found something interest in "dmesg" log:
[5294633.862284] __ratelimit: 20 callbacks suppressed
[5294633.862288] nginx[20568]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a1a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294634.659735] nginx[20569]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a0a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294634.818078] nginx[20571]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a0a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294634.819429] nginx[20581]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a0a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294634.920149] nginx[20567]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a0a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294635.313816] nginx[20589]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a0a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294635.402682] nginx[20590]: segfault at aa ip 00007fdc5a44eb41 sp
00007fff0260a0a8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294682.926163] nginx[20596]: segfault at 4a ip 00000000004459df sp
00007fff0260a0f0 error 4 in nginx[400000+a3000]
[5294685.155117] nginx[20595]: segfault at 4a ip 00000000004459df sp
00007fff0260a280 error 4 in nginx[400000+a3000]
[5294686.158466] nginx[21276]: segfault at 4a ip 00000000004459df sp
00007fff0260a130 error 4 in nginx[400000+a3000]
[5294688.683947] nginx[21313]: segfault at 1 ip 00007fdc5a44eb41 sp
00007fff0260a0c8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]
[5294695.987059] nginx[21361]: segfault at 1193d ip 00007fdc5a44eb41 sp
00007fff0260a0c8 error 6 in libc-2.11.3.so[7fdc5a3cf000+159000]

Seems to be a error in libc...

-----Ursprüngliche Nachricht-----
Von: nginx-bounces@nginx.org [mailto:nginx-bounces@nginx.org] Im Auftrag von
Lukas Tribus
Gesendet: Montag, 07. Jänner 2013 10:37
An: nginx@nginx.org
Betreff: RE: AW: Webserver crashes sometimes - don't know why


Well, actually you have to recompile the source-code and configure it with
--with-debug AND enable the debug command behind error.log (see link [1] at
the bottom of the mail).

Obviously this will log a huge amounts of data, so make sure you are
filesystem can cope with the amount of data logged.


[1] http://nginx.org/en/docs/debugging_log.html




----------------------------------------
> From: info@pkern.at
> To: nginx@nginx.org
> Subject: AW: Webserver crashes sometimes - don't know why
> Date: Mon, 7 Jan 2013 10:18:26 +0100
>
> Hi Lukas,
>
> No, I currently have the latest development version from svn of
> 01.01.2013
> - 1.3.11. (Revision 5001).
> I only have one installed module: headers more
>
> Have I add "debug" behind error.log? I currently have it without debug
> and I don't see any information about the crash.
>
> Thanks for your help :)
>
> Greets,
> Patschi
>


_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx