Network Management

High Value for Last Database Sync in Polling Engines Page or Data is Not Polling in Orion

Steps to take if the Last Database Update is more than 60 minutes and Last Database Sync is showing a high value and Data is not polling on the Polling Engine. Repairing services, repairing Orion core services, Example: -Last database sync is high E.G. 60 minutes and 3 seconds ago. -Polling engines not updating correctly. Polling engines page showing red database sync status -Data is not polling correctly

First published date

4/24/2019 2:35 PM

Last published date

11/19/2024 4:03 PM

Overview

When you go to Settings > All Settings > Polling Engines, the Last Database Update is showing a high value. There are many reasons for a high database sync value, all issues trace back to the polling engine not being able to communicate with the database. This article lists the most common causes for such an issue and how you can resolve it.

Product section

Orion Platform

Cause

  • SQL Server Time Zone Settings should be in sync with the Orion Server/s
  • Unlicensed polling engine
  • Permissions issue on the Orion server
  • Job Engine, Collector Service, Information Service failing
  • Polling Engine does not have sufficient resources (CPU, Memory, Etc.)
  • Both pool members of a pool are showing active in Engines table.

Resolution

  1. Verify the polling engine is licensed.
    1. Ensure there is a license applied to the polling engine within the web-based license manager: Settings > All Settings > License Manager.
    2. Alternatively, you can verify if Syslog and Trap services are started on the polling engines. Use the Orion Service Manager to check the status of these two services.
  2. Run the OrionPermission Checker using the article: Check permissions using the Orion Permission Checker.
  3. Ensure that the port is not being blocked by the firewall

Testing port connectivity can be performed with Database Manager (simply query the database). Or it can be performed with this PowerShell command. Replace the SQLServerHostName with SQL server hostname/IP address. 

# Scripts are not supported under any SolarWinds support program or service.
# Scripts are provided AS IS without warranty of any kind. SolarWinds further
# disclaims all warranties including, without limitation, any implied warranties
# of merchantability or of fitness for a particular purpose. The risk arising
# out of the use or performance of the scripts and documentation stays with you.
# In no event shall SolarWinds or anyone else involved in the creation,
# production, or delivery of the scripts be liable for any damages whatsoever
# (including, without limitation, damages for loss of business profits, business
# interruption, loss of business information, or other pecuniary loss) arising
# out of the use of or inability to use the scripts or documentation.

Test-NetConnection -ComputerName SQLServerHostName -port 1433

  1. Orion Server and SQL Server time should be in sync
  2. Restart Orion Services using the Orion Service Manager or Reboot the Polling Engine
  3. Run the Configuration Wizard to re-establish the connection to the database:
  4. If the issue persists, repair the Job Engine, Collector, and Information Service on the Orion server: Repair a failing Job Engine, Collector, and Information service in Orion Platform
  5. Make sure that the Polling Engine (Main or Additional Poller) has sufficient resources as mentioned in the article: Deployment sizing guidelines for the SolarWinds Platform
  6. Lastly, upgrade to the latest version/Hotfix of Orion: Perform a centralized upgrade of an existing deployment

For customers who have HA and the servers are in an HA Pool, make sure the Engines table does not contain both pool member entries. If yes, then remove the standby member from the Engines table.