On 05/20/2016 05:35 AM, Richard Shetron wrote: > How do I turn on tracing to find the source of this error. The > interface worked until I told check_perms to fix permissions so I'm sure > there is a permission issue. Also the qrunner won't run, which I also > suspect is a permission error. My partner who did the install has > retired for medical reasons so I'm trying to learn how to do all sorts > of things in too little time :( I tried to look in both the mailman > logs and the apache logs for errors and didn't find anything. > > Bug in Mailman version 2.1.21rc2 > > We're sorry, we hit a bug!
There should be a traceback and other information about this error in Mailman's error log. If it's not there, there is probably a permission issue in writing the log. You can at least temporarily ensure that Mailman's logs are writable by anyone and see if that helps. Also, you can edit $prefix/scripts/driver and at line 33 set STEALTH_MODE = 0 and the traceback will be included on the "we hit a bug" page. Also, if check_perms -f broke things, permissions must have been set in some non-standard way to begin with. See the FAQ article at <https://wiki.list.org/x/4030645>. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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
