Mailman error (2.1.16): "low level unrecoverable exception"
What does this error message mean? "low level unrecoverable exception"
I just installed my own build of mailman 2.1.16 (built under CentOS 5 x84_64) as an upgrade over the stock 2.1.9 that comes with CentOS 5 and I am getting this error. What should I be looking for?
-- Robert Heller -- 978-544-6933 / heller@deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
On 04/30/2014 11:30 AM, Robert Heller wrote:
What does this error message mean? "low level unrecoverable exception"
It means something really bad happened. One of the Mailman web CGIs threw an exception and the CGI driver script encountered another exception while trying to log a traceback and the environment info.
I just installed my own build of mailman 2.1.16 (built under CentOS 5 x84_64) as an upgrade over the stock 2.1.9 that comes with CentOS 5 and I am getting this error. What should I be looking for?
Did you restart Mailman or stop before, start after?
Did you totally remove the Centos package or try to 'upgrade' it. The latter is not at all straightforward. See the FAQ at http://wiki.list.org/x/KYCB.
There was an issue a while back, see https://mail.python.org/pipermail/mailman-users/2005-November/047814.html, but this was due to a SuSE patch that referenced a Python xml library that wasn't installed. The specifics aren't relevant to your issue, but it could indicate there's something missing in your python. Have you installed the python-dev package?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
At Wed, 30 Apr 2014 14:34:51 -0700 Mark Sapiro mark@msapiro.net wrote:
On 04/30/2014 11:30 AM, Robert Heller wrote:
What does this error message mean? "low level unrecoverable exception"
It means something really bad happened. One of the Mailman web CGIs threw an exception and the CGI driver script encountered another exception while trying to log a traceback and the environment info.
I just installed my own build of mailman 2.1.16 (built under CentOS 5 x84_64) as an upgrade over the stock 2.1.9 that comes with CentOS 5 and I am getting this error. What should I be looking for?
Did you restart Mailman or stop before, start after?
I believe the install scripts in the RPM stop and restart Mailman. But I will do an explicit shutdown of Mailman before the upgrade when I try it again.
Did you totally remove the Centos package or try to 'upgrade' it. The latter is not at all straightforward. See the FAQ at http://wiki.list.org/x/KYCB.
That page relates to upgrading from 2.1.5-20 or earlier. I was upgrading from 2.1.9, so that does not apply (?). When I did an upgrade to 2.1.16 from an 'bare' install of 2.1.9 on my home system, there weren't any (major) problems. And a fresh install of 2.1.16 (on another machine) had no problems either.
Ok, I did an explict stop of mailman, removed the old rpm (rpm -e) and then a fresh install of the new version, started mailman, and after some minor config tweaks, it seems to be working.
There was an issue a while back, see https://mail.python.org/pipermail/mailman-users/2005-November/047814.html, but this was due to a SuSE patch that referenced a Python xml library that wasn't installed. The specifics aren't relevant to your issue, but it could indicate there's something missing in your python. Have you installed the python-dev package?
-- Robert Heller -- 978-544-6933 / heller@deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
On 05/01/2014 08:21 AM, Robert Heller wrote:
At Wed, 30 Apr 2014 14:34:51 -0700 Mark Sapiro mark@msapiro.net wrote:
Did you totally remove the Centos package or try to 'upgrade' it. The latter is not at all straightforward. See the FAQ at http://wiki.list.org/x/KYCB.
That page relates to upgrading from 2.1.5-20 or earlier. I was upgrading from 2.1.9, so that does not apply (?).
That FAQ and the mailman-developers post linked from it explain changed in the RedHat/CentOS package beginning with 2.1.15 that render it impossible to do a straightforward configure/install of a GNU Mailman source distribution on top of an existing RedHat/CentOS package.
Ok, I did an explict stop of mailman, removed the old rpm (rpm -e) and then a fresh install of the new version, started mailman, and after some minor config tweaks, it seems to be working.
Good.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
At Thu, 01 May 2014 08:31:05 -0700 Mark Sapiro mark@msapiro.net wrote:
On 05/01/2014 08:21 AM, Robert Heller wrote:
At Wed, 30 Apr 2014 14:34:51 -0700 Mark Sapiro mark@msapiro.net wrote:
Did you totally remove the Centos package or try to 'upgrade' it. The latter is not at all straightforward. See the FAQ at http://wiki.list.org/x/KYCB.
That page relates to upgrading from 2.1.5-20 or earlier. I was upgrading from 2.1.9, so that does not apply (?).
That FAQ and the mailman-developers post linked from it explain changed in the RedHat/CentOS package beginning with 2.1.15 that render it impossible to do a straightforward configure/install of a GNU Mailman source distribution on top of an existing RedHat/CentOS package.
Ok, I did an explict stop of mailman, removed the old rpm (rpm -e) and then a fresh install of the new version, started mailman, and after some minor config tweaks, it seems to be working.
Good.
I also found a *fatal* error in Tagger.py at line 74:
May 01 10:50:39 2014 (17899) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/Tagger.py", line 74, in process mlist, msg, msgdata, Delete=False) TypeError: change_header() got an unexpected keyword argument 'Delete'
I deleted the ', Delete=False' from the change_header parameter list and removed Tagger.pyc and Tagger.pyo (forcing the use of the uncompiled code) as a short term temp fix (so that mail will go through). I *presume* that this is fixed in 2.1.18 and when that comes out (I understand it is due out "Real Soon Now"(tm)).
-- Robert Heller -- 978-544-6933 / heller@deepsoft.com Deepwoods Software -- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
On 05/01/2014 10:06 AM, Robert Heller wrote:
I also found a *fatal* error in Tagger.py at line 74:
...
TypeError: change_header() got an unexpected keyword argument 'Delete'
That's a known bug which was fixed in 2.1.17 https://bugs.launchpad.net/mailman/+bug/1251495.
I deleted the ', Delete=False' from the change_header parameter list
That's the wrong fix. The correct fix is to change the spelling from Delete=False to delete=False
and removed Tagger.pyc and Tagger.pyo (forcing the use of the uncompiled code) as a short term temp fix (so that mail will go through).
That was unnecessary. When Python imports a module, and there is a .py and a .pyc and maybe a .pyo, it checks the time stamps and if the .py is more recent, it loads that and compiles it and if it has permission, (re)writes the .pyc.
I *presume* that this is fixed in 2.1.18 and when that comes out (I understand it is due out "Real Soon Now"(tm)).
As I note above, fixed in 2.1.17, and the final 2.1.18 release will be this weekend barring any unforeseen personal emergencies.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
Robert Heller