Project

General

Profile

Actions

Bug #1861

closed

Suricata with multitenancy does not start in 3.1/3.1.1

Added by Peter Manev almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

It seems the issue appeared in 3.1 and continues to 3.1.1(where as in 3.0.1 it was fine).

A simple Suricata test start with 2 tenant.yaml config files in 3.0.1 works fine.
With the very same configs - Suricata 3.1 and 3.1.1 the initial start seems to stall here:

13/8/2016 -- 02:51:29 - <Info> - using 2 detect loader threads
13/8/2016 -- 02:51:29 - <Info> - multi-tenant selector type vlan
13/8/2016 -- 02:51:29 - <Info> - multi-detect is enabled (multi tenancy). Selector: vlan
13/8/2016 -- 02:51:29 - <Info> - vlan 1000 connected to tenant-id 1
13/8/2016 -- 02:51:29 - <Info> - vlan 2000 connected to tenant-id 2
13/8/2016 -- 02:51:29 - <Info> - tenant id: 1, /etc/suricata/tenant-1.yaml
13/8/2016 -- 02:51:29 - <Info> - tenant id: 2, /etc/suricata/tenant-2.yaml
Actions

Also available in: Atom PDF