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
Describe the bug
When an agent fails to complete its initial setup (i.e., it dies during init), VOLTTRON automatically restarts the agent every few seconds ad infinitum. vctl status shows the agent as being dead, with status 1. This is a problem, because having started a broken agent,
there is no obvious way to stop it from infinitely relaunching agent, since it is not running, short of restarting the platform.
To Reproduce
Steps to reproduce the behavior:
Put a code error into the __init__() of an agent, e.g., "None.get(4)".
Start the agent.
Watch a log tail as the agent repeatedly dies and restarts.
Expected behavior
Agents like the Forward Historian, which may fail to start if it is not able to reach its target, require the restarting functionality, but most agents do not. There should be a limited number of retries, which is configurable, perhaps as an argument to Agent, which can be used by the Forwarder (or manually by developers while debugging the init of a new agent) to specify a larger (or infinite) number of restarts. Other agents should use a default number which is small (say 5 or less). Each time it dies, the log should get a message saying, "Agent died, will restart x more times. Next restart in y seconds". Once x falls to 0, the agent stops restarting.
The text was updated successfully, but these errors were encountered:
Describe the bug
When an agent fails to complete its initial setup (i.e., it dies during init), VOLTTRON automatically restarts the agent every few seconds ad infinitum. vctl status shows the agent as being dead, with status 1. This is a problem, because having started a broken agent,
there is no obvious way to stop it from infinitely relaunching agent, since it is not running, short of restarting the platform.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Agents like the Forward Historian, which may fail to start if it is not able to reach its target, require the restarting functionality, but most agents do not. There should be a limited number of retries, which is configurable, perhaps as an argument to Agent, which can be used by the Forwarder (or manually by developers while debugging the init of a new agent) to specify a larger (or infinite) number of restarts. Other agents should use a default number which is small (say 5 or less). Each time it dies, the log should get a message saying, "Agent died, will restart x more times. Next restart in y seconds". Once x falls to 0, the agent stops restarting.
The text was updated successfully, but these errors were encountered: