Just got this when updating manually with suricata-update. Running with –no-test ran fine..rules worked fine..
29/9/2025 – 08:13:59 - – StateQueue behaving weirdly. Fatal Error. Exiting. Please file a bug report on this
29/9/2025 – 08:13:59 - – Suricata test failed, aborting.
29/9/2025 – 08:13:59 - – Restoring previous rules.
Worked fine without –no-test on Friday.
vjulien
(Victor Julien)
September 29, 2025, 2:39pm
2
What version of Suricata?
8.0.0 and 8.0.1 ….20 character rule is kinda silly.
vjulien
(Victor Julien)
September 29, 2025, 3:06pm
4
Are you able to (privately) share your ruleset? It seems to hit some kind of internal error condition.
Can I try running in….like…super verbose mode first? I can gather up the rule in the mean time.
novaksam
(Sam Novak)
September 29, 2025, 6:52pm
6
I’m having the same issue; started sometime over the weekend, I’m using the ET PRO ruleset, with 7.0.12 version of suricata (via security onion).
I was trying to get a stack trace, but gdb wouldn’t let me set a breakpoint on util-mpm-ac-queue.h:86
novaksam
(Sam Novak)
September 29, 2025, 7:12pm
7
I just pruned all of the updated and new rules from late last week “sed -i’’ ‘s/.*2025_09_26.*//’ ./all.rules” and suricata was able to start up. because some of those rules might be in ETPRO it might be difficult to troubleshoot.