apache2 crashed with SIGABRT in Py_FatalError()

Bug #1054888 reported by peter swain on 2012-09-23
This bug affects 7 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)

Bug Description

fresh upgrade of precise -> quantal
have not touched apache config, or used self-hosted pages, for months

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apache2.2-bin 2.2.22-6ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Sun Sep 23 00:25:40 2012
ExecutablePath: /usr/lib/apache2/mpm-itk/apache2
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/sbin/apache2 -k start
 PATH=(custom, no user)
Signal: 6
SourcePackage: apache2
 Py_FatalError () from /usr/lib/libpython2.7.so.1.0
 PyEval_AcquireThread () from /usr/lib/libpython2.7.so.1.0
 ?? () from /usr/lib/apache2/modules/mod_wsgi.so
 ?? () from /usr/lib/libapr-1.so.0
 apr_pool_destroy () from /usr/lib/libapr-1.so.0
Title: apache2 crashed with SIGABRT in Py_FatalError()
UpgradeStatus: Upgraded to quantal on 2012-09-20 (2 days ago)

peter swain (swine) wrote :

 Py_FatalError (msg=msg@entry=0xb71b121c "PyEval_AcquireThread: NULL new thread state") at ../Python/pythonrun.c:1689
 PyEval_AcquireThread (tstate=0x0) at ../Python/ceval.c:272
 ?? () from /tmp/tmpikWWC9/usr/lib/apache2/modules/mod_wsgi.so
 run_cleanups () from /tmp/tmpikWWC9/usr/lib/libapr-1.so.0
 apr_pool_destroy () from /tmp/tmpikWWC9/usr/lib/libapr-1.so.0

Changed in apache2 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in apache2 (Ubuntu):
status: New → Confirmed
Dimitri John Ledkov (xnox) wrote :

Got same thing in saucy now.

Hmm... apache is out of sync with python again?!

martin suc (martin-suc) wrote :

again in utopic ubuntu 14.10

Bryce Harrington (bryce) wrote :

Closing as expired, this appears to be an incompatibility between apache2.2 and python2, but Ubuntu's focus for maintenance is on 2.4 and 3.x now.

Changed in apache2 (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers