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

[Solved] Polling engines goes down after upgrading NPM to V10 Incl. SP1.

After upgrading from NPM 9.5 SP4 to V10 with SP1, my Polling engines goes down.

Under "Admin" / "Polling engines" status equals Down. I have an addtional polling engine which also is marked as down.

NetPerfmonService are runing on both servers, but cpu usage is 0??? Look at picture.

I can not stop the service, unless i am using task manager. Restarting the service does not solve the problem. Restarting all SolarWinds services does not solve the problem. Reboot of servers solve the problem, for a while.
Last time the Polling worked for 15 hours before the polling engines went down again.

I have a suspicion to the primary poller. Maybe its only necessary to boot the primary poller.

Anybody have a clue on whats going on?

SWO-NPM10-error1.jpg

Find more posts tagged with

Accepted answers

MFA

Solved. Problems with database, which NPM 9.5.1 did not discover. Size of database 70+ gigs. NPM V.10 could not work with the database in this condition, and therefore the polling engines went down.

I stopped all SolarWinds services on both polling engines, and did a database maintenance job which went on for 48 hours! After that the NPM has worked perfectly. The daily database maintenance has clearly not worked under ver. 9.5.1.

All comments

Rane

We had polling stop several times since NPM 10 Sp1. I heartily recommend a reboot of the poller and the SQL box as a start. We had issues with the DB connections timing out. Orion support busted our chops about running SQL on a VM on a SAN but its been that way since 7 and been running fine (course it may be that 10 is different... we're still holding our breath to see) but when we looked our SQL guy said that the queries and db design were sub-par and that a APM related process had gulped lots and lots of CPU and was stopping the poller form talking to the DB. We downed them all and brought them up and its been better (not perfect) since.

Roger

MFA

The polling servers get marked as down when the database archive job starts at 2:15. If i run database maintance is the same.

Stops here...

Maybe something is worng with the database, but it worked perfect on NPM 9.5.1...

MFA

Solved. Problems with database, which NPM 9.5.1 did not discover. Size of database 70+ gigs. NPM V.10 could not work with the database in this condition, and therefore the polling engines went down.