[
https://bro-tracker.atlassian.net/browse/BIT-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23919#comment-23919
]
Seth Hall commented on BIT-1510:
--------------------------------
Yeah, I don't think we should be sending crash reports in those cases. Just
because Bro wasn't shutting down quickly enough we shouldn't be indicating to
users that it crashed. I've seen a number of cases where Bro left to it's own
devices will take an extended period to shut down due to running scripts as it
flushes the connection table and other internal processing. Telling people
that it crashed is definitely wrong and those reports don't have anything that
would be useful to anyone.
> Crash reports when no crash happened
> ------------------------------------
>
> Key: BIT-1510
> URL: https://bro-tracker.atlassian.net/browse/BIT-1510
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: BroControl
> Affects Versions: git/master
> Reporter: Seth Hall
> Fix For: 2.5
>
>
> We need to make broctl stop sending crash reports when Bro was shutdown by a
> signal. It's confusing for users because they will get these emails
> sporadically when restarting Bro.
> The crash report typically has the following text and no backtrace:
> ==== stderr.log
> KILLED
> received termination signal
--
This message was sent by Atlassian JIRA
(v7.1.0-OD-05-006#71001)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
