Troubleshooting Tip: The miglogd daemon crashes frequently with FortiOS v7.2.7 causing the issue when miglogd application attempts to process logs

1. After upgrading FortiGate firmware version to v7.2.7, FortiGate does not function properly when the miglogd application attempts to process logs.
   
   
2. To check the issue, run the following CLI command:

diagnose debug crashlog read

It will show the result as below.

16174: 2025-02-24 09:35:45 <03557> firmware FortiGate-VM64 v7.2.7,build1577b1577,240131 (GA.M) (Release)

16175: 2025-02-24 09:35:45 <03557> application miglogd

16176: 2025-02-24 09:35:45 <03557> *** signal 11 (Segmentation fault) received ***

16177: 2025-02-24 09:35:45 <03557> Register dump:

16178: 2025-02-24 09:35:45 <03557> RAX: 00007f970ed64afb   RBX: 00000000103da160

16179: 2025-02-24 09:35:45 <03557> RCX: 0000000000004000   RDX: 00000000000086cf

16180: 2025-02-24 09:35:45 <03557> R08: 00007f970ed64afb   R09: 00007f972eeec0e0

16181: 2025-02-24 09:35:45 <03557> R10: 000000000000fc54   R11: 00007f972ef40340

16182: 2025-02-24 09:35:45 <03557> R12: 000000000000fc54   R13: 0000000010329380

16183: 2025-02-24 09:35:45 <03557> R14: 00000000011ebc30   R15: 00007f9728ddd548

16184: 2025-02-24 09:35:45 <03557> RSI: 00007f9728de4a91   RDI: 00007f970ed6c040

16185: 2025-02-24 09:35:45 <03557> RBP: 00007ffcab792bf0   RSP: 00007ffcab792bc8

16186: 2025-02-24 09:35:45 <03557> RIP: 00007f972eeec123   EFLAGS: 0000000000010206

16187: 2025-02-24 09:35:45 <03557> CS:  0033   FS: 0000   GS: 0000

16188: 2025-02-24 09:35:45 <03557> Trap: 000000000000000e   Error: 0000000000000007

16189: 2025-02-24 09:35:45 <03557> OldMask: 0000000000000000

16190: 2025-02-24 09:35:45 <03557> CR2: 00007f970ed6c000

16191: 2025-02-24 09:35:45 <03557> stack: 0x7ffcab792bc8 - 0x7ffcab792f00

16192: 2025-02-24 09:35:45 <03557> Backtrace:

16193: 2025-02-24 09:35:45 <03557> [0x7f972eeec123] => /usr/lib/x86_64-linux-gnu/libc.so.6  liboffset

16194: 2025-02-24 09:35:45 00135123

16195: 2025-02-24 09:35:45 <03557> [0x011d790f] => /bin/miglogd

16196: 2025-02-24 09:35:45 <03557> [0x011eb82b] => /bin/miglogd

16197: 2025-02-24 09:35:45 <03557> [0x011ebccb] => /bin/miglogd

16198: 2025-02-24 09:35:45 <03557> [0x011ebade] => /bin/miglogd

16199: 2025-02-24 09:35:45 <03557> [0x011ebe9c] => /bin/miglogd

16200: 2025-02-24 09:35:45 <03557> [0x02a65156] => /bin/miglogd

16201: 2025-02-24 09:35:45 <03557> [0x011ed493] => /bin/miglogd

16202: 2025-02-24 09:35:45 <03557> [0x00449e37] => /bin/miglogd

16203: 2025-02-24 09:35:45 <03557> [0x7f972eddadeb] => /usr/lib/x86_64-linux-gnu/libc.so.6

16204: 2025-02-24 09:35:45 (__libc_start_main+0x000000eb) liboffset 00023deb

16205: 2025-02-24 09:35:45 <03557> [0x004450da] => /bin/miglogd

16206: 2025-02-24 09:35:45 <03557> fortidev 6.0.1.0005

To check the usage of miglogd, run the following debug. If the crash is too frequent, the debug might capture the info about the miglog daemon and help to understand the reason behind the crash.

diagnose debug reset

diagnose debug application miglogd -1

diagnose debug console timestamp enable

diagnose debug enable

To fix:

For a permanent fix, it is necessary to upgrade FortiGate firmware version to v7.2.9, v7.4.4, and above.