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

Polling engine not in sync

Hi everyone,

I have a curious issue with NPM right now. I have the 2 polling engines in SolarWinds, one the main NPM and the other an additional polling engine (PE2). Whenever I start the System Manager and get into the screen where I get to select the polling engine, it says there that the 2nd polling engine is not in sync, with the date of the last database sync. Its the same issue when i open the Monitor Polling Engines tool, says also that PE2 is down.

But when I look in the web console all the nodes assigned in PE2, they are still gathering data and is very much updated. This means that the data it polls is still being stored in the database right?But why does it say that its not in sync when I still have data being polled?

Find more posts tagged with

network_performance_monitor

Accepted answers

All comments

GoldTipu

Is your SQL & all Polling engines are in same time zone having same time sync ?

epenney

We had similiar issue. One of our additional pollers was no longer sync'ing, however SNMP statistics continued to be gathered for the nodes managed by this poller - this seemed odd, however ICMP data (response time, latency) were no being collected. I'm curious if the data you see as still being collected is the SNMP or ICMP data ?

There were no events to catch this. I've just created an alert such that if last sync time is greater than or equal to 15min (for example) - please alert us.

In our case it seems to be triggers by config wizard type event on main poller (ie: services were briefly stopped/started). Its very odd that only 1 of our add'l pollers is consistently affected when this happens, however our 2nd add'l poller never has an issue.