Troubleshooting Tip: High CPU due to initXXXXXXXXXXX process

MichaelTorres · ‎12-26-2024

Description

This article resumes the basic troubleshooting when initXXXXXXXXXXX process is taking 99% of one CPU core.

Scope

FortiGate has 90-99% consumption in one of its cores due to the initXXXXXXXXXXX process.

Solution

Check the process using more CPU:

FGT_A $ diag sys top-all 3 30 10
�[H�[JRun Time: 75 days, 7 hours and 57 minutes
6U, 0N, 2S, 87I, 5WA, 0HI, 0SI, 0ST; 24101T, 15590F
initXXXXXXXXXXX 1 R 97.0 0.0
bcm.user 228 S < 12.0 0.4
snmpd 2454 S 6.5 0.4

Check the crash log or try to enable debugs. It may be seen as a loop of stack outputs:

16376: 2023-08-31 07:39:45 dbg_stack_print_to_b 123 0.000000 1
16377: 2023-08-31 07:39:45 dum_signal 1549 0.000000 1
16378: 2023-08-31 07:39:45 dbg_stack_print_to_b 123 0.000077 1
16379: 2023-08-31 07:39:45 dum_signal 1549 0.000077 1
16380: 2023-08-31 07:39:45 dbg_stack_print_to_b 123 0.000153 1

INIT is the parent of all userspace processes, it can not be killed.

Workaround:

To kill the process, restart the FortiGate.

Final solution:

Upgrade to v7.4.4.