Project

General

Profile

Actions
Copy link

Bug #924

closed

missing space between variable and value in suricata.yaml

Added by Peter Manev about 11 years ago. Updated over 1 year ago.

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

Description

This is Suricata version 2.0beta1 RELEASE and latest git

If we have no space between the variable and the value:

flow:
  memcap:32000000000000000000mb
  hash-size: 65536
  prealloc: 10000
  emergency-recovery: 30

Notice the missing space at the memcap value.

We get an ERR msg, like this:


- <Info> - CPUs/cores online: 2
Failed to parse configuration file at line 515: mapping values are not allowed in this context

Which does not give a hint that the ERR is because of a missing space.

Actions
Copy link
 #1

Updated by Victor Julien about 11 years ago

  • Target version set to TBD
Actions
Copy link
 #2

Updated by Andreas Herz about 8 years ago

  • Assignee set to OISF Dev
Actions
Copy link
 #3

Updated by Andreas Herz over 5 years ago

This is not an error message from us but rather from the external lib. Should we catch this beforehand?

Actions
Copy link
 #4

Updated by Philippe Antoine over 1 year ago

  • Status changed from New to Closed

Now we get [259] 21/7/2023 -- 11:04:10 - (conf-yaml-loader.c:196) <Error> (ConfYamlParse) -- [ERRCODE: SC_ERR_CONF_YAML_ERROR(242)] - Failed to parse configuration file at line 925: could not find expected ':'

We have the line number in the config to fix.
this is how libyaml works...
https://github.com/ansible/ansible-lint/issues/2226

Actions
Copy link

Also available in: Atom PDF