Project

General

Profile

Actions

Support #5033

closed

"Failed to attach filter: Cannot allocate memory" being thrown on some systems but not others that are seemingly identical.

Added by Zane B-H about 1 year ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Affected Versions:
Label:

Description

Running 6.0.2 and am running into this issue on a few systems. They are seemingly identical, but for some reason the BPF errors on one, but not another.

1/2/2022 -- 17:29:14 - <Perf> - AF_PACKET RX Ring params: block_size=32768 block_nr=103 frame_size=1600 frame_nr=2060
1/2/2022 -- 17:29:14 - <Info> - Using BPF '                                                                                                                                                      not ( host 141.2
06.161.42 and port 514 ) and not ( host 141.206.161.42 and port 1514 ) and not ( host 141.206.161.42 and port 2514 ) and not ( host 141.206.161.42 and port 3514 ) and not ( host 141.206.161.42 and port 4514 )
and not ( host 141.206.161.42 and port 5514 ) and not ( host 141.206.161.42 and port 6514 ) and not ( host 141.206.161.42 and port 7514 ) and not ( host 141.206.161.42 and port 8514 ) and not ( host 141.206.16
1.42 and port 9514 ) and not ( host 2.2.2.1 and port 514 ) and not ( host 2.2.2.1 and port 1514 ) and not ( host 2.2.2.1 and port 2514 ) and not ( host 2.2.2.1 and port 3514 ) and not ( host 2.2.2.1 and port 4
514 ) and not ( host 2.2.2.1 and port 5514 ) and not ( host 2.2.2.1 and port 6514 ) and not ( host 2.2.2.1 and port 7514 ) and not ( host 2.2.2.1 and port 8514 ) and not ( host 2.2.2.1 and port 9514 ) and not
( host 10.128.134.100 and port 514 ) and not ( host 10.128.134.100 and port 1514 ) and not ( host 10.128.134.100 and port 2514 ) and not ( host 10.128.134.100 and port 3514 ) and not ( host 10.128.134.100 and
port 4514 ) and not ( host 10.128.134.100 and port 5514 ) and not ( host 10.128.134.100 and port 6514 ) and not ( host 10.128.134.100 and port 7514 ) and not ( host 10.128.134.100 and port 8514 ) and not ( hos
t 10.128.134.100 and port 9514 ) and                                   not port 3260' on iface 'e1'
1/2/2022 -- 17:29:14 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Failed to attach filter: Cannot allocate memory
1/2/2022 -- 17:29:14 - <Error> - [ERRCODE: SC_ERR_AFP_CREATE(190)] - Couldn't init AF_PACKET socket, fatal error

And on a working system...

28/1/2022 -- 19:41:43 - <Perf> - AF_PACKET RX Ring params: block_size=32768 block_nr=103 frame_size=1600 frame_nr=2060
28/1/2022 -- 19:41:43 - <Info> - Using BPF '                                                                                                                                                      not ( host 141.206.161.42 and port 514 ) and not ( host 141.206.161.42 and port 1514 ) and not ( host 141.206.161.42 and port 2514 ) and not ( host 141.206.161.42 and port 3514 ) and not ( host 141.206.161.42 and port 4514 ) and not ( host 141.206.161.42 and port 5514 ) and not ( host 141.206.161.42 and port 6514 ) and not ( host 141.206.161.42 and port 7514 ) and not ( host 141.206.161.42 and port 8514 ) and not ( host 141.206.161.42 and port 9514 ) and not ( host 2.2.2.1 and port 514 ) and not ( host 2.2.2.1 and port 1514 ) and not ( host 2.2.2.1 and port 2514 ) and not ( host 2.2.2.1 and port 3514 ) and not ( host 2.2.2.1 and port 4514 ) and not ( host 2.2.2.1 and port 5514 ) and not ( host 2.2.2.1 and port 6514 ) and not ( host 2.2.2.1 and port 7514 ) and not ( host 2.2.2.1 and port 8514 ) and not ( host 2.2.2.1 and port 9514 ) and not ( host 10.128.134.100 and port 514 ) and not ( host 10.128.134.100 and port 1514 ) and not ( host 10.128.134.100 and port 2514 ) and not ( host 10.128.134.100 and port 3514 ) and not ( host 10.128.134.100 and port 4514 ) and not ( host 10.128.134.100 and port 5514 ) and not ( host 10.128.134.100 and port 6514 ) and not ( host 10.128.134.100 and port 7514 ) and not ( host 10.128.134.100 and port 8514 ) and not ( host 10.128.134.100 and port 9514 ) and                                   not port 3260' on iface 'e1'

For the ruleset...

not ( host 141.206.161.42 and port 514 ) and
not ( host 141.206.161.42 and port 1514 ) and
not ( host 141.206.161.42 and port 2514 ) and
not ( host 141.206.161.42 and port 3514 ) and
not ( host 141.206.161.42 and port 4514 ) and
not ( host 141.206.161.42 and port 5514 ) and
not ( host 141.206.161.42 and port 6514 ) and
not ( host 141.206.161.42 and port 7514 ) and
not ( host 141.206.161.42 and port 8514 ) and
not ( host 141.206.161.42 and port 9514 ) and
not ( host 2.2.2.1 and port 514 ) and
not ( host 2.2.2.1 and port 1514 ) and
not ( host 2.2.2.1 and port 2514 ) and
not ( host 2.2.2.1 and port 3514 ) and
not ( host 2.2.2.1 and port 4514 ) and
not ( host 2.2.2.1 and port 5514 ) and
not ( host 2.2.2.1 and port 6514 ) and
not ( host 2.2.2.1 and port 7514 ) and
not ( host 2.2.2.1 and port 8514 ) and
not ( host 2.2.2.1 and port 9514 ) and
not ( host 10.128.134.100 and port 514 ) and
not ( host 10.128.134.100 and port 1514 ) and
not ( host 10.128.134.100 and port 2514 ) and
not ( host 10.128.134.100 and port 3514 ) and
not ( host 10.128.134.100 and port 4514 ) and
not ( host 10.128.134.100 and port 5514 ) and
not ( host 10.128.134.100 and port 6514 ) and
not ( host 10.128.134.100 and port 7514 ) and
not ( host 10.128.134.100 and port 8514 ) and
not ( host 10.128.134.100 and port 9514 ) and
not port 3260
Actions #1

Updated by Peter Manev about 1 year ago

Are both systems the same ? (kernel/OS etc ?)

Actions #2

Updated by Zane B-H about 1 year ago

Peter Manev wrote in #note-1:

Are both systems the same ? (kernel/OS etc ?)

So been poking at this a bit more, it appears that our systems running 4.19.67-2+deb10u2 appear to specifically be bumping into this in some cases, just that those appear to be running slightly smaller rule sets in general than our ones running 4.9.30-2+deb9u5. Though we had some larger ones running on both, but it is looking like not.

Going to poke at that angle some more than I get a chance tomorrow.

Actions #3

Updated by Zane B-H about 1 year ago

Peter Manev wrote in #note-1:

Are both systems the same ? (kernel/OS etc ?)

More testing and nearly certain it is a bug in 4.19.67-2+deb10u2. Throwing large BFPs at it for other things besides suricata results in the same.

Actions #4

Updated by Victor Julien 12 months ago

  • Priority changed from High to Normal

So it seems to not be a Suricata issue?

Actions #5

Updated by Victor Julien 12 months ago

  • Tracker changed from Bug to Support
  • Status changed from New to Closed
Actions

Also available in: Atom PDF