mod_wsgi.so-3.2 gives errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mod-wsgi (Ubuntu) |
Fix Released
|
Medium
|
James Page |
Bug Description
When mod_wsgi.so links to mod_wsgi.so-3.2, apache2 throws error messages:
# ls /usr/lib/
lrwxrwxrwx 1 root root 40 2011-04-13 17:45 /usr/lib/
-rw-r--r-- 1 root root 156320 2011-04-07 14:10 /usr/lib/
-rw-r--r-- 1 root root 156320 2011-04-07 14:10 /usr/lib/
# tail -f /var/log/
[Wed Apr 13 17:45:05 2011] [notice] Apache/2.2.17 (Ubuntu) mod_wsgi/3.3 Python/3.2 configured -- resuming normal operations
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Wed Apr 13 17:45:07 2011] [notice] child pid 6114 exit signal Aborted (6)
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Wed Apr 13 17:45:09 2011] [notice] child pid 6257 exit signal Aborted (6)
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Wed Apr 13 17:45:11 2011] [notice] child pid 6321 exit signal Aborted (6)
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Wed Apr 13 17:45:13 2011] [notice] child pid 6355 exit signal Aborted (6)
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Wed Apr 13 17:45:15 2011] [notice] child pid 6432 exit signal Aborted (6)
...
Linking to mod_wsgi.so-3.1 fixes this for me.
# cp -sf /usr/lib/
# ls /usr/lib/
lrwxrwxrwx 1 root root 40 2011-04-13 17:50 /usr/lib/
-rw-r--r-- 1 root root 156320 2011-04-07 14:10 /usr/lib/
-rw-r--r-- 1 root root 156320 2011-04-07 14:10 /usr/lib/
# service apache2 restart
# tail -f /var/log/
[Wed Apr 13 17:50:42 2011] [notice] Apache/2.2.17 (Ubuntu) mod_wsgi/3.3 Python/3.1.3 configured -- resuming normal operations
Related branches
- Dave Walker (community): Approve
-
Diff: 30671 lines (+15427/-15024)9 files modified.pc/.version (+0/-1)
.pc/applied-patches (+0/-1)
.pc/fix-python-3.2-lp-749720.patch/mod_wsgi.c (+0/-14969)
.pc/python-3.2-compat.patch/mod_wsgi.c (+14969/-0)
debian/changelog (+10/-0)
debian/patches/fix-python-3.2-lp-749720.patch (+0/-45)
debian/patches/python-3.2-compat.patch (+327/-0)
debian/patches/series (+0/-1)
mod_wsgi.c (+121/-7)
tags: | added: server-nrs |
Changed in mod-wsgi (Ubuntu): | |
importance: | Undecided → Medium |
Changed in mod-wsgi (Ubuntu): | |
milestone: | none → ubuntu-11.04 |
Changed in mod-wsgi (Ubuntu): | |
assignee: | nobody → James Page (james-page) |
Changed in mod-wsgi (Ubuntu): | |
status: | Confirmed → In Progress |
tags: | added: patch |
Confirm on up-to-date Natty amd64:
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Fri Apr 15 15:29:21 2011] [notice] Apache/2.2.17 (Ubuntu) mod_wsgi/3.3 Python/3.2 configured -- resuming normal operations
[Fri Apr 15 15:29:21 2011] [notice] child pid 4480 exit signal Aborted (6)
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Fri Apr 15 15:29:22 2011] [notice] child pid 4479 exit signal Aborted (6)
[Fri Apr 15 15:29:35 2011] [notice] SIGUSR1 received. Doing graceful restart
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Fri Apr 15 15:29:35 2011] [notice] Apache/2.2.17 (Ubuntu) mod_wsgi/3.3 Python/3.2 configured -- resuming normal operations
[Fri Apr 15 15:29:35 2011] [notice] child pid 4560 exit signal Aborted (6)
Fatal Python error: PyEval_AcquireLock: current thread state is NULL
[Fri Apr 15 15:29:36 2011] [notice] child pid 4590 exit signal Aborted (6)