Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Memory Leak in Orion 8.5.1?

We've recently had to reboot our Orion servers a couple of times because the CPU becomes maxed out and the memory utilization goes way too high as well (see attached graphs).

We're running 8.5.1 as well as Netflow 2.2.1.

Has anyone else run in to this issue? The SQL server is on a separate box, and the physical hardware is beefy on both, so I don't think it's a hardware issue. We didn't seem to have this issue before upgrading to 8.5.1.

Thanks,

--Ron

Orion CPU Usage.JPG

Find more posts tagged with

Accepted answers

All comments

TinyElvis

Here is the memory Utilization

Orion Memory Usage.JPG

aLTeReGo

Have you narrowed the leak down to a specific process? Checkout this post and see if it's related.

savell

Our Orion graphs look very similar. In our case it is caused by dllhost.exe (the issue also existed prior to 8.5.1)

We do a regular unload of the Solarwinds COM+ application (via the Orion Service Manager) which appears appears to terminate the running dllhost process and restart another.

When dllhost.exe gets to 300+ meg CPU starts to increase and we also get missed polls. Anyone know how we can schedule an automatic night unload of this process?

Dave.

aLTeReGo

Anyone know how we can schedule an automatic night unload of this process?

Couldn't you create a scheduled task that executed an "IISRESET /RESTART" command?

TinyElvis

Now that you mention it, yeah, ours was the same process that got out of control. We could always shut down the Orion services and start them back up again, and things seemed to get better. Of course, we would always reboot just to be safe, however.

aLTeReGo

We could always shut down the Orion services and start them back up again, and things seemed to get better.

I'm restarting the Custom MIB Poller once every hour to keep the memory footprint at a reasonable size. I also notice that when it grows out of control it starts to miss polling cycles. Hopefully we'll see a fix shortly.