Changes

  signal-event email-update

  signal-event email-update

======Force first log rotation======

=====Force first log rotation=====

qplogsumm.pl only updates its statistics when the qpsmtpd log file is rotated.  This can take several days on a moderately busy server, and could take weeks or months on some servers.

qplogsumm.pl only updates its statistics when the qpsmtpd log file is rotated.  This can take several days on a moderately busy server, and could take weeks or months on some servers.

  kill -ALRM `cat /var/service/qpsmtpd/log/supervise/pid`

  kill -ALRM `cat /var/service/qpsmtpd/log/supervise/pid`

======Potential Problems======

=====Potential Problems=====

'''/var/log/qpsmtpd/state missing'''<br>

======/var/log/qpsmtpd/state missing======

qplogsumm.pl will completely lock all in-bound email if <tt>/var/log/qpsmtpd/state</tt> is missing when multilog attempts to rotate the qpsmtpd log file ([[bugzilla:3393|Bug 3393]]).  This will never happen under normal circumstances - only in the event of a disk error or if the administrator moves or deletes the existing file.  If this does happen, the problem can be resolved using

qplogsumm.pl will completely lock all in-bound email if <tt>/var/log/qpsmtpd/state</tt> is missing when multilog attempts to rotate the qpsmtpd log file ([[bugzilla:3393|Bug 3393]]).  This will never happen under normal circumstances - only in the event of a disk error or if the administrator moves or deletes the existing file.  If this does happen, the problem can be resolved using

   touch /var/log/qpsmtpd/state

   touch /var/log/qpsmtpd/state

   sv restart /var/log/qpsmtpd

   sv restart /var/log/qpsmtpd

'''Unprocessed Log Files'''<br>

======Unprocessed Log Files======

If qpsmtpd is terminated abnormally (due to a power failure, for example), the log files may not be completely "processed".  If this happens, you will have files in <tt>/var/log/qpsmtpd</tt> with names like the one shown below, ending in '''.u''':<code> @4000000048ec03873b1a841c.u</code>

If qpsmtpd is terminated abnormally (due to a power failure, for example), the log files may not be completely "processed".  If this happens, you will have files in <tt>/var/log/qpsmtpd</tt> with names like the one shown below, ending in '''.u''':<code> @4000000048ec03873b1a841c.u</code>