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
I was running a deamon bash script capture zeek stats, it runs zeekctl netstats every 5 seconds.
And there's another scripts that runs zeekctl deploy if it finds zeek crushed.
But I met a situation that if zeek crush at a specific time, that zeekctl netstats command will suspend and never ends, which cause zeekctl deploy waits for lock owned by zeekctl netstats and thus will not restart crushed zeek.
Envronment: Ubuntu 20.04 on virtual box ( 6cores i7-12700, 8G RAM)
Version: zeek 6.0.1
Except node.cfg, nothing is modified.
I tried to reproduce this problem, and this is the script that works to trigger this problem.
By print more logs, I guess that zeekctl netstats gets stuck at /ZeekControl/events.py line 67 endpoint.peer(host, node.getPort(), 1)
The text was updated successfully, but these errors were encountered:
0xxon
changed the title
zeekctl netstats gets stuck sometimes if zeek worker crushed
zeekctl netstats gets stuck sometimes if zeek worker crashed
Dec 20, 2023
I was running a deamon bash script capture zeek stats, it runs
zeekctl netstats
every 5 seconds.And there's another scripts that runs
zeekctl deploy
if it finds zeek crushed.But I met a situation that if zeek crush at a specific time, that
zeekctl netstats
command will suspend and never ends, which causezeekctl deploy
waits for lock owned byzeekctl netstats
and thus will not restart crushed zeek.Envronment: Ubuntu 20.04 on virtual box ( 6cores i7-12700, 8G RAM)
Version: zeek 6.0.1
Except node.cfg, nothing is modified.
I tried to reproduce this problem, and this is the script that works to trigger this problem.
By print more logs, I guess that
zeekctl netstats
gets stuck at /ZeekControl/events.py line 67endpoint.peer(host, node.getPort(), 1)
Thanks for helping me solving this problem.
The text was updated successfully, but these errors were encountered: