NPM Next Poll in the past

10/10/2019 9:54 AM

4/25/2025 6:54 PM

Every node displays Next Poll time within the NPM Node Details page; you can also find this information within the Database. Although sometimes, the next poll may show the time in the past; for example, the current time is 14:32, but the Next Poll show 14:29, even though the node is still polling and the next poll does update. 

Though the value may stay in the past, behavior like this means the node doesn't poll at all.

Scenario 1:

• The NPM Collector plugins, C:\Program Files (x86)\SolarWinds\Orion\NPM\SolarWinds.NPM.Collector.dll.config, got corrupted, and you'll see below error in the logs for the Job Engine worker process

[SWJobEngineWorker2.exe][9] FATAL SolarWinds.JobEngine.WorkerProcess.WorkerControllerService - (null) Exception caught 
System.Configuration.ConfigurationErrorsException: Configuration system failed to 
initialize ---> System.Configuration.ConfigurationErrorsException: Data at the root level 
is invalid. Line1, position 1. (C:\Program Files 
(x86)\SolarWinds\Orion\NPM\SolarWinds.NPM.Collector.dll.config line 1) ---> 
System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.

Scenario 2:

• The [NextPoll] is not updating, but the [LastSync] is.

Scenario 3:

• NextPoll is not updating and ICMP filing from Orion - even to localhost IPv4 address and loopback address.

Network Performance Monitor

Scenario 1:

• Usually, the cause for this is corrupted / incomplete DB files, this can happen due to a lot of network issues as the DB files are vague and provide inaccurate data or disk space. To get a better understanding, please provide Diagnostics for SolarWinds Support to review logs.
• Corrupted NPM Collector Plugin config

Scenario 2:

• Status [Pollers] are missing

Scenario 3:

• Faulty NIC indicated by following messages in Event logs

SystemModel: "ProLiant DL380 Gen9"
SystemName: "AEBCDEFGH.corp..com"
SystemProductID: "719064-B21"
SystemSerialNumber: "CZXU2349724"
TIME_CREATED: 132438674905620099 0x1d68445ec45de83
VariableNames[0]: "FloodControl"
VariableTypes[0]: 1 0x1 (string)
VariableValues[0]: "HP Ethernet detected too many changes happening to the network."
 
For more information, please contact HPE Support.

To possibly resolve this issue, please follow the steps on this article:

Repair a failing Job Engine and Collector Components 

OR

1. Connect to the Polling Engine with the issue.
2. Stop the SolarWinds services using the SolarWinds Platform Service Manager (Start, Stop, or Restart Orion Services with the Orion Service Manager)
3. Restart the SolarWinds services.

Scenario 1 Resolution:

Repair the SolarWinds Platform and run the Configuration Wizard.

1. Connect to the Polling Engine with the issue.
2. Open Control Panel from the Start menu and navigate to Programs and Features.
3. Select the SolarWinds Platform and click Repair.
4. Run the Configuration Wizard to complete the repair. 

NOTE: If that does not help, rebuild the Collector and Job engine SDF files as explained above.

Scenario 2 Resolution 1:

Either:

• Do a List Resources on the affected Node and ensure that Status Poller is assigned
• In the Web Console, go to Settings > All Settings > Manage Pollers, and assign Status Poller to the affected Nodes

Scenario 2 Resolution 2:

Turned out to be a faulty NIC card that needed to be replaced. Please check the NIC and make sure the SolarWinds server can ping both local IPv4 and IPv6 addresses to validate NIC functionality.