Cisco Bug: CSCvs03036 - Enhance cluster trace output to include more details to the reason why the unit quit.
Apr 15, 2020
- Cisco ASA 5500-X Series Firewalls
Known Affected Releases
Symptom: Cluster trace output was unable to explain the reason why the unit quit. Conditions: Debugging information from cluster trace did not provide any indications why the unit quit. Example logs from defect CSCvm33545: Firepower-Module1_10_17_2019_22_43_47.tar/opt/cisco/platform/logs/ssp_ntp.log.2.gz: ssp_ntpd.13362 [Thu Oct 17 18:00:29 UTC 2019] [@878]: INFO: detected sysclock-hwclock drift, sync hwclock <snip> select() to /dev/rtc to wait for clock tick timed out...synchronization failed <snip> ssp_ntpd.13362 [Thu Oct 17 18:01:20 UTC 2019] [@878]: INFO: detected sysclock-hwclock drift, sync hwclock <snip> Time read from Hardware Clock: 2019/12/03 18:01:27 <<< Hardware clock shows December, it's October Setting Hardware Clock to 18:01:21 = 1571335281 seconds since 1969 Clock drifted -0.7 seconds in the past 42 seconds in spite of a drift factor of -86399.090554 seconds/day. FTD Cluster trace log ++++++ Oct 13 Outage: +++++++++ path of the files ----- results-10-15-2019--211118/dir-archives/mnt-disk0-log/cluster_trace.log <------------------------------ Oct 13 12:49:17.979 [DBUG]Send CCP message to all: CCP_MSG_CLOCK_SYNC_NTFY Oct 13 12:49:18.049 [DBUG]Making an RPC call, Cluster SVM Client to unit-1-1(0) with parameter 0x0000000000000000 <end of file> results-10-15-2019--211118.tar.gz - dir-archives/mnt-disk0-log/cluster_trace.log.1 <clock jump> <start of file> results-10-15-2019--211118.tar.gz - dir-archives/mnt-disk0-log/cluster_trace.log Oct 14 19:42:54.849 [INFO]diskstatus application status is changed from up to down Oct 14 19:42:54.849 [DBUG]Send CCP message to all: CCP_MSG_APP_STATE Oct 14 19:42:54.849 [DBUG]Receive CCP message: CCP_MSG_APP_STATE Oct 14 19:42:54.849 [INFO]Peer unit unit-1-1(0) reported its diskstatus application status is up Oct 14 19:42:54.849 [DBUG]Send event (DISABLE, INTERNAL-EVENT, permanent, Master has application down that slave has up) to FSM. Current state MASTER Oct 14 19:42:54.849 [CRIT]Master unit unit-2-1 is quitting due to diskstatus Application health check failure, and master's application state is down Oct 14 19:42:54.849 [INFO]State machine changed from state MASTER to DISABLED
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases