By SimonVlc on

I´m having problems upgrading the db from 4.5.2 to drupal 4.6.

I execute the script update.php selecting the 2005-01-07 update. It runs ok, except for one table:

2005-01-18

CREATE TABLE {vocabulary_node_types} (

vid int(10) NOT NULL default '',

type varchar(16) NOT NULL default '',

PRIMARY KEY (vid, type))
FAILED

Anyone knows what´s bad here? Ty in advance.

Comments

kbahey’s picture

kbahey commented

I hope you are running on a test copy first before doing it to the live site.

Anyway, try the 4.5.0 2004-10-31 update. As I recall, there were no DB changes from 4.5.0 to 4.5.2.

Again, try it on a test copy first.
--
Consulting: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

SimonVlc’s picture

SimonVlc commented

Yes, I´m doing all with a test site and having backups of all my data. If I try the update 2004-10-31 (having restored the db to the initial status) I get this error:

Fatal error: Unknown column 'severity' in 'field list'
query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (0, 'php', 'Table \'search_total\' already exists
query: CREATE TABLE search_total (
word varchar(50) NOT NULL default \'\',
count int(10) unsigned default NULL,
PRIMARY KEY word (word)
) TYPE=MyISAM in /usr/home/hidrahyl/bonospoker.com/includes/database.mysql.inc on line 66.', 2, '', '/update.php?op=update'

kbahey’s picture

kbahey commented

This is a new column in 4.6. I think what happens is that the upgrade fails for some reason and watchdog tries to insert a line, but since the database is not yet upgraded to 4.6, this column does not exist.

Try this:

Restore the database to the state it was before the update attempt (i.e. 4.5.2 database).

In the update.php, there is a line that says:
$access_check = TRUE;

Change that to FALSE, and save the file. Then point your browser to the update script and the 2004-10-31 and see what happens.

--
Consulting: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

SimonVlc’s picture

SimonVlc commented

but it gives me the same error. And the error is given by the script itself, not the watchdog module.

kbahey’s picture

kbahey commented

What is happening is that creating the search_total table is failing, and that is causing a log attempt to happen, which in turn fails because the severity column does not exist yet.

Did you clean the database before you retry?

Try dropping all tables from the database, then reloading the 4.5.2 from scratch, and then retry the upgrade. Or you can simply drop the search_total table.

--
Consulting: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

Donovan’s picture

Donovan commented

The access_check=FALSE tweak worked like a charm for me! It allowed the 4.6 updater to work and bailed me out of a bind. Much appreciated!

"It always seems impossible, until it is done."
- Nelson Mandela

paul@grabthemic.org’s picture

paul@grabthemic.org commented

Between the FreeBSD ports process doing a destructive upgrade and overwriting my config files so I couldn't login and the Drupal upgrade script putting my database content and the dump I pulled out of sync, my site is upside down.

Yes, a backup before starting would have allowed me to restore things a little easier but I was a little puzzled when i couldn't login. Where is that information stored? There is no conf.php in the 4.6 tarball, and it seems that functionality is duplicated in settings.php. Hunting for that information is not what I want to be doing when I faced with something like this. 

user error: Unknown column 'severity' in 'field list'
query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (0, 'access denied', '<em>admin</em> denied access.', 1, '<a href=\"?q=admin\" class=\"active\">view</a>', '/drupal/index.php?q=admin', '192.168.2.3', 1115751381) in /usr/local/www/data-dist/drupal/includes/database.mysql.inc on line 66.

I'll ask around and see if anyone was using this Drupal site at all before I rebuild it. But just a heads up for anyone else who moves from 4.5.x to 4.6.

JohnR’s picture

JohnR commented

FWIW, you can try to set $access_check to FALSE in update.php. On the database update page, selecting update from 4.5 solved this particular problem for me.

However, drupal has now gone completely nuts. On the index page, it thinks I am logged in as the admin user; on the admin page, it thinks I am not logged in. I give up, for now, and have reverted to 4.5.2.

TheFazz’s picture

TheFazz commented

I've been trying to upgrade from 4.5.2 to 4.6.0 for some time now. For info, I have very little knowledge of PHP, mySQL and unix, so perhaps I am doing so many things wrong.

For info, I am still testing the upgrades on my WinXP before I even attempt this on my Linux hosting.... I am using phpmyadmin to help me with all the mySQL stuff. I am using phpdev5 on my WinXP. I guess this comes with:

  • PHP4.2.3
  • MySQL4
  • phpMyAdmin 2.3.2
  • apache 1.3.2

Here's what I had experienced wrong:

  1. uploading the mySQL database from the "live" website: the database file was about 16Mbytes... so I had to split it into many pieces. The most tedius was splitting the "accesslog" table which itself was is 5Mbytes
  2. so once I uploaded the database, I ran the site on my WinXP: it was not perfect... there was some such about not being able to send cookie headers or something - anyway, I ignored this...
  3. I started disabling all the distributed modules, but it didn't go well: as php didn't display any page after that... I was stuck...
  4. so I decided to delete the 4.5.2 drupal scripts and install the 4.6.0 scripts - so far okay (of course I kept a backup of the 4.5.2 scripts
  5. I ran the update.php script which didn't go well: it defaulted to the last updates since 4.5.2 - which was about right. But the last line of the update was a fatal error...
    2005-01-19

    ALTER TABLE {vocabulary} DROP nodes
    OK

    2005-01-20

    Fatal error: Call to undefined function: node_list() in c:\www\phpdev\www\mykartorg\database\updates.inc on line 2161

  6. I now run out of ideas - except to try again... but thought against this and decide wait for 4.7 instead (hopefully with an easier idiot proof upgrade script

But if anybody has had a similar experience and found a solution please please let me know! Thanks in advance!

Cheers
Fazz

http://www.my-kart.org/

eco_bogdan’s picture

eco_bogdan commented

I just add text column severity to watchdog in phpMyAdmin. It works!

maca’s picture

maca commented

I upgraded from 4.4.0 to 4.6.3 this week and found this error too. I thing this is a bug in updates.inc on line 2130:

vid int(10) NOT NULL default '',

could be:

vid int(10) NOT NULL default '0',

It works for me.

hi