[Snort-users] problem with snort 188.8.131.52 (stop working)
justin.heath at ...11827...
Sat Nov 25 16:24:50 EST 2006
Could either of you enable debugging and provide a backtrace of the
running process (when having the issue)? If so, please send the info
over to bugs at ...10585...
On 11/25/06, Jason Haar <Jason.Haar at ...294...> wrote:
> 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. 184.108.40.206 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.
> Jason Haar
> 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