[Snort-users] problem with snort 126.96.36.199 (stop working)
Jason.Haar at ...294...
Sat Nov 25 14:57:59 EST 2006
Justin Heath wrote:
> How long does it take before you see this issue? Is it possible to run
> a tcpdump to get a packet trace during this time? If so can send the
> packet trace to bugs at ...950...?
I can report a "me too" on this now. 188.8.131.52 under CentOS4.4 ran
successfully for a lot longer than 2.6.1 did, but the problem still
occurred. I'm going to guess it took >24hours for the problem to
reoccur. As that will be in the 10+Gb range, I don't think a tcpdump
will be possible :-)
"ps" showed the same condition. snort was in a "R" state, and attaching
with strace produced no output - instead of the roar of output expected.
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
More information about the Snort-users