nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

cirrusmonitorserver.exe using 1.2GB of Memory

FormerMember

Not exactly sure why it was doing this. Why would it be taking this much memory?

Find more posts tagged with

Accepted answers

All comments

chris.lapoint

I would suggest submitting a support ticket with these details on your install to help with troubleshooting. I expect they'll want to get logs as well:

What version of Cirrus are you running? How many nodes?
Is node monitoring enabled? If so, does disabliing reduce memory used?
Did this problem recently occur? If so, what/if any jobs or settings changes have you made?

FormerMember

Funny thing is was in a stuck citrix session - bounced the session and it went away.

chris.lapoint

That's good news. Let us know if you see this again because we'd definitely want to address if its really a Cirrus issue.

FormerMember

Chris I'm looking at the task manager again and this .exe is running under a users account. How does this service/process start and where can I change this to a service based account rather than a users account?

CoreyMac

This same thing happens to us. I just stopped the process and logged back in and the memory and CPU have been released. We end up using 400-1000MB when it hangs up and even after the user interface is closed down the process stays and buries a CPU.

This is most likely to happen when two of us are in it and at least one stays in the GUI for a long time. Hard to reproduce and only happens once or twice a week, though we do not use Cirrus GUI every day... Maybe since the automated jobs run to collect configs at 5pm, if we are in the GUI at that time that is what triggers it... Hard to say, but you are not alone...