[Oisf-users] Suricata problem with detect-cpu-set upper bound.

[Eric Leblond]

Hello,

Le jeudi 21 février 2013 à 18:08 +0000, Duarte Silva a écrit :
> Hi all,
> 
> 
> I got this on Suricata logs:
> 
> 21/2/2013 -- 18:03:00 - <Error> - [ERRCODE:
> SC_ERR_INVALID_ARGUMENT(13)] - detect-cpu-set: upper bound (2) of cpu
> set is too high, only 2 cpu(s)
> 
> 
> The affinity settings for the detect-cpu-set are as follows:
> 
> 
>     - detect-cpu-set:
>         cpu: [ "all" ]
>         mode: "exclusive" # run detect threads in these cpus
>         # Use explicitely 3 threads and don't compute number by using
>         # detect-thread-ratio variable:
>         # threads: 3
>         prio:
>           low: [ 0 ]
>           medium: [ "1-2" ]
>           high: [ 3 ]

This line here indicate that the cpu 3 is used. Please use number below
1 in these categories as you have ony 2 CPUs.

BR,

>           default: "high"
>           #default: "medium"
> 
> 
> Note that I'm using one dual core CPU.
> 
> 
> Best regards,
> 
> Duarte Silva
> 
> _______________________________________________
> Suricata IDS Users mailing list: oisf-users at openinfosecfoundation.org
> Site: http://suricata-ids.org | Support: http://suricata-ids.org/support/
> List: https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users
> OISF: http://www.openinfosecfoundation.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20130221/fc995a29/attachment.sig>