Uncaught runner exception: unknown encoding: us-ascii
Please help! Since upgrading to Mailman 2.1.12 and Python 2.6.1, my error log is filling up with messages like this and virtually no messages are moving through my mailing lists. Based on a search of the archives, I removed ALL digest.mbox files and ran unshunt. No messages moved and the errors continue.
Mar 02 09:51:11 2009 (30278) SHUNTING: 1236010837.317246+dbe24d8d98f7ad6b16fdd98b1f18ae69b6a225e7 Mar 02 09:51:11 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 09:51:11 2009 (30278) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/lib/python2.5/email/generator.py", line 84, in flatten File "/usr/lib/python2.5/email/generator.py", line 116, in _write File "/var/mailman/Mailman/Handlers/SpamDetect.py", line 84, in _write_headers Generator._write_headers(self, msg) File "/usr/lib/python2.5/email/generator.py", line 150, in _write_headers File "/usr/lib/python2.5/email/generator.py", line 26, in _is8bitstring LookupError: unknown encoding: us-ascii
rpyne@kinfolk.org wrote:
You say you have Python 2.6.1, but your Python email library seems to be python2.5.
Did you upgrade Python after installing Mailman?
It appears your installation may not be completely consistent. What Python version is invoked by a "python" command.
You may need to rerun Mailman's configure and make install.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2 Mar 2009 at 9:10, Mark Sapiro wrote:
# python Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) [GCC 4.2.4] on linux2 Type "help", "copyright", "credits" or "license" for more information.
I re-ran the configure and install of mailman, ran unshunt and the errors still show using python 2.5:
Mar 02 10:39:45 2009 (30280) SHUNTING: 1236015583.0520451+8058beae403d3fbac5f2571929549c19e2125acd Mar 02 10:39:53 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 10:39:53 2009 (30278) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/lib/python2.5/email/generator.py", line 84, in flatten File "/usr/lib/python2.5/email/generator.py", line 109, in _write File "/usr/lib/python2.5/email/generator.py", line 135, in _dispatch File "/usr/lib/python2.5/email/generator.py", line 201, in _handle_multipart File "/usr/lib/python2.5/email/generator.py", line 84, in flatten File "/usr/lib/python2.5/email/generator.py", line 116, in _write File "/var/mailman/Mailman/Handlers/SpamDetect.py", line 84, in _write_headers Generator._write_headers(self, msg) File "/usr/lib/python2.5/email/generator.py", line 150, in _write_headers File "/usr/lib/python2.5/email/generator.py", line 26, in _is8bitstring LookupError: unknown encoding: us-ascii
Mar 02 10:39:54 2009 (30278) SHUNTING: 1236014500.0552149+8a7b01ddc869ad3d723ffcadca4644d72858e68b Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: /var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c35185 46e179e37b02.bak
rpyne@kinfolk.org wrote:
What does config.log show for your configure command line and for things like the following:
configure:1714: checking for --with-python configure:1726: result: no configure:1733: checking for python configure:1751: found /usr/bin/python configure:1764: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok
(the first several lines after
## ----------- ## ## Core tests. ## ## ----------- ##
Are you also getting many errors like the following?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2 Mar 2009 at 10:24, Mark Sapiro wrote:
configure:1714: checking for --with-python configure:1726: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok configure:1872: checking that Python has a working distutils configure:1921: result: yes configure:1969: checking for a BSD-compatible install configure:2025: result: /usr/bin/install -c configure:2036: checking whether make sets $(MAKE)
Yes:
Mar 02 11:23:49 2009 (13849) Skipping and preserving unparseable message: 1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d05094c2a5fa49 Mar 02 11:23:49 2009 (13849) Failed to unlink/preserve backup file: /var/mailman/qfiles/out/1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d 05094c2a5fa49.bak
Since the only thing on the server that is (intentionally) using Python, I deleted the /lib/python2.5 and /usr/lib/python2.5 directories and have reinstalled Python, reinstalled Mailman and rebooted the server.
It appears to have cleared things up as I ran unshunt and now all of the qfiles except bad are empty and several previously shunted emails are delivering.
Thanks.
rpyne@kinfolk.org wrote:
Unfortunately, I neglected to put the actual error in the above log message - one more thing for 2.2 :)
This seems to say there is an error in trying to move the .bak backup queue entry for the unparseable message to a .psv entry in the qfiles/bad queue. I don't know why.
Well, perhaps we'll never understand fully what the issues were, but I'm glad it's OK now.
Those .psv files in qfiles/bad are the unparseable messages. Almost certainly, they are spam in a malformed MIME message. if you're curious, you can examine them with 'bin/dumpdb -p'.
With default settings, they will be discarded by cron/cull_bad_shunt after 7 days.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
rpyne@kinfolk.org wrote:
You say you have Python 2.6.1, but your Python email library seems to be python2.5.
Did you upgrade Python after installing Mailman?
It appears your installation may not be completely consistent. What Python version is invoked by a "python" command.
You may need to rerun Mailman's configure and make install.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2 Mar 2009 at 9:10, Mark Sapiro wrote:
# python Python 2.6.1 (r261:67515, Feb 28 2009, 15:18:21) [GCC 4.2.4] on linux2 Type "help", "copyright", "credits" or "license" for more information.
I re-ran the configure and install of mailman, ran unshunt and the errors still show using python 2.5:
Mar 02 10:39:45 2009 (30280) SHUNTING: 1236015583.0520451+8058beae403d3fbac5f2571929549c19e2125acd Mar 02 10:39:53 2009 (30278) Uncaught runner exception: unknown encoding: us-ascii Mar 02 10:39:53 2009 (30278) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/lib/python2.5/email/generator.py", line 84, in flatten File "/usr/lib/python2.5/email/generator.py", line 109, in _write File "/usr/lib/python2.5/email/generator.py", line 135, in _dispatch File "/usr/lib/python2.5/email/generator.py", line 201, in _handle_multipart File "/usr/lib/python2.5/email/generator.py", line 84, in flatten File "/usr/lib/python2.5/email/generator.py", line 116, in _write File "/var/mailman/Mailman/Handlers/SpamDetect.py", line 84, in _write_headers Generator._write_headers(self, msg) File "/usr/lib/python2.5/email/generator.py", line 150, in _write_headers File "/usr/lib/python2.5/email/generator.py", line 26, in _is8bitstring LookupError: unknown encoding: us-ascii
Mar 02 10:39:54 2009 (30278) SHUNTING: 1236014500.0552149+8a7b01ddc869ad3d723ffcadca4644d72858e68b Mar 02 10:39:54 2009 (30278) Failed to unlink/preserve backup file: /var/mailman/qfiles/in/1236014500.0552149+5aed32c1bfbe6e4ac85c02c35185 46e179e37b02.bak
rpyne@kinfolk.org wrote:
What does config.log show for your configure command line and for things like the following:
configure:1714: checking for --with-python configure:1726: result: no configure:1733: checking for python configure:1751: found /usr/bin/python configure:1764: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok
(the first several lines after
## ----------- ## ## Core tests. ## ## ----------- ##
Are you also getting many errors like the following?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2 Mar 2009 at 10:24, Mark Sapiro wrote:
configure:1714: checking for --with-python configure:1726: result: /usr/bin/python configure:1774: checking Python interpreter configure:1792: result: /usr/bin/python configure:1796: checking Python version configure:1829: result: 2.6.1 configure:1833: checking Python's email package configure:1866: result: ok configure:1872: checking that Python has a working distutils configure:1921: result: yes configure:1969: checking for a BSD-compatible install configure:2025: result: /usr/bin/install -c configure:2036: checking whether make sets $(MAKE)
Yes:
Mar 02 11:23:49 2009 (13849) Skipping and preserving unparseable message: 1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d05094c2a5fa49 Mar 02 11:23:49 2009 (13849) Failed to unlink/preserve backup file: /var/mailman/qfiles/out/1236014500.0552149+80fb5a8a97a8d0c248a1d845d2d 05094c2a5fa49.bak
Since the only thing on the server that is (intentionally) using Python, I deleted the /lib/python2.5 and /usr/lib/python2.5 directories and have reinstalled Python, reinstalled Mailman and rebooted the server.
It appears to have cleared things up as I ran unshunt and now all of the qfiles except bad are empty and several previously shunted emails are delivering.
Thanks.
rpyne@kinfolk.org wrote:
Unfortunately, I neglected to put the actual error in the above log message - one more thing for 2.2 :)
This seems to say there is an error in trying to move the .bak backup queue entry for the unparseable message to a .psv entry in the qfiles/bad queue. I don't know why.
Well, perhaps we'll never understand fully what the issues were, but I'm glad it's OK now.
Those .psv files in qfiles/bad are the unparseable messages. Almost certainly, they are spam in a malformed MIME message. if you're curious, you can examine them with 'bin/dumpdb -p'.
With default settings, they will be discarded by cron/cull_bad_shunt after 7 days.
-- 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 -
rpyne＠kinfolk.org