[
https://bro-tracker.atlassian.net/browse/BIT-1353?page=com.atlassian.jira.p…
]
Daniel Thayer commented on BIT-1353:
------------------------------------
I'm not seeing a problem. As a test, I simulated a slow node by adding a
"sleep"
command to one of the scripts that broctl runs on the remote host.
If the sleep is long enough to exceed the timeout, then I see "???" in the
status
output (in the "Running", "Peers", and "Started" columns).
Otherwise, broctl status simply gathers information reported by Bro.
BroCtl status/top take excessive amount of time
-----------------------------------------------
Key: BIT-1353
URL:
https://bro-tracker.atlassian.net/browse/BIT-1353
Project: Bro Issue Tracker
Issue Type: Problem
Components: BroControl
Affects Versions: git/master
Reporter: Johanna Amann
Assignee: Daniel Thayer
Fix For: 2.4
After running a large bro cluster for a few days on a FreeBSD system (FreeBSD 10.1, 28
physical nodes, 81 worker processes), broctl actions that interact with all nodes seem to
take excessive amounts of time (>2 minutes for a broctl status). This was not the case
right after starting up the cluster.
If there is any way I can help with more information, please let me know what to do.
--
This message was sent by Atlassian JIRA
(v6.4-OD-16-005#64014)