[Oisf-users] yaml-loader error with 2.0dev (rev 3967bd5)

Peter Manev petermanev at gmail.com
Fri Feb 7 15:31:34 UTC 2014


On Fri, Feb 7, 2014 at 4:09 PM, Stefan Sabolowitsch
<Stefan.Sabolowitsch at felten-group.com> wrote:
> Hi all,
> have here two suri Server with the same suri version 2.0dev (rev 3967bd5).
> One sure server starts without problems, but on the other i get yaml-loader error.
>
> [11082] 7/2/2014 -- 15:01:05 - (conf-yaml-loader.c:178) <Error> (ConfYamlParse) -- [ERRCODE: SC_ERR_CONF_YAML_ERROR(240)] - Failed to parse configuration fi
> le at line 727: did not find expected key
>
> Line 727 is this value:
>   iqueue-packets: 2048
>
>
> If I delete this value, see also this warning at the start:
> [11254] 7/2/2014 -- 15:01:16 - (conf-yaml-loader.c:265) <Info> (ConfYamlParse) -- Configuration node 'enabled' redefined.
> [11254] 7/2/2014 -- 15:01:16 - (conf-yaml-loader.c:265) <Info> (ConfYamlParse) -- Configuration node 'detection-ports' redefined.
>
> a "suricata -V" give this:
> This is Suricata version 2.0dev (rev 3967bd5)
>
> Why does the same binary version not the new key from the last git ?
>


Do you possibly have 2 different yaml versions - from different
versions, aka stable(or old git) on one place and a git yaml on the
other?




-- 
Regards,
Peter Manev



More information about the Oisf-users mailing list