Project

General

Profile

Actions
Copy link

Bug #6750

closed

dpdk: examine the functionality of multiple parallel-running DPDK Suricata processes

Added by Lukas Sismis 10 months ago. Updated 9 months ago.

Status:
Rejected
Priority:
Low
Assignee:
Lukas Sismis
Target version:
8.0.0-beta1
Affected Versions:
7.0.2
Effort:
Difficulty:
Label:

Description

There is certain suspicion that if two (and more) independent DPDK Suricata processes with different file prefixes run in parallel, they somehow can affect each other and prevent from shutting down.
There were multiple Suricata processes to make sure Suricata workers ran on the correct NUMA nodes with their respective NICs (placed on different NUMA nodes).

Error message:

Error: suricata: stacktrace:sig 6:gsignal+0x0000010f;abort+0x00000127;__assert_fail_base.cold.0+0x0000000f;__assert_fail+0x00000046;TmThreadClearThreadsFamily+0x00000217;PostRunDeinit+0x000000eb;SuricataMain+0x00002bd2;__libc_start_main+0x000000e5;_start+0x0000002e [SignalHandlerUnexpected:suricata.c:321]

Actions
Copy link
 #1

Updated by Lukas Sismis 9 months ago

  • Status changed from Assigned to Rejected

Evaluated with multiple DPDK virtual devices (net_null) in the config:

dpdk:
  eal-params:
    proc-type: primary
    file-prefix: second-proc
      # no-huge:
    vdev: ["net_null0", "net_null1", "net_null2", "net_null3"]

No segfault observed.

Actions
Copy link

Also available in: Atom PDF