[
https://bro-tracker.atlassian.net/browse/BIT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seth Hall updated BIT-266:
--------------------------
Resolution: Fixed
Status: Closed (was: Open)
Without more debugging information or activity on this ticket, I'm just going
to close it.
> broctl cron hangs with dead hosts
> ---------------------------------
>
> Key: BIT-266
> URL: https://bro-tracker.atlassian.net/browse/BIT-266
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: BroControl
> Affects Versions: git/master
> Reporter: solomon
> Assignee: Daniel Thayer
> Fix For: 2.2
>
>
> If a bro node has become completely inaccessible (dead or otherwise offline),
> the broctl 'cron' task will hang for far too long while attempting to restart
> bro on that host. When 'broctl cron' is run from the system crontab, this
> negatively impacts any other use of broctl and prevents almost all
> interactive use of broctl, which repeatedly times out with 'cannot get lock'
> error message.
> One is forced to either kill all running python processes on the master
> (thereby killing the blocking 'broctl cron' task), or to run broctl
> non-interactively (such as running "broctl top" from the command line)
> over-and-over again until the process successfully gets the lock.
> broctl should timeout more quickly with hosts that are completely offline.
--
This message was sent by Atlassian JIRA
(v6.2-OD-01#6204)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
