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

Robin Sommer commented on BIT-1356:
-----------------------------------

Can somebody see if  0620bc97 helps?

> Bro process sticks around after broctl stop
> -------------------------------------------
>
>                 Key: BIT-1356
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1356
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: BroControl
>    Affects Versions: git/master
>            Reporter: Johanna Amann
>            Assignee: Daniel Thayer
>             Fix For: 2.4
>
>
> It seems that after running a "broctl stop" not all bro processes are killed 
> immediately. On our cluster, one of the processes keeps running; I seems like 
> it eventually terminates after all log-compression is done. Is that on 
> purpose or is that a bug?
> Ps output  (on the node running the manager, bro process in first line, 
> including the running compression jobs for completeness):
> {code}
> $ ps -ax | grep bro
> 23353  -  IN       20:06.96 /xa/bro/master/bin/bro -U .status -p broctl -p 
> broctl-live -p local -p manager local.bro broctl base/frameworks/cluster 
> local-manager.bro broctl/auto
> 24979  -  I         0:00.01 bash 
> /xa/bro/master/share/broctl/scripts/archive-log http.2015-03-25-14-40-30.log 
> http 15-03-25_14.40.30 15-03-25_16.29.29 1 ascii
> 25047  -  I         0:00.01 bash 
> /xa/bro/master/share/broctl/scripts/archive-log conn.2015-03-25-14-40-30.log 
> conn 15-03-25_14.40.30 15-03-25_16.29.29 1 ascii
> 25841  -  S         0:00.59 bash 
> /xa/bro/master/share/broctl/scripts/post-terminate 
> /xa/bro/master/spool/manager
> 29204  0  D+        0:00.00 grep bro
> {code}



--
This message was sent by Atlassian JIRA
(v6.4-OD-16-006#64014)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Reply via email to