On January 4, 2008, Javier Fernández-Sanguino Peña wrote: > tag 445334 upstream > thanks > > On Thu, Oct 04, 2007 at 08:13:12PM -0600, Gordon Haverland wrote: > > I've gone through 2 snort-mysql upgrades now, and seen in my > > logs after the upgrade a note that my dbase version (106) is > > too old, I need to have 107 (or better). The log notes that > > there are "cursory details" in README.database. Well, if the > > details are there, they are too cursory. Please provide more > > information. > > Do you mean you get the error "database: The underlying > database seems to be running an older version of the DB schema > (current version=%d, required minimum version= %d)." ? > > The doc/README.database file seems to only contain changelog > entries of the changes in the database schema up to v106 > (2002-09-03). I'm not sure what chances have been introduced > from v106 to v107 (which changed in 2.6) > > Googling I've found this entry: > > http://bookmarklust.blogspot.com/2007/09/upgrading-snort.html > > Which suggests doing: > > 1. ALTER TABLE signature ADD sig_gid INT UNSIGNED; > + This is the only addition needed by the new version of > snort. 2. INSERT INTO schema (vseq, ctime) VALUES ('107', > now()); + Snort queries the schema version when it starts to > make sure the DB is compatible. > 3. DELETE from schema where vseq=; > + Now we need to remove the previous version from the > table > > Could you please confirm if this fixes your problem? If so, I > will ammend upstream's README.database documentation, if not > unfortunately, this is an upstream bug I cannot do anything > about. I will forward it.
Probably in November (another one or two upgrades of snort-mysql) I dropped the snort tables and remade them. Which got rid of the error. However, it would be nice to have something like what you suggest in the documentation. I hope you had a nice Christmas/New Years. Gord
