[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oisf-users
Subject:    Re: [Oisf-users] 2.0.5 Memory Leak ?
From:       "Jay M." <jskier () gmail ! com>
Date:       2015-01-16 21:29:17
Message-ID: CACEdYO31cTaLp7p4WT3LkEspQ3wcRO=C6T_dB2-4qjvRgztBhw () mail ! gmail ! com
[Download RAW message or body]

It is my understanding that both versions are checked for memory leaks
and there aren't any.

Any additional insight on the rules (quantity, set) you are using?
Hardware, OS, and kernel?

Also, as Andreas pointed out, I put in an issue for the reload call
memory issue (apparently it's fragmentation, not a leak). My solution
is to restart suricata at off-peak hours a couple times a day for the
time being, instead of reloading.

--
Jay
jskier@gmail.com


On Fri, Jan 16, 2015 at 1:46 PM, Phil Daws <uxbod@splatnix.net> wrote:
> Hello:
> 
> any known issues with 2.0.5 and memory leaks ? have had to restart Suricata a few \
> times as swap was consumed and it stopped responding; am running inline mode.  Once \
> it was restarted all was fine. 
> Thanks, Phil
> (null)
> (null)
> _______________________________________________
> Suricata IDS Users mailing list: oisf-users@openinfosecfoundation.org
> Site: http://suricata-ids.org | Support: http://suricata-ids.org/support/
> List: https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users
> Training now available: http://suricata-ids.org/training/
_______________________________________________
Suricata IDS Users mailing list: oisf-users@openinfosecfoundation.org
Site: http://suricata-ids.org | Support: http://suricata-ids.org/support/
List: https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users
Training now available: http://suricata-ids.org/training/


[prev in list] [next in list] [prev in thread] [next in thread]