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

Polling Engine Down Since Update 10.2.1

Ballzo

Since I updated to 10.2.1 on Monday, my polling engine says its down. Anyone have this issue or know of a fix? I already tried to do a repair installation with the help of support but it didn't work and I have not heard back from them in a few hours.

Find more posts tagged with

Accepted answers

All comments

byrona

What specifically isn't working? When you open the Orion Service manager, which services are not running? I ran into a very similar problem yesterday when I upgraded so I may be able to help.

Ballzo

Everything appears to be running but the polling engine says its down.

Polling Engine on ENTSW01
Engine Status	Polling Engine Down
Type of Polling Engine	Primary
Polling Engine Version	SolarWinds Orion Core Services 2011.2.1
IP Address
Last Database Sync	231 minutes 49 seconds ago
Polling Completion	66.93
Elements	15882
Network Node Elements	940
Volume Elements	1495
Interface Elements	13447
Polling Rate	131% of its maximum rate. Polling intervals increase if the polling rate exceeds 100% of the maximum rate. Add Poller » Learn more
Total Job Weight	3581

byrona

Unfortunately this doesn't look like the same problem I encountered. From the looks of this your polling engine is getting overwhelmed and giving up.

cdh

Did you have 15882 elements on this single polling engine prior to the upgrade? That seems like a lot for one polling engine.

Ballzo

Yes. nothing changed there.

danielleh

Hi Ballzo--

I have this marked for the PM to comment on.

Thanks,
DH

savell

I have the same issue after application of 10.2.1 (from 10.2).

Of 4 polling engines, 1 is reporting down (although it is collecting data - and appears to be functioning correctly). Tried a number of config wizards, repairs etc, but no change).

I'll raise a case.

Dave.

filipv

Are the system clocks on all sw servers in sync?

savell

Yes, all the servers are keyed from the same ntp source, and all are in sync (and in the same timezone).

Support understand the poller status issue and have a fix in train (the keepalive for the poller status can't run while the topology calculation is updating - and ours is taking a very very long time...)

Our issue number for this problem is 301623.

I also then started taking a look at why the topology update was taking so long. I opened a case 302090 to investigate why errors were appearing in the log files (NPM polling devices for OID's that are not supported by a subset of our devices). ET thinks (above) that this is not related to the topology calculation duration - but I'll get these errors sorted out and then chase that aspect further.

Dave.

Your issue with errors in Collector Core log file is related to insufficient security rights for topology polling on your devices. We are not able to get detail information about VLANs.

Error code returned from SNMP device.
SNMP_ERRORSTATUS_AUTHORIZATIONERROR - 16

savell

Thanks for such a quick response ET!

I'll have a look and see what could be causing this - we don't generally have snmpviews defined that limit access to any specific OID(s) on our devices.

Dave.