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
Since temboard-agent 9.0.1 i have a few issues when trying to stop & start quickly (eg using some automated tests in CI) the agent, here are a few steps to reproduce what i observe on my side (outside of my tests suite / CI):
Install temboard-agent 9.0.1
Run temboard-agent in backround: temboard-agent --config /tmp/temboard-agent-17-test.conf &
Get the PID of the temboard-agent (from previous step)
kill the first temboard-agent and launch (quickly) a new one temboard-agent with: kill <pid first agent> && temboard-agent --config /tmp/temboard-agent-17-test.conf
After the last operation, we can observe this error:
INFO: app: Starting temboard-agent. version=9.0.1INFO: app: Using config file /tmp/temboard-agent-17-test.conf.WARNING: agent: Hostname dontbecurious is not a FQDN.INFO: serve: Resetting monitoring data.CRITICAL: app: Failed to start HTTPS server: [Errno 98] Address already in use.
When I run top, pstree or any other tool to watch the processes, i can see a few temboard processes (and the especially the web worker) taking a few seconds before dying. So i guess killing all the process take some time the HTTP(s) port is kept open / busy by a nearly dead process.
The text was updated successfully, but these errors were encountered:
Hello,
Since temboard-agent 9.0.1 i have a few issues when trying to stop & start quickly (eg using some automated tests in CI) the agent, here are a few steps to reproduce what i observe on my side (outside of my tests suite / CI):
temboard-agent --config /tmp/temboard-agent-17-test.conf &
kill <pid first agent> && temboard-agent --config /tmp/temboard-agent-17-test.conf
When I run
top
,pstree
or any other tool to watch the processes, i can see a few temboard processes (and the especially the web worker) taking a few seconds before dying. So i guess killing all the process take some time the HTTP(s) port is kept open / busy by a nearly dead process.The text was updated successfully, but these errors were encountered: