Possible Cause Found for Agent Nodes Not Updating Polling Engine Correctly
I recently opened a support case regarding an issue where changing an agent-managed node's polling engine from the Orion Web Console would update the node properties in Orion, but the agent itself would continue pointing to the original polling engine. This mismatch caused the node to appear down.
My workaround had been to manually log into the server and reconfigure the agent to point to the correct polling engine.
After additional testing, I believe the issue may be related to outdated agent versions.
What I observed
- Nodes migrated from an older polling engine would update in Orion, but the agent configuration would not.
- As a result:
- Node Properties showed the new polling engine.
- Agent Settings still showed the old polling engine.
- The node would then lose communication and appear down.
What appears to fix it
- Manually reconfigure/migrate the agent from the old polling engine.
- Allow the agent to update to the newer version.
- After the agent update, polling engine changes initiated from the Orion Web Console work normally.
I tested this by re-migrating a node that had already received the agent update, and the polling engine change completed successfully from the portal.
Environment
- Orion Platform Version: 2026.2.1
- Outdated Agent Version: 2024.2.0.1965
- Old Polling Engine Version: 2026.1.0.2558
- New Polling Engine Version: 2026.2.1.4103
Additional Notes
- Observed on both Windows and Linux agents.
- Confirmed not to be a firewall, network, or port connectivity issue.
Reference to the original discussion: Changing Polling Engine for Agent Node
