There is a bug in v5.0.4
Two issues:
The cmdbsvr process dies and restarts with excessive CPU usage.
I have to kill it with: diag sys kill 11 <pid>
where pid is the number of the process when you do a diag sys top command
example:
diag sys top
Run Time: 32 days, 0 hours and 47 minutes
2U, 78S, 20I; 3959T, 1525F, 253KF
cmdbsvr 2418 R 93.6 0.5
ipsengine 74 S < 53.8 2.5
ipsengine 75 S < 28.2 2.6
hatalk 2427 S < 25.9 0.2
ipsengine 84 S < 18.6 2.6
miglogd 47 R 16.4 0.4
newcli 6749 R 14.4 0.3
ipsengine 83 S < 12.7 2.6
ipsengine 68 S < 6.1 2.6
proxyworker 58 S 5.4 2.0
urlfilter 82 S 5.4 0.5
stpd 117 S 3.4 0.2
ipsengine 2874 S < 2.9 2.5
snmpd 92 S 2.1 0.2
proxyworker 65 S 1.3 1.1
reportd 90 S 1.3 0.5
forticron 80 S 1.3 0.3
hasync 2428 S < 1.1 0.3
sshd 6747 S 1.1 0.3
proxyacceptor 57 S 0.9 0.0
the PID is 2418 so to kill the process with signall 11 (restart) the command is
diag sys kill 11 2418
The second issue that was found by the engineers, is that the ipsengine is reading a file incorrectly and can cause high CPU usage. I don' t usually kill this process as the cpu usage tends to go back down by itself.
Rick