Project

General

Profile

Actions

Bug #125

closed

Improperly spaced config file causes the engine to hang during init.

Added by Will Metcalf almost 14 years ago. Updated almost 14 years ago.

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

Description

Improper spacing in the attached config for the alert-debug stuff causes the engine to hang during init. Additionally Would it be possible to add a line number where the parsing error occurred?

sh c ulimit -c unlimited; /testresults/2010-03-26-11-07-39/CentOS-5.3-32-bit/oisf/src/suricata -r /pcaps/tests/suricata40.pcap -s /testscripts/current-all-blah.rules -l /testresults/2010-03-26-11-07-39/CentOS-5.3-32-bit/oisf/src/ -c /testscripts/suricata35.yaml
unlimited
Warning: Invalid global_log_level assigned by user. Falling back on the default_log_level "Info"
Warning: Invalid global_log_format supplied by user or format length exceeded limit of "128" characters. Falling back on default log_format "[%i] %t - (%f:%l) <%d> (%n) -
"
Warning: Output_interface not supplied by user. Falling back on default_output_interface "Console"
[3685] 26/3/2010 -- 14:27:05 - (suricata.c:582) <Info> (main) -- This is Suricata version 0.8.1
[3685] 26/3/2010 -- 14:27:05 - (util-cpu.c:150) <Info> (UtilCpuPrintSummary) -- CPUs Summary:
[3685] 26/3/2010 -- 14:27:05 - (util-cpu.c:152) <Info> (UtilCpuPrintSummary) -- CPUs online: 2
[3685] 26/3/2010 -- 14:27:05 - (util-cpu.c:154) <Info> (UtilCpuPrintSummary) -- CPUs configured 2
Failed to parse configuration file: did not find expected key


Files

suricata35.yaml (3.25 KB) suricata35.yaml broken config Will Metcalf, 03/26/2010 01:53 PM
0001-Fix-bug-125.patch (2.3 KB) 0001-Fix-bug-125.patch Jason Ish, 03/26/2010 03:35 PM
Actions #1

Updated by Jason Ish almost 14 years ago

  • Status changed from New to Assigned
Actions #2

Updated by Jason Ish almost 14 years ago

This patch should address this bug.

I'd like to display more context about the error, but our hands may be tied a little as we are using a somewhat validating file format, where an error a few lines back could actually be the cause of the error, and we don't actually sanity check the contents of the file until its loaded completely - one of the drawbacks of a config that will load anything (think unknown modules) rather than verify everything it reads in for contextual validity.

Actions #3

Updated by Victor Julien almost 14 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

Applied, thanks Jason.

Actions

Also available in: Atom PDF