Project

General

Profile

Actions

Bug #525

closed

Optimization #551: Replace SCLogError by a counter for memory issue and other memcap

[ERRCODE: SC_ERR_MEM_ALLOC(1)]

Added by rahim ramezanian almost 12 years ago. Updated almost 11 years ago.

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

Description

I run the suricata by the following command to read a pcap file
sudo suricata -c /etc/suricata/suricata.yaml -r /..../filename.pcap

but on the screen it shows the following errer in my terminal
[ERRCODE: SC_ERR_MEM_ALLOC(1)] - Defrag: Failed to allocate tracker.

If it is an error it should not be printed in my terminal screen as snort did not do it.

Best

Actions #1

Updated by Peter Manev almost 12 years ago

What Suricata ver are you using?

suricata --build-info

would tell you that.

Because this was fixed in the current git master.

thanks

Actions #2

Updated by rahim ramezanian almost 12 years ago

Hi
I am using v 1.3
thanks

Actions #3

Updated by rahim ramezanian almost 12 years ago

Hi
I am using v 1.3, But I do not install it from git.
thanks

Actions #4

Updated by Peter Manev almost 12 years ago

If you update to the current gitmaster - this should be fixed.

Please find some more info here :
http://planet.suricata-ids.org/
in the Article "Suricata, to 10Gbps and beyond" from the 30July, section "Defrag".

Thanks

Actions #5

Updated by Victor Julien almost 12 years ago

Is this an actual memory allocation failure or did we hit an internal memcap in the defrag engine?

Actions #6

Updated by Eric Leblond almost 12 years ago

You may need to increase the "defrag.trackers" variable when this problem occurs.

Actions #7

Updated by Eric Leblond almost 12 years ago

I mean to modify:

defrag:
  trackers: 65535
Actions #8

Updated by Victor Julien over 11 years ago

  • Status changed from New to Assigned
  • Assignee set to Eric Leblond
  • Target version set to 1.4beta3
  • Parent task set to #551
Actions #9

Updated by Eric Leblond over 11 years ago

Has defrag code rewrite indirectly triggered a "need to close" on this ticket ?

Actions #10

Updated by Victor Julien over 11 years ago

I see 2 error logs in case of PacketDefragPktSetup that we should fix.

Actions #11

Updated by Victor Julien over 11 years ago

  • Target version changed from 1.4beta3 to 1.4rc1
Actions #12

Updated by Victor Julien over 11 years ago

  • Target version changed from 1.4rc1 to 2.0rc2
Actions #13

Updated by Victor Julien almost 11 years ago

  • Status changed from Assigned to Closed
  • Target version deleted (2.0rc2)

Closing this as the larger issue is addressed by #551.

Actions

Also available in: Atom PDF