[Oisf-users] segfault in libc

[Cooper F. Nelson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Are you sure you are not having an out-of-memory segfault or
experiencing a side effect of the the OOM killer?

> http://stackoverflow.com/questions/6132333/how-to-detect-out-of-memory-segfaults

I ran into an issue on my dev box where if it ran out of memory the OOM
killer would kill and AF_PACKET thread, which would then cause suricata
to segfault.

You can check if this is happening by grepping for 'Killed process' in
your syslog.

- -Coop

On 9/9/2013 1:08 AM, Christophe Vandeplas wrote:
> 
> I do need to say that the box is currently underscaled. (not enough
> CPU and not enough RAM)
> RAM is coming, and to solve the CPU problem on the short term we're
> going to filter the traffic on the network taps (or capture filter) to
> remove the useless traffic that's passing.
> 
> Christophe
> _______________________________________________
> 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/
> 


- -- 
Cooper Nelson
Network Security Analyst
UCSD ACT Security Team
cnelson at ucsd.edu x41042
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSLfJKAAoJEKIFRYQsa8FWATEH/i7Eny2+yVlhOTkdqmCyeGG9
L0PXchVoQX0BRMKG5kERt8QPy4B3CEq1AjoKZl/4lLnBFarcTdtX2B0drLSQP64f
qsGJBQdyIZRwVEndga3ZY4YfLm8eN031SH7GAXoouQyupvIqdER/r84ktGHGh5vS
rHkT5qYq39GP/1NrFDnPJ4aitjHWz0nnUuLjJmfhWKFeonEq0sIv7SWObkL63rC0
DEPOJB0zJBgVpTbHYikWMjLBbOYkt0AFqMx7tjoNiNxbajsPG7XFzpgTfGju2WsH
4W9P9re+A5FeGwsPAbe2Jn6T1kHRw0vR5gcZ/X42cKThm8R6HGGgTuh+oOO/7kw=
=MoVq
-----END PGP SIGNATURE-----