ПРОЕКТЫ 


  АРХИВ 


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]

nginx segfault



Периодически появляются следующие ошибки:

xserv:/var/log# grep nginx /var/log/messages
Jun  3 16:55:56 xserv kernel: nginx[12535]: segfault at 00000014 eip 0805e6d5 
esp bfa37b60 error 6
Jun  3 19:18:04 xserv kernel: nginx[13458]: segfault at 000001a4 eip 08079f87 
esp bfa37ba0 error 4
Jun  3 20:09:48 xserv kernel: nginx[13456]: segfault at 00000000 eip 0804ce5f 
esp bfa37ab0 error 4
xserv:/var/log# grep '20:09:48' /var/log/nginx/error.log
2008/06/01 20:09:48 [error] 3478#0: *9785550 directory index of 
"/home/blablabla/htdocs/images/" is forbidden, client: xxx.xxx.xxx.xxx, server: 
blablabla.org, request: "GET /images/ HTTP/1.1", host: "blablabla.org", 
referrer: "http://blablabla.org/";
2008/06/03 20:09:48 [error] 13456#0: *21890783 upstream sent too big header 
while reading response header from upstream, client: xxx.xxx.xxx.xxx server: 
blablabla.org, request: "GET /parse.php?sid=d7b6c21f351510c5910af54f2bc7e083 
HTTP/1.1", upstream: "fastcgi://unix:/tmp/php.sock:", host: "blablabla.org"
2008/06/03 20:09:48 [alert] 13456#0: *21890783 recv() failed (95: Operation not 
supported) while reading response header from upstream, client: 
xxx.xxx.xxx.xxx, server: 0.0.0.0:80
2008/06/03 20:09:48 [alert] 3472#0: worker process 13456 exited on signal 11
2008/06/03 20:09:48 [error] 24328#0: *21891995 directory index of 
"/home/blablabla/htdocs/images/" is forbidden, client: xxx.xxx.xxx.xxx, server: 
blablabla.org, request: "GET /images/ HTTP/1.1", host: "blablabla.org", 
referrer: "http://blablabla.org/";

nginx 0.6.31
debian etch, kernel 2.6.24.3

насколько я понимаю проблема не критическая, но интересует почему nginx не 
может нормально обработать ошибку с парсингом больших хидеров?

-- 



 




Copyright © Lexa Software, 1996-2009.