Nginx-ru mailing list archive (nginx-ru@sysoev.ru)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
worker process N exited on signal 11
- To: nginx-ru@xxxxxxxxx
- Subject: worker process N exited on signal 11
- From: "paranoidchaos" <nginx-forum@xxxxxxxx>
- Date: Thu, 04 Nov 2010 09:26:47 -0400
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mickey.jlkhosting.com; s=x; h=Sender:From:Message-ID:Content-Transfer-Encoding:Content-Type:Subject:To:Date; bh=XJ+9dN2ZGIBydMNkeUlJXqN9pz1NptuuEbiPsrIV5jU=; b=H9HFavj7WCQoc/2VTF8U85EBjxUDhWOKbIhzE3NTMTqTmwg6+VKEHz80OXu+l2dxtVxrPBkrZHJvCUmi+EpPeSj48YPubK8HAR7R0cdQyvQpXLXffp9cRVY4v40i8Zb5;
Здравствуйте
наблюдал за графиком активности nginx (в
munin) и вдруг график NGINX STATUS (Active connections,
Reading, Writing, Waiting) лавинообразно зашкалил
до 800 connections хотя на графике NGINX REQUESTS всё
было в норме в среднем 20 r/s.
полез в логи
вот после этой строки
[color=#FF0000]2010/11/04 16:48:12 [alert] 2315#0: *54931098 writev()
failed (22: Invalid argument) while sending to client, client: 81.20
0.59.198, server: _, request: "GET
/index.php?id=1587&qid=12&ssid=NULL%20LIMIT%200%20UNION%20SELECT%20CHAR%2853%2C88%2C55%2
C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%
2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55
%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C5
5%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C
55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2
C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%
2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88
%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C8
8%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C
88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2
C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%
2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853
%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%285
3%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%28
53%2C88%2C55%2C80%2C81%2C100%2C106%2C99%2C79%2C51%29%2CCHAR%2853%2C88%2C55%2C80[/color]
в логах пошёл сегфолт
[color=#FF0000]*** glibc detected *** nginx: worker process: free():
invalid next size (fast): 0x0000000000efedb0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x338727230f]
/lib64/libc.so.6(cfree+0x4b)[0x338727276b]
nginx: worker process[0x41753f]
nginx: worker process[0x4175a9]
nginx: worker process[0x406e04]
nginx: worker process[0x42cb2a]
nginx: worker process[0x42cc0d]
nginx: worker process[0x42ec05]
nginx: worker process[0x42f043]
nginx: worker process[0x42b21d]
nginx: worker process[0x4269a3]
nginx: worker process[0x426ace]
nginx: worker process[0x42f57c]
nginx: worker process[0x42fd90]
nginx: worker process[0x430292]
nginx: worker process[0x42d94e]
nginx: worker process[0x41980e]
nginx: worker process[0x4196d0]
nginx: worker process[0x41eea0]
nginx: worker process[0x41d7e7]
nginx: worker process[0x41f689]
nginx: worker process[0x4062da]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x338721d994]
nginx: worker process[0x404ad9]
2010/11/04 16:49:37 [alert] 17423#0: worker process 2315 exited on
signal 6
2010/11/04 16:53:23 [alert] 14441#0: ignore long locked inactive cache
entry b4599f772edd34815a86c4042662502c, count:1
2010/11/04 16:53:48 [alert] 14441#0: ignore long locked inactive cache
entry 39a531d13533cbc8c5fb9887af19d8ed, count:1
2010/11/04 16:53:49 [alert] 14441#0: ignore long locked inactive cache
entry 773ed85e18dad90a7a7bdde02018bb59, count:1
2010/11/04 16:53:50 [alert] 14441#0: ignore long locked inactive cache
entry b255244ed026b89709fcd3bf43bb7ae4, count:1
2010/11/04 16:53:50 [alert] 14441#0: ignore long locked inactive cache
entry bd1cc3babc95a3799cfdff7609cdd39c, count:1
2010/11/04 16:54:07 [alert] 14441#0: ignore long locked inactive cache
entry d9a2c468a65727016e081d9a279b1814, count:1
2010/11/04 16:54:15 [alert] 14441#0: ignore long locked inactive cache
entry bcfe91f4823d8f129ff448bc5248b2ec, count:1
2010/11/04 16:54:17 [alert] 14441#0: ignore long locked inactive cache
entry f868e840b9330c3f63364760cd65a2ba, count:1
2010/11/04 16:54:33 [alert] 14441#0: ignore long locked inactive cache
entry 857393a91f72db369d184e2e033d6e3f, count:1
2010/11/04 16:54:35 [alert] 14441#0: ignore long locked inactive cache
entry 6a87a1670bfff5e6190a76705bcaaa6e, count:1[/color]
перезапуск ничего не изменил - опять
посыпались строки вида
[color=#FF0000]2010/11/04 16:54:35 [alert] 14441#0: ignore long locked
inactive cache entry 6a87a1670bfff5e6190a76705bcaaa6e, count:1[/color]
пришлось очистить вручную кеш
что произошло ?
пс: врубит отладку пока не могу -
рабочий сервер
пс2: решил поверить - ввожу данный
кривой запрос но ничего не происходит
Posted at Nginx Forum:
http://forum.nginx.org/read.php?21,147599,147599#msg-147599
_______________________________________________
nginx-ru mailing list
nginx-ru@xxxxxxxxx
http://nginx.org/mailman/listinfo/nginx-ru
|
