You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling /next/<node> from an external service to notify Oxidized of config changes, the API sometimes responds with 500 Internal Server Error, particularly at startup.
Apparently this is due to the underlying next implementation only searching the list of nodes that aren't currently 'running' a poll job. If the node is currently 'running', then it will not be found, and this will raise which is not caught, not return nil/false which would be.
When calling
/next/<node>
from an external service to notify Oxidized of config changes, the API sometimes responds with 500 Internal Server Error, particularly at startup.Apparently this is due to the underlying
next
implementation only searching the list of nodes that aren't currently 'running' a poll job. If the node is currently 'running', then it will not be found, and this will raise which is not caught, not return nil/false which would be.oxidized/lib/oxidized/nodes.rb
Line 72 in 9594ae1
The text was updated successfully, but these errors were encountered: