[Python-Dev] Failed issue tracker submission

R. David Murray rdmurray at bitdance.com
Thu Apr 5 04:17:45 CEST 2012


On Thu, 05 Apr 2012 01:29:47 -0000, Python tracker <roundup-admin at psf.upfronthosting.co.za> wrote:
> 
> An unexpected error occurred during the processing
> of your message. The tracker administrator is being
> notified.

Since the bounce message went here, I'm posting this here for those who
are curious what caused it.

It was triggered by my committing a patch with two issue numbers in the
commit message.  This triggered a DB lock problem on the roundup end,
from the xapian indexer:

Traceback (most recent call last):
  File "/home/roundup/lib/python2.5/site-packages/roundup/mailgw.py", line 1395,
  in handle_Message
    return self.handle_message(message)
  File "/home/roundup/lib/python2.5/site-packages/roundup/mailgw.py", line 1451,
  in handle_message
    return self._handle_message(message)
  File "/home/roundup/lib/python2.5/site-packages/roundup/mailgw.py", line 1529,
  in _handle_message
    parsed_message.create_msg()
  File "/home/roundup/lib/python2.5/site-packages/roundup/mailgw.py", line 1105,
  in create_msg
    messageid=messageid, inreplyto=inreplyto, **self.msg_props)
  File "/home/roundup/lib/python2.5/site-
  packages/roundup/backends/rdbms_common.py", line 2958, in create
    content, mime_type)
  File "/home/roundup/lib/python2.5/site-
  packages/roundup/backends/indexer_xapian.py", line 59, in add_text
    database = self._get_database()
  File "/home/roundup/lib/python2.5/site-
  packages/roundup/backends/indexer_xapian.py", line 21, in _get_database
    return xapian.WritableDatabase(index, xapian.DB_CREATE_OR_OPEN)
  File "/usr/lib/python2.6/dist-packages/xapian/__init__.py", line 4059, in
  __init__
    _xapian.WritableDatabase_swiginit(self,_xapian.new_WritableDatabase(*args))
DatabaseLockError: Unable to get write lock on /home/roundup/trackers/tracker/db
/text-index: already locked

The Xapian index is new since the server upgrade, so it is possible this will
always happen when more than one issue number is mentioned.  Or it could
be a random timing thing.  Presumably it could also occur during normal
web submissions if they happen to happen at the same time, which is
a little bit worrisome.

If anyone has any Xapien experience and would be willing to help out with
debugging this and/or some indexing issues, please let me know :)

--David


More information about the Python-Dev mailing list