[Bro-Dev] [JIRA] (BIT-1353) BroCtl status/top take excessive amount of time

Johanna Amann (JIRA) jira at bro-tracker.atlassian.net
Thu Mar 26 07:47:00 PDT 2015

    [ https://bro-tracker.atlassian.net/browse/BIT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20118#comment-20118 ] 

Johanna Amann commented on BIT-1353:

And even more detail - the cause of this was hardware problems on two nodes. The bro instances of these nodes were still kind-of-running, but I don't think they were communicating with master anymore and they were unnkillable (even with kill -9); probably hanging while waiting for disk-io (harddrive problems). Since you still could ssh into the nodes, and they worked normally unless you tried to do certain file system accesses, broctl apparently listed them as online, without giving any indication of problems with the nodes, besides the fact that "status" takes a long time.

> 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
>             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

More information about the bro-dev mailing list