Project

General

Profile

Actions

Support #2618

closed

suricata 4.0.5 + pfring 7.2.0 crashes

Added by Rado Ce over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Affected Versions:
Label:

Description

Hi!

I'm running suricata 4.0.5 (4.0.4 was also affected) with pf_ring 7.2.0 on CentOS 1804, kernel 3.10.0-862.el7.x86_64 like this:

suricata  -c /etc/suricata/suricata.yaml --pfring-int=zc:99@0 --pfring-int=zc:99@1 \
--pfring-int=zc:99@2 --pfring-int=zc:99@3 --pfring-int=zc:99@4 --pfring-int=zc:99@5 \
--pidfile /run/suricata.pid --runmode=workers

from time to time it just exits, so I've rebuilt it with debugging enabled, before crash there's this log entry:

12/9/2018 -- 14:07:59 - <Debug> - creating thread "US"...
12/9/2018 -- 14:07:59 - <Debug> - US starting
12/9/2018 -- 14:07:59 - <Debug> - error with the counter ids
12/9/2018 -- 14:07:59 - <Debug> - stats_ctx->sts 0x7fa1580008e0
12/9/2018 -- 14:07:59 - <Debug> - US started...
12/9/2018 -- 14:07:59 - <Debug> - error with the counter ids
12/9/2018 -- 14:07:59 - <Debug> - stats_ctx->sts 0x7fa158000910
12/9/2018 -- 14:07:59 - <Error> - [ERRCODE: SC_ERR_THREAD_INIT(49)] - thread "W#01-zc:99@0" failed to initialize: flags 0145
12/9/2018 -- 14:07:59 - <Error> - [ERRCODE: SC_ERR_INITIALIZATION(45)] - Engine initialization failed, aborting...

After this pfring's egress queues are locked, so I have to restart pfring and then suricata. There are other applications using other pfring queues in that time and they are working after this occurs.

This happens sometimes every day, sometimes every two or three days, no rule there. Also regardless of traffic.

Build info log attached.
Thanks in advance
Rado


Files

suricata_build_info.txt (3.2 KB) suricata_build_info.txt Rado Ce, 09/12/2018 03:16 PM
suricata04.log (7.57 KB) suricata04.log Rado Ce, 09/13/2018 03:43 PM
Actions

Also available in: Atom PDF