Mailman error log file
We receive an error "We're sorry, we hit a bug!" Upon inspection, we found that we run out of space on the server. We found that the error log file in /usr/local/mailman/logs grows rapidly. We delete one a couple days ago at 33GB in size. 3 days pass and it grows to 11GB.
How do we check if verbose logging is on?
Thank you,
Hung Phan wrote:
How do we check if verbose logging is on?
Unless you have enabled SMTP debugging as discussed in the FAQ at
<http://wiki.list.org/x/-IA9> (adding "
self.__conn.set_debuglevel(1)" to the definition of the _connect
method in Mailman/Handlers/SMTPDirect.py) or installed some other
local modification to log stuff to Mailman's error log, the only
things logged there are actual errors and exceptions that need to be
addressed. If you need help understanding these, post some typical,
complete log messages including traceback and and other information.
There is no 'verbose' logging switch.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
That's it! The set_debuglevel(1) commend is left over from when we debugged an issue previously. We, however, have a different issue. We use logrotate to rotate the error log daily. After we implemented that, the new error log file stays at 0. Is it normal? Posts mention other services also write entries in this log file besides exim so should the file stay at 0 after 2 days?
Thank you very much for all the help,
On Feb 22, 2013, at 6:18 PM, Mark Sapiro wrote:
On 2/26/2013 3:02 PM, Hung Phan wrote:
We, however, have a different issue. We use logrotate to rotate the error log daily. After we implemented that, the new error log file stays at 0. Is it normal? Posts mention other services also write entries in this log file besides exim so should the file stay at 0 after 2 days?
Almost everything written to Mailman's error log is the result of some kind of error or exception that should not normally occur. Some of these can result from user errors such as an invalid list name in a URL to access a web admin page or an invalid private archive URL, but most indicate some kind of Mailman internal error, so yes, it is normal for this log to be empty and when it isn't, the messages should be examined to see if there is some error condition that should be attended to.
Note: exim writes its own logs. It does not write to Mailman's logs. The 'error' log messages from set_debuglevel(1) are written by Python's smtplib module used by Mailman/Handlers/SMTPDirect.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hung Phan wrote:
How do we check if verbose logging is on?
Unless you have enabled SMTP debugging as discussed in the FAQ at
<http://wiki.list.org/x/-IA9> (adding "
self.__conn.set_debuglevel(1)" to the definition of the _connect
method in Mailman/Handlers/SMTPDirect.py) or installed some other
local modification to log stuff to Mailman's error log, the only
things logged there are actual errors and exceptions that need to be
addressed. If you need help understanding these, post some typical,
complete log messages including traceback and and other information.
There is no 'verbose' logging switch.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
That's it! The set_debuglevel(1) commend is left over from when we debugged an issue previously. We, however, have a different issue. We use logrotate to rotate the error log daily. After we implemented that, the new error log file stays at 0. Is it normal? Posts mention other services also write entries in this log file besides exim so should the file stay at 0 after 2 days?
Thank you very much for all the help,
On Feb 22, 2013, at 6:18 PM, Mark Sapiro wrote:
On 2/26/2013 3:02 PM, Hung Phan wrote:
We, however, have a different issue. We use logrotate to rotate the error log daily. After we implemented that, the new error log file stays at 0. Is it normal? Posts mention other services also write entries in this log file besides exim so should the file stay at 0 after 2 days?
Almost everything written to Mailman's error log is the result of some kind of error or exception that should not normally occur. Some of these can result from user errors such as an invalid list name in a URL to access a web admin page or an invalid private archive URL, but most indicate some kind of Mailman internal error, so yes, it is normal for this log to be empty and when it isn't, the messages should be examined to see if there is some error condition that should be attended to.
Note: exim writes its own logs. It does not write to Mailman's logs. The 'error' log messages from set_debuglevel(1) are written by Python's smtplib module used by Mailman/Handlers/SMTPDirect.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Hung Phan -
Mark Sapiro