[ https://bro-tracker.atlassian.net/browse/BIT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20918#comment-20918 ]
Aashish Sharma commented on BIT-1396: ------------------------------------- Issue Remains. I am not sure what specific crashes of bro is causing it but yes logs are not getting archived. While, I have not manually been able to reproduce this, there is quite a few of this events which happened automatically since Jun 1st: Logs got moved to ~/spool/tmp but never got archived: 36G post-terminate-2015-06-02-13-50-24-6473-crash 9.4G post-terminate-2015-06-03-15-05-04-18332-crash 11G post-terminate-2015-06-05-15-05-05-12274-crash 9.4G post-terminate-2015-06-08-15-05-45-71408-crash 11G post-terminate-2015-06-11-15-05-45-5191-crash > Logs disappearing on broctl restart > ----------------------------------- > > Key: BIT-1396 > URL: https://bro-tracker.atlassian.net/browse/BIT-1396 > Project: Bro Issue Tracker > Issue Type: Problem > Components: Bro > Affects Versions: 2.4 > Reporter: Aashish Sharma > Priority: High > Fix For: 2.4 > > > Noticed that on certain restarts of bro-2.4-beta, logs arbitrarily disappear. > Restarts happen as > - broctl check; broctl restart > - broctl check; broctl restart --clean > - broctl restart > or some variant - not precisely sure. But all log files for that duration of > restarts are missing -- This message was sent by Atlassian JIRA (v6.5-OD-05-041#65001) _______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev