# Bro always crashes

**URL:** <https://community.zeek.org/t/bro-always-crashes/53>\
**Category:** Zeek\
**Created:** [May 7, 1999, 8:33am UTC](https://community.zeek.org/t/bro-always-crashes/53 "1999-05-07T08:33:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vern](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/vern/32/630_2.png) [@Vern](https://community.zeek.org/u/Vern)\
**Post date:** [May 7, 1999, 8:33am UTC](https://community.zeek.org/t/bro-always-crashes/53/1 "1999-05-07T08:33:42Z")

</div>

> without seeing a SYN-ack from B.80 in between. This then leads to  
> Bro holding state for the half-established connection after it sees  
> A.1234 -\> B.80.

I should add that I diagnosed this because the connection summaries  
Bro generated on stdout looked like:

925897359.600000 0.26 http ? 1775 199.108.25.84 130.104.28.234 SHR X

"SHR" indicates a half-stablished connection that was closed by the  
responder. (It's the responder in this case because the only packets  
Bro saw were the SYN-ack [rather than the SYN] and the FIN.)

This is a highly unusual state for normal traffic, i.e. when Bro sees  
both sides of the connections.

&nbsp;&nbsp;&nbsp;&nbsp;Vern

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:36pm UTC](https://community.zeek.org/t/bro-always-crashes/53/2 "2022-05-06T15:36:06Z")

</div>


