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 <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. ------------------------------------------------------ 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
