nginx segfaults when a try_files directive is used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nginx (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Precise |
Triaged
|
Medium
|
Unassigned | ||
Quantal |
Fix Released
|
Low
|
Unassigned |
Bug Description
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://
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
ProcVersionSign
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)
Changed in nginx (Ubuntu): | |
importance: | Undecided → Low |
Changed in nginx (Ubuntu Precise): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in nginx (Ubuntu Quantal): | |
status: | Triaged → Fix Released |
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.