Operational Defect Database
BugZero found this defect 3673 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000g3hwSAA
FireCluster Sync can fail if cluster member memory is low
Last update date:
4/30/2014
Affected products:
Firebox M200
Firebox M300
Firebox M270
Firebox M370
Firebox M470
Firebox M570
Firebox M670
Firebox M290
Firebox M390
Firebox M400
Firebox M500
Firebox M440
Affected releases:
All
Fireware
11.x
11.10.x
11.10
11.10.1
11.10.2
11.10.3
11.10.4
11.10.5
11.10.6
11.10.7
Fixed releases:
All
Description:
Issue
In some cases, one or both members of a FireCluster do not have enough available memory to perform the sync operation. When this occurs, error messages such as these can show in the log messages:May 2 15:48:10 2013 FBXTM530-Passive local3.err systemd[12451]: 500:RAM availability is already in "red" state, cannot proceed with backup.May 2 15:48:10 2013 FBXTM530-Passive local3.err ccd[1024]: ccd_backup_wgbk: SystemD error: /system/sync failed. Tmout=75 seconds. retcode=500, response=RAM availability is already in "red" state, cannot proceed with backup.May 2 15:48:10 2013 FBXTM530-Passive local3.err ctd[1022]: Failed to access '/pending/clst_sync_file.2.1366447225.80B202DDD596B' to sync
Workaround/Solution
When this issue occurs, you can reboot the cluster members to free up memory. To reduce downtime, follow these steps.: In Firebox System Manager, select Tools > Cluster > Reboot member.From the drop-down list, select the backup master device and click OK. The non-master device reboots. After the non-master device reboots, select Tools > Cluster > Failover master.Repeat steps 1 and 2 to reboot the previous master. You can also change your device configuration to reduce memory use. For example, use the information in this article to reduce memory and CPU use by Gateway AntiVirus: Optimize HTTP Gateway AV performance.
