[Numpy-discussion] Temporary error accessing NumPy tickets

Pauli Virtanen pav@iki...
Fri Aug 31 11:35:50 CDT 2012


Ondřej Čertík <ondrej.certik <at> gmail.com> writes:
> When I access tickets, for example:
> 
> http://projects.scipy.org/numpy/ticket/2185
> 
> then sometimes I get:
> 
> Trac detected an internal error:
> OperationalError: database is locked
> 
> For example yesterday. A refresh in about a minute fixed the problem.
> Today it still lasts at the moment.

The failures are probably partly triggered by the machine running out of memory.
It runs services on mod_python, which apparently slowly leaks. Someone (who?)
with root access on the machine needs to restart Apache. (Note: "apachectl
graceful" is not enough to correct this, it needs a real restart of the process.)

Longer term solution is to move out of mod_python (mod_wsgi likely, going to CGI
will create other performance problems), or to transition the stuff there to a
more beefy server.

-- 
Pauli Virtanen



More information about the NumPy-Discussion mailing list