Snort mailing list archives
Re: mysql database "gone away"
From: Jason Brvenik <jasonb () sourcefire com>
Date: Mon, 16 Jul 2007 20:45:57 -0400
Obviously it would be nice if some process could be configured to retry this connection and get the data back to the server. What do other people use to get over this problem ? I mean, if you have a connectivity problem into your data centre and you lose connectivty to all your probes, do people really manually log into each remote probe and restart the service ? It just seems a bit . . . manual. I accept that it is a limitation of the mysql client in use, but in practical terms what do people do to ensure the database link doesn't stay down for hours(days/weeks) after a temporary glitch like this ?
Use unified output and barnyard. Writing to the database directly from the snort engine directly should be a last resort. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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
Current thread:
- mysql database "gone away" David Ryan (Jul 16)
- Re: mysql database "gone away" Dirk Geschke (Jul 16)
- Re: mysql database "gone away" Jason Brvenik (Jul 16)
- <Possible follow-ups>
- Re: mysql database "gone away" cconn (Jul 17)
