Scheduled task failures after upgrade to 10.8
search cancel

Scheduled task failures after upgrade to 10.8


Article ID: 254730


Updated On:


Protection Suite Enterprise Edition Messaging Gateway


Following the upgrade to Messaging Gateway 10.8.0 or 10.8.1, you may see scheduled tasks, such as backups, fail with similar to the following errors logged in the BrightmailLog.log

Nov 14 2022 00:00:00 [BrightmailScheduler_Worker-46] [AgentEvent] WARN - null: Name or service not known : null 
Nov 14 2022 00:00:00 [BrightmailScheduler_Worker-46] [AgentHelper] ERROR - An agent error has occurred in the following code path: 
 at org.quartz.simpl.SimpleThreadPool$
Nov 14 2022 00:00:00 [BrightmailScheduler_Worker-46] [AgentHelper] ERROR - --- Host Name: null 
Nov 14 2022 00:00:00 [BrightmailScheduler_Worker-46] [AgentHelper] ERROR - --- Agent Port Number: 41002 
Nov 14 2022 00:00:00 [BrightmailScheduler_Worker-46] [AgentHelper] ERROR - The response object is null. 
Nov 14 2022 00:00:00 [BrightmailScheduler_Worker-46] [ScriptHelper] ERROR - The Agent running on null is temporarily unreachable. Please check the specified host. ; nested exception is: null: Name or service not known 


Release : 10.8.0 or 10.8.1


The scheduled backup is failing due to configuration corruption or a name resolution error. 


Primary Resolution

This issue is often corrected by recreating the scheduled configuration, such as creating a new scheduled backup and deleting the old scheduled entry.

  1. Log into Messaging Gateway Control Center as an administrator
  2. Go to Administration > Version > Backup
  3. Create a new scheduled backup matching the configuration of the original backup using the Add button
  4. Delete the original scheduled backup by selecting it and clicking Delete

Secondary Workaround

If recreating the scheduled backups does not correct the issue, then it may be due to name resolution issues that are discussed below.

It should be noted that manual backups do not appear to be affected.

Further improvements are being added to future releases to help address potential underlying causes.


  1. Add the Control Center IP address to the local host file in Administration > Configuration > host > DNS / Time > Host name and IP Address Mapping as shown below
  2. Restart the Control Center appliance or virtual machine