[Bro-Dev] [JIRA] (BIT-1228) broctl needs to keep track of desired state

Daniel Thayer (JIRA) jira at bro-tracker.atlassian.net
Tue Mar 17 07:50:01 PDT 2015

     [ https://bro-tracker.atlassian.net/browse/BIT-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Thayer updated BIT-1228:
    Resolution: Fixed
        Status: Closed  (was: Open)

This functionality is now in git master.

> broctl needs to keep track of desired state
> -------------------------------------------
>                 Key: BIT-1228
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1228
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: BroControl
>            Reporter: Justin Azoff
>            Assignee: Justin Azoff
>            Priority: Low
>             Fix For: 2.4
> On a multi-node cluster the following sequence of events can happen:
> * A cluster node (node-2) has a power problem and is shut down
> * broctl stop is ran on the manager
> * broctl then fails to stop bro on node-2
> * node-2 reboots
> * broctl cron restarts bro on node-2 because the last known state is up
> The problem can happen in reverse as well, where broctl will not restart bro on a node that was down.
> The problem arises because broctl stores the actual state of the nodes, but not the desired state.  commands like stop and start need to set the desired start first, and then attempt to sync reality with that state information.  broctl cron then just needs to attempt the similar sync.

This message was sent by Atlassian JIRA

More information about the bro-dev mailing list