[Snort-users] Barnyard2 and dealing with mysql_error
jlay at ...13475...
Sun Aug 7 16:34:34 EDT 2011
The issue isn't with barnyard not running (in this case at least) it's with
the fact that barnyard runs, attempts to connect to the remote db, gets the
mysql_error, then that alert is never seen from again. I suppose I could
nuke the waldo file and aim barnyard at the current u2 file, but eh…a bit of
a hassle. Thanks though.
From: Dave Werden <dwerden55 at ...131...>
Date: Sun, 07 Aug 2011 13:02:46 -0400
To: James Lay <jlay at ...13475...>, Snort
<snort-users at lists.sourceforge.net>
Subject: Re: [Snort-users] Barnyard2 and dealing with mysql_error
Have you tried adding Barnyard2 to your cron? A quick script to check if
it's running and restart if it's not, then have this cron'd at every couple
minutes or so? Similar solutions have worked in the past.
Hope that helps a little,
Sent from my T-Mobile myTouch 3G Slide
----- Reply message -----
From: "James Lay" <jlay at ...13475...>
Date: Sun, Aug 7, 2011 7:52 am
Subject: [Snort-users] Barnyard2 and dealing with mysql_error
To: "Snort" <snort-users at lists.sourceforge.net>
So yea?sometimes my connection goes wonky and drops. Is there a way to get
barnaryd2 to restart after something like this? I was under the impression
that one of the benefits of using barnyard2 instead of straight snort->db
was to due away with surprises like this. Currently I'm log monitoring and
just stopping the process so I can manually start it later?hardly a
solution, but at least I don't lose my data. Anyone have a better solution
to this? Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Snort-users