Troubleshooting Tip: The Signal 6 confsyncd crash is resulting in the blades on the primary chassis becoming unsynchronized

[amrit]

Description	This article provides a workaround for a situation where the confsyncd daemon crashes with signal 6, leading to synchronization problems between the blades of the primary chassis device.
Scope	FortiGate Chassis 6000/7000, FortiOS v7.2, v7.4 and v7.6.
Solution	Execute the command below to verify the presence of the following crash event.   diagnose debug crashlog read  Example output: 2070: 2025-11-18 00:26:16 <06465> firmware FortiGate-6000F v7.2.11,build1740b1740,250210 (GA.M) (Release) 2071: 2025-11-18 00:26:16 <06465> application confsyncd 2072: 2025-11-18 00:26:16 <06465> *** signal 6 (Aborted) received *** 2073: 2025-11-18 00:26:16 <06465> Register dump: 2074: 2025-11-18 00:26:16 <06465> RAX: 0000000000000000 RBX: 00007f42d1eb0040 2075: 2025-11-18 00:26:16 <06465> RCX: ffffffffffffffff RDX: 0000000000000000 2076: 2025-11-18 00:26:16 <06465> R08: 0000000000000000 R09: 00007ffff815fc70 2077: 2025-11-18 00:26:16 <06465> R10: 0000000000000008 R11: 0000000000000246 2078: 2025-11-18 00:26:16 <06465> R12: 00007ffff815fee0 R13: 0000000000001000 2079: 2025-11-18 00:26:16 <06465> R14: 0000000000000010 R15: 00007f42d1e00000 2080: 2025-11-18 00:26:16 <06465> RSI: 00007ffff815fc70 RDI: 0000000000000002 2081: 2025-11-18 00:26:16 <06465> RBP: 00007ffff815ffc0 RSP: 00007ffff815fc70 2082: 2025-11-18 00:26:16 <06465> RIP: 00007f42d475ce41 EFLAGS: 0000000000000246 2083: 2025-11-18 00:26:16 <06465> CS: 0033 FS: 0000 GS: 0000 2084: 2025-11-18 00:26:16 <06465> Trap: 0000000000000000 Error: 0000000000000000 2085: 2025-11-18 00:26:16 <06465> OldMask: 0000000000000000 2086: 2025-11-18 00:26:16 <06465> CR2: 0000000000000000 2087: 2025-11-18 00:26:16 <06465> stack: 0x7ffff815fc70 - 0x7ffff8163b20 2088: 2025-11-18 00:26:16 <06465> Backtrace: 2089: 2025-11-18 00:26:16 <06465> [0x7f42d475ce41] => /usr/lib/x86_64-linux-gnu/libc.so.6 2090: 2025-11-18 00:26:16 (gsignal+0x00000141) liboffset 00038e41 2091: 2025-11-18 00:26:16 <06465> [0x7f42d4746557] => /usr/lib/x86_64-linux-gnu/libc.so.6 2092: 2025-11-18 00:26:16 (abort+0x00000123) liboffset 00022557 2093: 2025-11-18 00:26:16 <06465> [0x7f42d479e370] => /usr/lib/x86_64-linux-gnu/libc.so.6 liboffset 2094: 2025-11-18 00:26:16 0007a370 2095: 2025-11-18 00:26:16 <06465> [0x7f42d47a572a] => /usr/lib/x86_64-linux-gnu/libc.so.6 liboffset 2096: 2025-11-18 00:26:16 0008172a 2097: 2025-11-18 00:26:16 <06465> [0x7f42d47a6d6c] => /usr/lib/x86_64-linux-gnu/libc.so.6 liboffset 2098: 2025-11-18 00:26:16 00082d6c 2099: 2025-11-18 00:26:16 <06465> [0x008ba40f] => /bin/confsyncd 2100: 2025-11-18 00:26:16 <06465> [0x008becb2] => /bin/confsyncd 2101: 2025-11-18 00:26:16 <06465> [0x008bf29d] => /bin/confsyncd 2102: 2025-11-18 00:26:16 <06465> [0x008bf61c] => /bin/confsyncd 2103: 2025-11-18 00:26:16 <06465> [0x008b215a] => /bin/confsyncd 2104: 2025-11-18 00:26:16 <06465> [0x008af7f3] => /bin/confsyncd 2105: 2025-11-18 00:26:16 <06465> [0x008ad2e8] => /bin/confsyncd 2106: 2025-11-18 00:26:16 <06465> [0x008b2cf3] => /bin/confsyncd 2107: 2025-11-18 00:26:16 <06465> [0x0044d21f] => /bin/confsyncd 2108: 2025-11-18 00:26:16 <06465> [0x004527d8] => /bin/confsyncd 2109: 2025-11-18 00:26:16 <06465> [0x004530c6] => /bin/confsyncd 2110: 2025-11-18 00:26:16 <06465> [0x00455818] => /bin/confsyncd 2111: 2025-11-18 00:26:16 <06465> [0x004562c4] => /bin/confsyncd 2112: 2025-11-18 00:26:16 <06465> [0x7f42d4747e1b] => /usr/lib/x86_64-linux-gnu/libc.so.6 2113: 2025-11-18 00:26:16 (__libc_start_main+0x000000eb) liboffset 00023e1b 2114: 2025-11-18 00:26:16 <06465> [0x00448afa] => /bin/confsyncd 2115: 2025-11-18 00:26:16 <06465> fortidev 6.0.2.0008 2116: 2025-11-18 00:26:16 the killed daemon is /bin/confsyncd: status=0x6 2117: 2025-11-18 01:26:19 confsyncd crashed 1 times. The latest crash was at 2025-11-18 00:26:16. Following the crash, the blades may become out-of-sync, which can be verified by running the command below: diagnose load-balance status Note: In a multi-VDOM setup, run this command in the global VDOM: Slot 1: FPC6KFT0XXXXXXX Status:Working Function:Active Link: Base: Up Fabric: Up Heartbeat: Management: Good Data: Good Status Message:"Waiting for configuration sync." To fix this issue, recalculate the confsync checksum by running the following commands in the global VDOM on the FIM/MBD. diagnose sys confsync csum-recalculate Note: If HA also becomes out-of-sync and no checksum difference is found, run the following command to fix the problem: diagnose sys ha checksum recalculate The engineering team is currently working on this issue, and the permanent fix will be released in FortiOS versions 7.4.10. and 7.6.5. Related articles: Troubleshooting Tip: FortiGate Chassis blade config synchronization issues (confsync)  Technical Tip: FortiGate-6000/7000 Chassis health check commands