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

NetPerfMon shutdown time

The release notes for 9.1 state that the NetPerfMon service will shutdown immediately as opposed to taking forever to do so. This has not been my experience. SP installs still fail every time because NetPerfMon takes 10+ minutes to shutdown. It seems that even if I kill the process before the installation of the SP, it starts the service after installation, and has to stop it again when the Configuration Wizard is run, which dies yet again because NetPerfMon won't stop in a timely fashion.

This occurs on both my production server and a new server I am building using an Eval version of 9.1.

Find more posts tagged with

Accepted answers

FormerMember

In most cases, it does shut down immediately, but we've noticed some cases where it takes longer than expected. We'll take another cut at making it shut down more quickly in more cases in a future release.

All comments

FormerMember

smcdonald

Yep - I've seen the same thing now for quite a while - it seems related to the number of elements being monitored. I had around 10,000 elements on my server and it would take nearly 15minutes - you could see the memory slowly being reduced if you watched it in taskmgr...

I recently got the polling engine and offloaded about 7000 onto the polling engine - the main server now can shut the service down within 1-2mins - the polling engine however takes 10+ minutes... I use the taskmgr to kill it often during upgrades - and turn off the Restart The Service option if it fails in the service manager.

I'm looking forward to it shutting down quickly in the future - it makes upgrades a real pain...

MarkHamlin

When you kill the netperfmon process on the primary NPM server, can you tell if you're loosing data that the poller on the primary may have collected?

jbaulsir

We saw the same behavior after the 9.1 sp 3 install.

JasonKV

When you kill the netperfmon process on the primary NPM server, can you tell if you're loosing data that the poller on the primary may have collected?

I would also like to know this. As I have read a number of times on here to just kill the process I am uncomfortable doing so as I was under the impression that it was dumping collected data from memory to the database. Killing it would discard this data? Would be interested in knowing what actually happens.

JasonKV

When you kill the netperfmon process on the primary NPM server, can you tell if you're loosing data that the poller on the primary may have collected?

FormerMember

Killing the process won't corrupt your data. You can kill it and rest easy.

smcdonald

When I need to kill this manually - for instance when installing a service etc - I set the Recovery Options on the MMC services tab for the NetPerfMon service to "Take No Action" - that way windows wont try to restart it when you kill it. Note that everytime you run the Config Wizard it resets this to "Restart The Service".

I think killing it should definately be the default option from Solarwinds when it tries to stop/restart services while installing updates/upgrading - otherwise I need to babysit the service and kill it/restart it manually when doing upgrades these days - a real pain...