Guest

Preview Tool

Cisco Bug: CSCul18507 - MID syncs fail cause we don't wait for hermes to startup

Last Modified

Sep 08, 2020

Products (1)

  • Cisco Content Security Management Appliance

Known Affected Releases

10.1.0-037 10.1.0-052 11.5.1-115 12.5.0-648 13.0.0-249 7.9.1-102 8.1.0-000 9.6.1-019

Description (partial)

Symptom:
During backups, you may get one of the following alerts:

Wed Oct 30 21:45:37 2013 Warning: BACKUP: Unable to update MID on remote machine 10.80.38.109, this may cause inconsistencies with Spam Quarantine database. Try upgrading target machine to same Async OS version.

BACKUP: Unable to update MID on remote machine 10.80.38.109 due to the error: hostname.backup.machine: The daemon is not responding., this may cause inconsistencies with Quarantine database.

Conditions:
The error occurs when the destination SMA is lagging and does not start up a process fast enough to be able to handle the MID sync command.  The error is not a problem unless you need put the backup SMA into production.  The out of sync MID numbers would generate database errors and failures to quarantine new email, until you receive enough emails to make up the number missing from the last MID sync success.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.