Fortigate f40 crash

[rasulzade]

Hello everybody! A few days ago, I encountered a problem with my Fortigate F40 hanging. The problem was solved by rebooting, after updating to version 7.2.10, it went into the boot loop. The firmware for an earlier version 7.2.3 helped, then updated to 7.4.5. The Internet disappeared in the evening, then appeared in the morning by itself.

Here is the crash log: 

1: 2024-10-27 03:36:16 the killed daemon is /bin/sflowd: status=0x0
2: 2024-10-27 03:36:29 the killed daemon is /bin/sshd: status=0x100
3: 2024-10-27 03:48:34 the killed daemon is /bin/getty: status=0x0
4: 2024-10-27 03:48:46 Interface a is brought down. process_id=1700, process_name="cmdbsvr"
5: 2024-10-27 03:48:46 Interface lan1 is brought down. process_id=1700, process_name="cmdbsvr"
6: 2024-10-27 03:48:46 Interface lan2 is brought down. process_id=1700, process_name="cmdbsvr"
7: 2024-10-27 03:48:46 Interface lan3 is brought down. process_id=1700, process_name="cmdbsvr"
8: 2024-10-27 03:48:46 Interface wan is brought down. process_id=1700, process_name="cmdbsvr"
9: 2024-10-27 14:51:45 the killed daemon is /bin/sflowd: status=0x0
10: 2024-10-27 15:03:28 the killed daemon is /bin/csfd: status=0x0
11: 2024-10-27 15:03:28 the killed daemon is /bin/eap_proxy: status=0x0
12: 2024-10-27 15:28:35 Interface lan1 is brought down. process_id=695, process_name="httpsd"
13: 2024-10-27 15:28:35 Interface lan2 is brought down. process_id=695, process_name="httpsd"
14: 2024-10-27 15:28:35 Interface lan3 is brought down. process_id=695, process_name="httpsd"
15: 2024-10-27 15:30:35 the killed daemon is /bin/sflowd: status=0x0
16: 2024-10-27 15:30:45 the killed daemon is /bin/sflowd: status=0x0
17: 2024-10-27 15:37:37 the killed daemon is /bin/sflowd: status=0x0
18: 2024-10-28 05:00:41 the killed daemon is /bin/sflowd: status=0x0
Crash log interval is 3600 seconds.

Please help me with the solution.

[abarushka]

Hello,

I cannot spot any suspicious log entries in the crashlog.

I would recommend to connect laptop to the unit via the physical cable console and wait for the issue to be triggered again. Once the issue it triggered please check whether crashlog is generated.