An unexpected error occurred during the processing of your message. The tracker administrator is being notified.
Return-Path: python-dev@python.org X-Original-To: report@bugs.python.org Delivered-To: roundup+tracker@psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id 18F1D1CA8A for report@bugs.python.org; Thu, 5 Apr 2012 03:29:47 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3VNRKk5ffZzMDH for report@bugs.python.org; Thu, 5 Apr 2012 03:29:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1333589386; bh=mxZYtp1PNBk7+3KkQ2c0Ir4UpBYOh1g7JxosMonW0bg=; h=Date:Message-Id:Content-Type:MIME-Version: Content-Transfer-Encoding:From:To:Subject; b=dkAMMMzcIiS6RnMbU2X82n0soHqci8LQJeJZtQefi9I0bhSh9IbG/qrBrdjTdG3sE QOAeN4ttDr5vy83SY7pcXGH4sXVAlMGHAwKPUcOYRFIHKzKoy/gNwOfPRRIdxDg3C0 Go6dQtIJi0j/uS4EI9o7oEJHVczuzJLkdGRcA6ik= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 05 Apr 2012 03:29:46 +0200 Received: from dinsdale.python.org (svn.python.org [IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for report@bugs.python.org; Thu, 5 Apr 2012 03:29:46 +0200 (CEST) Received: from localhost ([127.0.0.1] helo=dinsdale.python.org ident=hg) by dinsdale.python.org with esmtp (Exim 4.72) (envelope-from python-dev@python.org) id 1SFbWE-0008LO-KB for report@bugs.python.org; Thu, 05 Apr 2012 03:29:46 +0200 Date: Thu, 05 Apr 2012 03:29:46 +0200 Message-Id: E1SFbWE-0008LO-KB@dinsdale.python.org Content-Type: text/plain; charset="utf8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 From: python-dev@python.org To: report@bugs.python.org Subject: [issue14490]
TmV3IGNoYW5nZXNldCA2MmRkZTVkZDQ3NWUgYnkgUiBEYXZpZCBNdXJyYXkgaW4gYnJhbmNoICcz LjInOgojMTQ0OTAsICMxNDQ5MTogYWRkICdzdW5kcnknLXN0eWxlIGltcG9ydCB0ZXN0cyBmb3Ig VG9vbHMvc2NyaXB0cy4KaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvNjJkZGU1ZGQ0 NzVlCgoKTmV3IGNoYW5nZXNldCA2OTZjYjUyNDMyMmEgYnkgUiBEYXZpZCBNdXJyYXkgaW4gYnJh bmNoICdkZWZhdWx0JzoKTWVyZ2UgIzE0NDkwLCAjMTQ0OTE6IGFkZCAnc3VuZHJ5Jy1zdHlsZSBp bXBvcnQgdGVzdHMgZm9yIFRvb2xzL3NjcmlwdHMuCmh0dHA6Ly9oZy5weXRob24ub3JnL2NweXRo b24vcmV2LzY5NmNiNTI0MzIyYQo=
On Thu, 05 Apr 2012 01:29:47 -0000, Python tracker roundup-admin@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
-
Python tracker -
R. David Murray