[Mailman-Users] web interface bug after restore mailman
cengao at gmail.com
Wed Aug 1 06:14:04 CEST 2007
thanks a lot for your suggestion.
the error log is as follows
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy
of this page to the webmaster for this site with a description of what
Traceback (most recent call last):
File "/usr/local/bin/mailman//scripts/driver", line 82, in run_main
line 52, in __init__
Logger.__init__(self, category, nofail, immediate)
File "/usr/local/bin/mailman//Mailman/Logging/Logger.py", line 50, in __init__
File "/usr/local/bin/mailman//Mailman/Logging/Logger.py", line 68, in __get_f
line 566, in open
file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 13] Permission denied: '/usr/local/bin/mailman/logs/error'
sys.version 2.3.5 (#1, Dec 25 2005, 07:24:19) [GCC 4.0.1 (Apple
Computer, Inc. build 5250)]
FYI, the log directory and even all the mailman directory is owned by
And in /logs/error , it says
Aug 01 00:02:04 2007 (432) Uncaught runner exception: multipart message with
no defined boundary
Aug 01 00:02:04 2007 (432) Traceback (most recent call last):
File "/usr/local/bin/mailman//Mailman/Queue/Runner.py", line 100, in _oneloop
msg, msgdata = self._switchboard.dequeue(filebase)
File "/usr/local/bin/mailman//Mailman/Queue/Switchboard.py", line 164, in dequ
msg = email.message_from_string(msg, Message.Message)
File "/usr/local/bin/mailman/pythonlib/email/__init__.py", line 51, in message
return Parser(_class, strict=strict).parsestr(s)
File "/usr/local/bin/mailman/pythonlib/email/Parser.py", line 75, in parsestr
return self.parse(StringIO(text), headersonly=headersonly)
File "/usr/local/bin/mailman/pythonlib/email/Parser.py", line 64, in parse
self._parsebody(root, fp, firstbodyline)
File "/usr/local/bin/mailman/pythonlib/email/Parser.py", line 246, in _parsebo
BoundaryError: multipart message with no defined boundary
Aug 01 00:02:04 2007 (432) Ignoring unparseable message: 1181090435.8718021+ee06
and this error log has only been written twice since I restored this
directory, although I've accessed the web page tons of times.
thanks again for your help
On 7/31/07, Mark Sapiro <msapiro at value.net> wrote:
> Cen Gao wrote"
> >Now mailman works well and it can distribute mail without any problem.
> >The only problem I get is I can not access any web interface pages and
> >it shows the error message as below.
> >Bug in Mailman version 2.1.9
> >We're sorry, we hit a bug!
> >Please inform the webmaster for this site of this problem. Printing of
> >traceback and other system information has been explicitly inhibited,
> >but the webmaster can find this information in the Mailman error logs.
> >I am pretty sure that my httpd is configured well.(Otherwise, I should get a "
> >404 not found" error rather than this)
> >check_perms shows no permission problem.
> >I even did a reinstall from source and the problem remains.
> >And it seems that the $mailman/logs/error didn't show any error, nor
> >I can found any in /var/logs/
> Look in mm_cfg.py for a definition of LOG_DIR. If there isn't one, then
> look in Defaults.py ( there it should be
> LOG_DIR = os.path.join(VAR_PREFIX, 'logs')
> ), and if so, then look in Defaults.py for the definition of
> VAR_PREFIX. This should tell you where the logs are.
> If you still can't find them, or if the problem is the error log isn't
> being written (are the smtp and post logs in the same directory being
> written?), you can edit $mailman/scripts/driver and find line 31 or so
> which says
> STEALTH_MODE = 0
> and change it to
> STEALTH_MODE = 1
> which will display the error information in your browser. Without this
> information, there's not much more we can do.
> Mark Sapiro <msapiro at value.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users