[
https://bro-tracker.atlassian.net/browse/BIT-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20715#comment-20715
]
Aashish Sharma commented on BIT-1396:
-------------------------------------
I found the 'missing' logs in spool/tmp/<crash_dump> dir.
However, as I mentioned before, this crash_dump wasn't something outstanding
(likely a script bug) so, I never noticed it happen when doing broctl restart
etc.
So logs didn't quite disappear atleast but weren't moved to archive folder too.
I think I am suppose to send Daniel stderr.out. Doing that now.
Aashish
--
Aashish Sharma (asha...@lbl.gov)
Cyber Security,
Lawrence Berkeley National Laboratory
http://go.lbl.gov/pgp-aashish
Office: (510)-495-2680 Cell: (510)-612-7971
> 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-03-002#65000)
_______________________________________________
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
