Mark Sapiro <m...@msapiro.net> wrote:

> The above message indicates the traceback was written to some 'error' log,
> just not the one you're looking at.
> 
> You can always edit (temporarily) Mailman's scripts/driver and at line 33
> change
> 
> STEALTH_MODE = 1
> 
> to
> 
> STEALTH_MODE = 0
> 
> and that will allow the traceback and other diagnostic info to be displayed
> instead of the "We're sorry, we hit a bug!" message.
> 
> 
> > Would like to show some logging, but it simply is not there.
> 
> 
> It was successfully written to an 'error' log somewhere or the "We're sorry,
> we hit a bug!" message would say:
> 
> "Mailman experienced a very low level failure and could not even generate a
> useful traceback for you.  Please report this to the Mailman administrator at
> this site."
> 

Thanks Mark, the page is showing that the log location was not writeable, must
be the bug.

Resetting the LOG_DIR to default saved me.

Apologies for the noise.

-- 
Roel Wagenaar,

Linux-User #469851 with the Linux Counter; http://linuxcounter.net/

Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen.
Vraag: Waarom is top-posting een slechte gewoonte?
Antw.: Top-posting.
Vraag: Wat is het meest ergerlijke in e-mail?

Ignorence is when you don't know anything and somebody finds out.
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to