Actions
Bug #914
closedHaving a high number of pickup queues (216+) makes suricata crash
Affected Versions:
Effort:
Difficulty:
Label:
Description
If suricata has to create 216 or more queues, it errors out with «Error: Queue "picku" doesn't have a reader» after having validated the first 215.
Creating 215 queues or less succeeds.
I've attached debug logs with threads forced to 215 (success.log.gz) and to 216 (failure.log.gz)
Files
Updated by Victor Julien about 11 years ago
- Assignee set to OISF Dev
- Target version changed from 2.0beta1 to 2.0beta2
Probably related to #928.
Updated by Victor Julien about 11 years ago
- Status changed from New to Assigned
- Assignee changed from OISF Dev to Victor Julien
Updated by Victor Julien about 11 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Issue applied only to the autofp runmode.
Fixed by:
commit 6d348346230dedd9ee140c490068bf999e3a7db3
Author: Victor Julien <victor@inliniac.net>
Date: Mon Sep 9 17:19:03 2013 +0200
Runmode fixes and cleanups
Bug #939: thread name buffers are sized inconsistently
These buffers are now all fixed at 16 bytes.
Bug #914: Having a high number of pickup queues (216+) makes suricata crash
Fixed so that we can now have 256 pickup queues, which is the current built-in
maximum. Improved the error reporting.
Bug #928: Max number of threads
Error reporting improved. Issue was the same as #914.
Updated by Victor Julien about 11 years ago
Issue #947 tracks resolving the 256 queues limitation.
Actions