SolarWinds HA showing as AdditionalPoller instead of AdditionalPollerStandby

Dear Community members,

I am having strange case here. We have and Active and Standby Polling Engine in a Pool but from last few days both are showing as Active in the HA Pool. When checked in registry editor, the Install type for the Standby server is showing as AdditionalPollerStandby where as for the RunType it is showing as AdditionalPoller instead of AdditionalPollerStandby.

I tried to update the Registry values manually after disabling the services. It gets updated to AdditionalPoller value but as soon as I start the High Availability Service in the Standby Server, the value gets reverted and starts showing as AdditionalPoller instead of AdditionalPollerStandby.

Has anyone faced the similar issue or any fix for this? Both Servers are shwoing as Active-Active.

Thanks

Vikas Pandita

Find more posts tagged with

Orion Platform

SolarWinds Orion

pool

High Availability

Accepted answers

All comments

stevenstadel

Try Resolution 2 - Make sure everything is shutdown on the expected standby server. support.solarwinds.com/.../High-Availability-not-working-after-reboot

vikasp

I have updated the registry but it reverts to the same position within a minute

stevenstadel

Make sure that the SolarWinds High Availability Service is Stopped on the servers before you change the reg key. That way it will not change the key back. If you are still having issues you may need support to help you rebuild HA.

My Steps

Stop SolarWinds High Availability Service on both servers. (Services.msc)
Check the High Availability registry key on the Active Main Poller, Standby, and all Additional Pollers.
1. Open the Registry Editor (regedit.exe)
2. Navigate to:
  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Solarwinds\HighAvailability
3. Examine the RunType value and double-click to update (if necessary). Verify the following:
  - On the active primary polling engine, the RunType value must be MainPoller.
  - On the Standby primary polling engine, the RunType value must be MainPollerStandby.
  - On an active APE, the RunType value must be AdditionalPoller.
  - On a Standby APE, the RunType value must be AdditionalPollerStandby.
  - Start the SolarWinds High Availability Service on the primary server using the Services.MSC.
Make sure to set Startup Type to the following On Active Poller(s):

Services.msc

Name	Status	Startup Type
SolarWinds Administration Service	Running	Automatic
SolarWinds Agent Service	Running	Automatic
SolarWinds Alerting Service V2	Running	Manual
SolarWinds Collector Service	Running	Manual
SolarWinds Cortex Service	Running	Manual
SolarWinds High Availability Service	Running	Automatic
SolarWinds Information Service	Running	Manual
SolarWinds Information Service V3	Running	Manual
SolarWinds Job Engine v2	Running	Manual
SolarWinds Orion Module Engine	Running	Automatic
SolarWinds Recommendations	Running	Manual
SolarWinds Syslog Service	Running	Manual
SolarWinds Trap Service	Running	Manual

Start the SolarWinds High Availability service on the Standby server.
Make sure to set Startup Type to the following on Standby Poller(s):

Services.msc

Name	Status	Startup Type
SolarWinds Administration Service	Running	Automatic
SolarWinds Agent Service	Running	Automatic
SolarWinds Alerting Service V2		Disabled
SolarWinds Collector Service		Disabled
SolarWinds Cortex Service		Disabled
SolarWinds High Availability Service	Running	Automatic
SolarWinds Information Service		Disabled
SolarWinds Information Service V3		Disabled
SolarWinds Job Engine v2		Disabled
SolarWinds Orion Module Engine	Running	Automatic
SolarWinds Recommendations		Disabled
SolarWinds Syslog Service		Disabled
SolarWinds Trap Service		Disabled

This is a PowerShell script that will query the regkey instead of manually doing it, run it under a credential that has access to the servers.

$servers = @( "MainPollerA",  "MainPollerB",  "AdditionalPoller1A", "AdditionalPoller1B", "AdditionalPoller2A", "AdditionalPoller2B", "AdditionalPoller3A", "AdditionalPoller3B", "AdditionalPoller4A", "AdditionalPoller4B" )

ForEach ($srv in $servers) {
    Invoke-Command -ComputerName $srv -ScriptBlock {
        [string] $installType = (Get-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\SolarWinds\HighAvailability" -Name "InstallType" -ErrorAction "SilentlyContinue").InstallType
        [string] $RunType = (Get-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\SolarWinds\HighAvailability" -Name "RunType" -ErrorAction "SilentlyContinue").RunType

        $computerName = $env:computername

 #       if ($installType -ne $RunType) {
            Write-Output "$computerName :: InstallType ($installType) - RunType ($RunType)"
  #      }
    }
}

KITGuy

My install has been doing this for months. It will also create a duplicate VIP sometimes. It eventually makes the Orion Module service stop on the non active server.

I have manually set them to the correct registry settings after stopping the services and it re-occurs.

I have just upgraded to 2024.4 and it is still doing it.