snort-1.8 and mysql timestamp problem...

[Michael Teng <mteng () altavista com>]

I have snort-1.8 and mysql 3.23.40 running on Sparc Solaris 2.51 and when the entries are logged into the database the 
timestamp is always 0000-00-00 00:00:00. Is anyone else having a problem with this? All other entries in the database 
are okay except for the timestamp. The alert file has the correct timestamp but somehow these timestamps are not 
correctly logged into the database. 

I go into mysql and look at the entries for event:

select * from event limit 0,2; 

and the timestamps are still zeros. I've read that the timestamp is generated once the entry is created but in my case 
the timestamp is not created. Any thoughts?? 


Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com

_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
http://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users