Following update to Symantec Messaging Gateway (SMG) 9.5.x backup or restore opreations taking longer than thirty (30) minutes generate an error in the control center BrightmailLog.log file. An alert will be sent if the backup was scheduled and alerting for failed scheduled tasks has been configured.
Following error may be displayed by the Control Center:
Error: Cannot backup the database on the local host. The Agent running on 127.0.0.1 is temporarily unreachable. Please check the specified host.; nested exception is: java.net.SocketTimeoutException: Read timed out
Following error appears in BrightmailLog.log:
Jun 06 2011 09:30:00 [BrightmailScheduler_Worker-3] ERROR - --- Host Name: 127.0.0.1
Jun 06 2011 09:30:00 [BrightmailScheduler_Worker-3] ERROR - --- Agent Port Number: 41002
Jun 06 2011 09:30:00 [BrightmailScheduler_Worker-3] ERROR - The response object is null.
Jun 06 2011 09:30:00 [BrightmailScheduler_Worker-3] ERROR - com.brightmail.common.BrightmailException: The Agent running on 127.0.0.1 is temporarily unreachable. Please check the specified host. ; nested exception is:
java.net.SocketTimeoutException: Read timed out
Jun 06 2011 09:30:00 [BrightmailScheduler_Worker-3] ERROR - Error occurred while attempting to execute scheduled backup.
The control center process stops listening for return status from the backup or restore after thirty (30) minutes and interprets the timeout as an error.
This issue has been addressed with the SMG 10.0.0 release. Backup and restore operations are exempted from the timeout applied to other control center - scanner communication.
For SMG 9.5.x backups, this is a cosmetic error. The backup script is running to completion and backups will be valid (provided there isn't another concurrent issue with the backup). This error can be safely ignored until Symantec addresses the issue in a future release.
For restore operations, the full restore datafile may not be pushed to the appliance prior to the timeout in which case the restore will fail. If a restore takes longer than thirty (30) minutes the restore should be performed from the Control Center command line interface (CLI) db-restore command.
For information on the db-restore CLI command, please see HOWTO53690
Imported Document ID: TECH161640
Subscribing will provide email updates when this Article is updated. Login is required.