Core Update 162: Suricata emits logspam galore

Hi,

first, thank you very much for testing Core Update 162. :slight_smile:

Indeed, I get a ton of these log messages as well since I upgraded my testing machine:

12/05/2021-08:16:33.852710  [**] [1:2210059:1] SURICATA STREAM pkt seen on wrong thread [**] [Classification: (null)] [Priority: 3] {TCP} x:x -> x:x

They are no cause for worries, but are quite annoying. I will raise a ticket so we can silence this (or deal with it’s root cause) before releasing Core Update 162.

EDIT: Done, please refer to bug #12738.

EDIT #2: On a closer look, Suricata does not seem to load any rules at all after the upgrade. Not good, raised bug #12739 for this.

Thanks, and best regards,
Peter Müller

1 Like