We're sorry, we hit a bug!
L.S.
Bug in Mailman version 2.1.15
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing oftraceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.
The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about.
The last thing changed is the adres of the main pages.
It looks like the mail-system is not affected, any idea what is going on?
Would like to show some logging, but it simply is not there.
-- 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?
Why be difficult, when with a bit of effort, you can be impossible?
On 07/01/2014 07:08 AM, Roel Wagenaar wrote:
L.S.
Bug in Mailman version 2.1.15
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.
The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about.
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."
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro <mark@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.
Well, on a new implementation, I'm getting the same thing in 2.18-1. What'd you do to fix it on your end?
On Tue, 1 Jul 2014 17:33:19 +0200, you wrote:
Mark Sapiro <mark@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.
On 01/10/2015 06:53 AM, Steve Matzura wrote:
Well, on a new implementation, I'm getting the same thing in 2.18-1. What'd you do to fix it on your end?
I think that one was a permissions error. As Mr. Wagenaar reported, he had overridden the LOG_DIR setting and it pointed to an unwritable location.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
Roel Wagenaar -
Steve Matzura