[Snort-users] Snort 2.6.1 Stops Logging
Jason.Haar at ...294...
Tue Nov 21 16:33:59 EST 2006
Colin Grady wrote:
> I've migrated one system from Snort 220.127.116.11 <http://18.104.22.168> to Snort
> 2.6.1. I've made no configuration file changes and no command-line
> changes between the two releases, but after somewhere around 20-30
> minutes after being started Snort 2.6.1 seems to stop logging data.
> I'm using unified logging, which is being processed through Barnyard.
> The Snort process continues to run and the processor time continues to
> climb, but the unified logs stop growing -- so it's not related to
> Barnyard as best as I can tell.
> Anyone else seen anything like this?
I think this is a "me too". I've just noticed that 2.6.1RC1 appears to
work initially, but stops logging at some later time. I am just
upgrading to 2.6.1 to see if that fixes it - but your report implies it
won't. We're using both syslog and mysql output modules - and both stop
reporting - so that (plus your barnyard report) implies the problem is
occurring somewhere earlier on.
This is snort-2.6.1RC1 under CentOS4.4
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