[Bug 759943] Re: mod_wsgi.so-3.2 gives errors

[James Page]

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)


** Changed in: mod-wsgi (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/759943

Title:
  mod_wsgi.so-3.2 gives errors