I am going to open a support ticket, but checking to see if anyone else had the Rapid7 Insight Agent taking up all the CPU after Windows patching?
I’ve not had any reports in our organisation. My own asset is running normally on the latest version of the agent post patching. Interested to hear what the cause was once it’s determined ?
Nothing on our side has been reported
Hi, I also have the same problem, but it started happening since Rapid7 version 4.0.16 and the error has never been fixed definitively.
I have two servers that, whenever I restart them, Rapid7 ends up using 100% of the CPU.
I’m still waiting for our provider to resolve the issue.
Yes, I have also been having the same issue since 4/7/25 which looks like that’s when 4.0.16 came out. Sometimes after patching the agent will take up all CPU and stay that way until the service is restarted. The longest I let it go is 4 days just see if it would eventually clear, which it didn’t. It only impacts single vCPU machines(since apparently the agent can only use 1 CPU). I’ve spent a lot of time working with Rapid7 support and the most I got out of them is a recommendation to upgrade to 2CPUs on every server. They did indicate that there is a command to rate limit the agent to 50% of a CPU. I feel like that is just a Band-Aid to the issue.
That was basically the same answer I got, increase from 2 vCPUs because the Agent can temporarily take up all of a single CPU. Didn’t leave me really comfortable
I’d be ok with that answer if it only temporarily took all the CPU. But in my case it just locks up 100% CPU forever until the service is restarted. I haven’t had an issue with those single CPU servers until April.