Reload 3 (all builds)
Reload repeatedly sending notifications to the Admin.
Follow these steps to determine the problem:
1) Check the logs.
The Reload error log should indicate whether these notifications are for recent errors, or old errors.2) Clear the Postfix queue.
The Reload error log can be viewed from the Linux terminal. After having logged into a terminal session on the Reload server, type the following command:
reloadThen press enter.
This command loads a simple GUI, where you can view logs. Once it has loaded select, 'Logs', then select 'Support' to view the current support log.
The Reload support log, contains a collection of all the Reload logs in this order:
*SYSTEM EVENT LOG - LAST 20 LINESScroll down through the logs until you have reached the full System Error log, and find the most recent errors that have occurred.
*SYSTEM MONITOR LOG
*SYSTEM ERROR LOG - LAST 20 LINES
*SYSTEM AGENT LOG
*SYSTEM EVENT LOG
*SYSTEM ERROR LOG
*SYSTEM STATUS REPORT
If none of the logged errors are recent then proceed to step 2.
If there are recent errors, it is possible that the admin notifications are being sent for these errors, and the next step is to take, is to resolve those errors, and then the admin notifications should stop.
If the notifications do not stop after resolving the errors, the repeat step 1.
Reload sends notifications through the Linux email service, PostFix. Very seldom, these notifications can get stuck in the PostFix mail queue, and continue to be sent over and over, until the queue is cleared out.
At a terminal prompt on the Reload server, enter the following command:
postsuper -d ALLThis should clear out all the messages in the PostFix queue, and stop the repeating notifications.
This article was originally published in the GWAVA knowledgebase as article ID 1978.