Welcome! Log In Create A New Profile

Advanced

Re: POST causes segfault (502 'upstream prematurely closed connection')

August 12, 2009 08:18AM
Maxim Dounin Wrote:
-------------------------------------------------------
> Hello!

[ .. ]
> > The nginx access log file shows a 502 response, and Apache doesn't register a hit.
> >
> > Nginx error log: "upstream prematurely closed connection while reading response header from upstream"]
> > Apache log: " child pid 5566 exit signal Segmentation fault (11)"

[ .. ]
> .. probably the only part of the investigation
> relevant to this
> list is what triggers problem and possible
> workarounds (if any).

In my case the cause is what looks like a bug in mod_perl2. The object handling request parameters (Apache2::Request) failed to initialise where expected. I have not been able to create a proper test case for it as it needs a quite specific scenario. If anyone is interested I can email then more details, anything posted on here would be out of context.

Thanks for your time and help.
Subject Author Posted

POST causes segfault (502 'upstream prematurely closed connection')

miradev August 04, 2009 07:32AM

Re: POST causes segfault (502 'upstream prematurely closed connection')

Maxim Dounin August 06, 2009 04:46PM

Re: POST causes segfault (502 'upstream prematurely closed connection')

miradev August 12, 2009 08:18AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 287
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