[Bro-Dev] [JIRA] (BIT-1510) Crash reports when no crash happened
Daniel Thayer (JIRA)
jira at bro-tracker.atlassian.net
Thu Jan 21 14:44:00 PST 2016
[ https://bro-tracker.atlassian.net/browse/BIT-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23918#comment-23918 ]
Daniel Thayer commented on BIT-1510:
------------------------------------
I forgot to mention that a node does not enter the "crashed" state
(and therefore, there is no crash report sent) in the case when "broctl stop"
sends a SIGKILL (this happens when SIGTERM does not terminate Bro).
> 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)
More information about the bro-dev
mailing list