nginx segfaults when a try_files directive is used

[Neil Bertram]

There is an unpatched bug present in the version of Nginx that ships with Precise (at least version 1.1.19-1 on AMD64).

The upstream bug report (closed/fixed already) is http://trac.nginx.org/nginx/ticket/152

The bug was fixed upstream in 1.1.20 and beyond.

It causes an nginx worker crash with something similar to:

2012/09/05 16:25:12 [alert] 12295#0: worker process 12370 exited on signal 11 (core dumped)

in syslog.

The client sees a "no data" response when this happens.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nginx-full 1.1.19-1
ProcVersionSignature: Ubuntu 3.2.0-27.43-virtual 3.2.21
Uname: Linux 3.2.0-27-virtual x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Wed Sep 5 16:46:15 2012
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 TERM=xterm
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: nginx
UpgradeStatus: Upgraded to precise on 2012-08-07 (28 days ago)

[Thomas Ward (teward)]

Can you include a sample of what your "try_files" item states? I have tested with static HTML running slightly dynamic content on my testing system, and this was not able to be reproduced.

[Thomas Ward (teward)]

Note that using the sample(s) provided by the ticket, this is not reproducible in Precise on my testing system.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Artem V. Ryabov (avryabov)]

On nginx support site wrote:
"Please update your nginx first.
Nginx 1.1.19 is known as unstable."

http://trac.nginx.org/nginx/ticket/218

[Michael Lustfield (michaellustfield)]

Thomas and I will look into pushing http://trac.nginx.org/nginx/changeset/4601/nginx through the SRU process.

[Thomas Ward (teward)]

I am setting this as Triaged as it is now awaiting someone to take up fixing it.

[Thomas Ward (teward)]

This is being fixed in Bug #1065555. The nginx trac bug referenced here refers to upstream Changeset 4601, which is being applied by #1065555's SRU. I'm going to mark this as a duplicate of that bug, so we can track update status in that bug.