Justin Azoff created BIT-1228:
---------------------------------
Summary: 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
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
(v6.4-OD-02-003#64000)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
