Technical Tip: CPU Utilization of 'cmdbsrv' Daemon Remains High for Approximately 11 Minutes After Rebooting FortiGate

[ssanga]

Description	This article provides a solution for an issue where the 'cmdbsrv' daemon on FortiGate devices experiences high CPU utilization (85% to 90%) for approximately 11 minutes after a reboot leading to temporary performance issues.
Scope	FortiGate v7.6.1.
Solution	After rebooting the FortiGate, the 'cmdbsrv' daemon exhibits high CPU utilization, typically between 85% and 90% for about 11 minutes. Once this period elapses, the CPU utilization of the 'cmdbsrv' daemon returns to normal. diagnose sys top 2 50 10:53:26 AM up 0 days, 0 hours and 4 minutes 0U, 0N, 0S, 100I, 0WA, 0HI, 0SI, 0ST; 387709T, 361363F cmdbsvr 9790 R 85.6 0.0 0 <After 11 Minutes>: 11:01:33 AM up 0 days, 0 hours and 12 minutes 0U, 0N, 0S, 100I, 0WA, 0HI, 0SI, 0ST; 387709T, 360582F cmdbsvr 9790 S 0.1 0.0 0 This issue has been resolved in v7.6.3; scheduled to be released in March 2025. These timelines for firmware release are estimates and may be subject to change. General debug information required by FortiGate TAC for investigation. Debugs: diagnose sys top 2 50 diagnose sys process pidof cmdbsvr diagnose sys process trace <PID> diagnose sys process dump <PID> diagnose sys process pstack <PID> diagnose sys process sock-mem <PID> TAC Report: execute tac report Configuration file of the FortiGate.