We're noticing that the SolarWinds agent is consuming a significant amount of RAM on our servers.
In this instance, it's using over 3GB.
Restarting the agent does temporarily alleviate the issue. I'm thinking of running a scheduled task on all my servers to restart the agent daily, but that seems to be masking the problem.
Does anyone have any ideas on how to resolve this?
I can't speak for other people, but yes is the Solarwinds.ServiceHost.Process that's eating up the memory in our environment. This screenshot says it all, Solarwinds.ServiceHost.Process is talking 6.45 Gig of memory from one system, while taking over a Gig of memory on other systems.
Thank you to everyone who opened a support cases regarding the issue outlined in this thread. Because of your assistance our engineering teams have identified the cause of the issue and are now working on developing a fix.
Cpeheotel, Yes hotfix 6 didn't do much to resolve our issue either. Our case #00155294 is still open and every couple of days we get the usual, "....update from DEV and they are requesting another dump files for the specific service...". I wouldn't be surprised if we've sent them a dozen dump files by now.
I won't be much help here other than saying you're not alone. We have the agent running on about 100 nodes in our environment and since we upgraded to 2018.2, we've hit a few instances where the agent just start swallowing RAM. We restart the service and it goes away. I opened a support case for it but the only "solution" that was given was to restart it, which really feels unacceptable as a response. I had even captured full agent logs and submitted them with my support case but never got a solid answer on why.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.