ПРОЕКТЫ 


  АРХИВ 


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 + default {deferred|bind} = корки


  • To: nginx-ru@xxxxxxxxx
  • Subject: Re: nginx + default {deferred|bind} = корки
  • From: Roxis <roxis@xxxxxxx>
  • Date: Tue, 29 May 2007 18:56:27 +0200
  • Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:references:in-reply-to:x-mailer:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=dzrdu0AShFKG0+3aowic4iPPmpq3CvsXDgHVo9F1FN6QDO/X57PcR07zvgh9YtEXsKQqNkxvcZhJ1+o5wxed5XFw8zEJrgdel8PwhOoHLl//n7wbFVGN3FuGq7AMx0HneyR6oELVQisUJCHTZ/XLbdRXOiw2Zo7wY7ffQfKPiWs=
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:references:in-reply-to:x-mailer:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=A2x12t1tJXG1XwVGE5vRKT0B5TbauTc6WXRDcYq6je6TWKhym1xwKcqs9ldWs/lQCSrWRk2Qggaz8ynPO30XBUF5op+qIbL1Z1ZjBuw7XvZT+gj8obkUwm7H4ZpNSuGepZT2/zL4lNhDvsnaC1f2jN3Zp5zXWtTAUoEzU2VvVus=
  • In-reply-to: <20070529163205.GI79693@xxxxxxxxxxxxx>
  • References: <46515618.4070108@xxxxxxxxxx> <465C3275.5020408@xxxxxxxxxx> <20070529163205.GI79693@xxxxxxxxxxxxx>

On Tuesday 29 May 2007, Igor Sysoev wrote:
> Прилагаемый патч должее пофиксить segfault.
>
> > >nest tmp # uname -srm
> > >Linux 2.6.20.3-grsec x86_64
> > >
> > >аналогичное поведение при замене deferred на bind
> >
> > на i386 - ругань в логи после попытки запуска
> > 2007/05/29 08:59:28 [emerg] 12979#0: bind() to 127.0.0.1:80 failed (98:
> > Address already in use)
> > 2007/05/29 08:59:28 [emerg] 12979#0: still could not bind()
> >
> > Это вообще нормальное поведение при таком конфиге? Как я понимаю,
> > проблема в неверном порядке bind()
>
> FreeBSD позволяет bind() to 127.0.0.1:80 и *:80 в любом порядке.
> Насчёт Линукса - нужно проверить.

с патчем:

2007/05/29 18:52:14 [alert] 20406#0: changing the listen() backlog to -1 for 
0.0.0.0:80 failed, ignored (98: Address already in use)
2007/05/29 18:52:14 [debug] 20408#0: epoll add event: fd:4 op:1 ev:00000001
2007/05/29 18:52:14 [debug] 20408#0: epoll add event: fd:5 op:1 ev:00000001
2007/05/29 18:52:14 [debug] 20408#0: post event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: delete posted event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: accept on 0.0.0.0:80, ready: 0
2007/05/29 18:52:14 [alert] 20408#0: accept() failed (22: Invalid argument) 
while accepting new connection on 0.0.0.0:80
2007/05/29 18:52:14 [debug] 20408#0: post event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: delete posted event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: accept on 0.0.0.0:80, ready: 0
2007/05/29 18:52:14 [alert] 20408#0: accept() failed (22: Invalid argument) 
while accepting new connection on 0.0.0.0:80
2007/05/29 18:52:14 [debug] 20408#0: post event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: delete posted event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: accept on 0.0.0.0:80, ready: 0
2007/05/29 18:52:14 [alert] 20408#0: accept() failed (22: Invalid argument) 
while accepting new connection on 0.0.0.0:80
2007/05/29 18:52:14 [debug] 20408#0: post event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: delete posted event 080CEEB4
2007/05/29 18:52:14 [debug] 20408#0: accept on 0.0.0.0:80, ready: 0
2007/05/29 18:52:14 [alert] 20408#0: accept() failed (22: Invalid argument) 
while accepting new connection on 0.0.0.0:80

и так до бесконечности, и очень быстро




 




Copyright © Lexa Software, 1996-2009.