Mailman is not working. Messages come in, nothing goes out. Logs are useless, providing no clue as to what is happening.
In a working mailman system. what is the sequence of logging that a message would go through?
mjb.
On 04/24/2016 10:12 PM, Mark J Bradakis wrote:
Mailman is not working. Messages come in, nothing goes out. Logs are useless, providing no clue as to what is happening.
There is a FAQ article at https://wiki.list.org/x/4030723 which may help.
In a working mailman system. what is the sequence of logging that a message would go through?
For a normal message that is accepted and delivered without moderation, there will be entries in Mailman's post and smtp logs, both of which are written by Mailman's final delivery process.
For messages which are 'shunted' due to an unanticipated exception in processing, there will be an entry in the error log. For messages which are held for moderation or automatically discarded or rejected, there will be an entry in the vette log.
If the MTA log shows delivery to Mailman and there are no Mailman log entries, the most likely explanation is that Mailman's IncomingRunner is not running or 'stuck' and the messages are sitting in Mailman's in/ queue. Or possibly they are getting to the out/ queue and OutgoingRunner is not running or 'stuck'.
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!
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.
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.
participants (3)
-
Mark J Bradakis -
Mark Sapiro -
Richard Shetron