One or more Custom Node Pollers are in Unknown state

Following a clean-up of our environment I have noticed we have multiple nodes with the error "One or more Custom Node Pollers are in Unknown state".

When checking the pollers assigned there are no longer any assigned.

I have also checked the Universal Device Poller application,installed on the MPE and the devices have no customer pollers assigned however the nodes still appear with an unknown state.

Has anyone else expierenced this issue?

Version 2024.2.1

Find more posts tagged with

universal_device_poller

custom_node_properties

universal_device_pollers

Accepted answers

All comments

SOHanlon2

@GeneShogo I have found an article where you have experienced something similar, did you find a resolution?

bobmarley

That must be a bug, possibly open a ticket?

bobmarley

This started happening to me in 2024.0 just recently. Did you ever get it resolved?

SOHanlon2

This was raised with SolarWinds however, the issue was put down to the polling issues we have been having across our environment. Have you got similar issues with your environment?

bobmarley

It is still occurring. We just added 12 new polling engines and even after the nodes were moved to the new engines the problem still persists.

SOHanlon2

Might be worth raising a ticket to SolarWinds, Let me know if they provide a fix

bobmarley

I still have not found a resolution but here is the query I was using to troubleshoot. None of the pollers that get pulled up show unknown, they all are showing valid data.

SELECT 
    n.NodeID,
    n.Caption AS NodeName,
     n.StatusDescription AS StatusMessage,
    cpa.CustomPollerAssignmentID,
    cpa.AssignmentName AS PollerName,
    cps.Status AS PollerStatus
FROM 
    Orion.Nodes n
JOIN 
    Orion.NPM.CustomPollerAssignment cpa ON n.NodeID = cpa.NodeID
JOIN 
    Orion.NPM.CustomPollerStatus cps ON cpa.CustomPollerAssignmentID = cps.CustomPollerAssignmentID
WHERE 

n.StatusDescription LIKE '%Node status is Up, One or more Custom Node Pollers are in Unknown state.%'

md040864

I take it no one has found a solution to this yet, I am also seeing exactly the same issue in Version 2025.1

I have a support call open and will post the resolution, assuming one is found.

yer

Agreed, something similar happens to me, but to an earlier version, it was a bug, the workaround is to go to the data base an changes the sates to remove that unknown status manually. if I remember correctly. My case where bug C-99011 / Case 01316083.