Welcome! Log In Create A New Profile

Advanced

Re: nginx crash

Maxim Dounin
November 23, 2011 07:30AM
Hello!

On Wed, Nov 23, 2011 at 04:01:29AM +0000, António P. P. Almeida wrote:

> On 14 Nov 2011 16h57 WET, magicbearmo@gmail.com wrote:
>
> > Hello,
> >
> > I think is also not relative to crash, when I increase the zone key
> > size, crash hasn't happen again (but my upstream are also up), so I
> > still unknown where has the crash happen.
> > Just I had update all of my server to 1.1.8, I want to test for your
> > config because some of my server has running dynamic page, and they
> > aren't return the Content-Length.
>
> I'm having a similar issue. The php-fpm workers stop responding and
> since the FCGI cache lifetime is 15s I get a bunch of SEGVs on the
> cache manager.

By "lifetime" you mean "fastcgi_cache_path ... inactive=15s"?

If yes, than you may want to change your configuration: this isn't
going to work well as nginx uses "inactive" as a guard against
stale cache entry locks (left by crashed workers, if any). It
was never expected to be lower than time required to fetch
a resource from an upstream, and setting it to lower expected to
cause problems.

If no, you may want to provide more details. (Ideally I would
like to see full debug log showing the crash, the "ignore long
locked inactive cache entry" alert and some time before it, but I
understand it would be hard to obtain unless you are able to
reproduce the problem at will.)

> I'm increasing the cache keys zone size from 5M to 10M. I know you
> guys at nginx.com are busy people, but please look into this issue. Is
> really making Nginx sensitive to failings in apps. Which it shouldn't
> be since there's a clear separation between app and server. That's
> IMHO one big selling point, among many others of course.

Recently posted patch series[1] addresses major part of the
problem: it resolves deadlock after such crashes. It would be
fine to resolve the crash itself too, but I wasn't yet able to
trace the problem cause (unless it's caused by too low inactive
time, which is mostly a configuration problem, see above).

[1] http://mailman.nginx.org/pipermail/nginx-devel/2011-November/001471.html

Maxim Dounin

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

nginx crash

magicbear 4942 November 12, 2011 06:16AM

Re: nginx crash

magicbear 2028 November 12, 2011 09:08AM

Re: nginx crash

Maxim Dounin 1267 November 12, 2011 11:18AM

Re: nginx crash

magicbear 1593 November 12, 2011 02:06PM

Re: nginx crash

António P. P. Almeida 1068 November 13, 2011 06:18PM

Re: nginx crash

Maxim Dounin 1127 November 13, 2011 06:56PM

Re: nginx crash

ビリビリⅤ 1016 November 14, 2011 11:14AM

Re: nginx crash

Maxim Dounin 1070 November 14, 2011 11:52AM

Re: nginx crash

magicbear 1133 November 14, 2011 11:58AM

Re: nginx crash

António P. P. Almeida 748 November 22, 2011 11:04PM

Re: nginx crash

Maxim Dounin 1019 November 23, 2011 07:30AM

Re: nginx crash

António P. P. Almeida 1032 November 23, 2011 03:22PM

Re: nginx crash

Maxim Dounin 928 November 23, 2011 04:54PM

Re: nginx crash

António P. P. Almeida 884 November 24, 2011 03:32AM

Re: nginx crash

magicbear 1293 November 26, 2011 09:08AM

Re: nginx crash

Maxim Dounin 1289 November 28, 2011 02:16PM

Re: nginx crash

Andrew Alexeev 886 November 23, 2011 07:32AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 159
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready