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@snort.org.
Thanks,
Justin Heath
On 11/25/06, Jason Haar <Jason.Haar@trimble.co.nz> 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@snort.org?
I can report a "me too" on this now. 2.6.1.1 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.
--
Cheers
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
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users
