Hi,

I have just gone through a pretty ugly upgrade from 4.5.2 to 4.6.0 (hoping to continue to 4.6.3) and I have the following errors:

user error: Table 'xeno_drpl2.flood' doesn't exist
query: DELETE FROM flood WHERE timestamp < 1125009439 in /home/xeno/public_html/includes/database.mysql.inc on line 66.

And

Fatal error: Unknown column 'severity' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (1, 'php', 'Table \'xeno_drpl2.flood\' doesn\'t exist query: DELETE FROM flood WHERE timestamp &lt; 1125009439 in /home/xeno/public_html/includes/database.mysql.inc on line 66.', 2, '', '/index.php?q=admin', '131.203.100.29', 1125013039) in /home/xeno/public_html/includes/database.mysql.inc on line 66

I can view the admin pages but if I try to submit anything these errors stop me. Looking at it is seems that I am missing the .flood table. Looking at the database there is indeed no flood table.

Could someone post some SQL so that I can insert this table please?

Cheers,

Matt

Comments

eloieli’s picture

I rummaged around and found code to insert the flood table. I thought all would be right with the world (ever the potimist) and now I get the following error


Fatal error: Unknown column 'severity' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (1, 'php', 'Unknown column \'severity\' in \'field list\' query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (1, \'regular\', \'cron run completed (via poormanscron)\', 0, \'\', \'/?q=user/login\', \'131.203.100.29\', 1125021410) in /home/xeno/public_html/includes/database.mysql.inc on line 66.', 2, '', '/?q=user/login', '131.203.100.29', 1125021410) in /home/xeno/public_html/includes/database.mysql.inc on line 66

This is a little harder for me to solve. The Line 66 in databse.mysql.inc is:

    trigger_error(mysql_error() ."\nquery: ". htmlspecialchars($query), E_USER_ERROR);

Which looks to me simply like it's reporting the error rather than the source of the error.

It seems like it's trying to insert information into a no existent field but I don't know where that field is. Can anyone help?

eloieli’s picture

I sorted this one out in the end.

ALl I can say is I should ahve listened when people said to deactivate custom modules and themes when upgrading. You'll save yourself a lot of headaces.

bertboerland’s picture

I had the same

go to mysql and give
ALTER TABLE watchdog ADD COLUMN severity tinyint(3) unsigned NOT NULL default '0';

did the trick for me.
--
groets
bertb

--
groets
bert boerland