Same thing here, on 5.4.2 on a 90D. Also see "netscan" jumping up as well.
If there were a way to make "reportd" and "netscan" into "low priority" (shows as "N" on diag sys top) I wouldn't have a problem, but as it is "reportd" grabs so many CPU cycles that it's impacting users
Did you every find a solution for this? I am having the exact same problem, and it happens very often (every hour or so). Reportd suddenly using 99% CPU, which stops when I kill it (and it automatically reloads). Then, before too long, it happens again. I am still setting up this unit for the first time, so I have a very simple setup (nearly stock) and just a couple computers sitting on it, in a test environment.
I have a Fortigate 90D running 5.4.3.
We've found other things that drive the CPU nuts, one is VPN'ing out with SSLVPN back into the same subnet, but that makes sslvpnd go high CPU, not reportd and not netscan. And a simple rule blocks the SSLVPN loopback.
Wish I had an answer to the reportd load problem other than a multi-core new box (like the 61E instead of 90D we have).
I do not have any policies in learning mode. I also tried executing a factory reset, and the problem still occurred even with only 2 WAN interfaces and one hardware switch with 802.1x authentication and DHCP defined, three IPV4 policies, a RADIUS and RSSO server, and one RSSO group. Those were literally the only things configured after the factory reset, and reportd still jumped up to 99%.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.