[
https://bro-tracker.atlassian.net/browse/BIT-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25400#comment-25400
]
Daniel Thayer commented on BIT-1510:
------------------------------------
Branch "topic/dnthayer/ticket1510" in the broctl repo changes
the behavior of broctl when a node crashes during shutdown.
In such a case, the node status after the "stop" command finishes
will be "stopped" instead of "crashed". Also, a crash report is no longer
generated in this case (however, the user will still be able to see an
output message generated by the "stop" command and the user
can still access the archived stdout/stderr.log files in case those
are useful).
> 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.2.0-OD-05-023#72002)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
