By wellsy on

So the 4.7 release candidates are maturing.

Critical bugs look to be pretty thin on the ground?

drupal.org is now running on 4.7? Yes? No?

So I guess there is a way of migrating 4.6 data to 4.7? Correct/Incorrect?

If you have a proven solution please share it here.

PS: please check all flamethrowers at the door (LOL)

⋅ Categories: Drupal 4.7.x

Comments

heine’s picture

heine commented

It depends; the biggest issue seems to be the removal of the base tag (see http://drupal.org/node/58106). This means that links are there, but not working; of course this depends on how (and where) you've constructed your links and whether or not your drupal site is in a directory.

Update.php attempts to modify all links and even yesterday Steven made a patch to improve the process (see http://drupal.org/node/58131).

Removal of the base tag was a bugfix; it is however entirely possible to put it back using the theme (simply change page.tpl.php), somewhat mitigating the issue.

A second big issue; some modules haven't been released for 4.7.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

wellsy’s picture

wellsy commented

as I have moved some time ago to standardise all links to utilize the base tag format.

With some sql magic that will not really be a problem though.

My real concern is to be able to 'seamlessly' migrate my 4.6 database to 4.7.

Is that now possible?

Modules will come for sure and I personally only have a very small few on my required list.

wellsy

orchidsonline.com.au

heine’s picture

heine commented

I just updated a site from 4.5 to 4.7 RC2. Apart from the base tag issue, no problems. This is, however, a site with just two additional modules.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

wellsy’s picture

wellsy commented

can you describe your proceedure?

wellsy

orchidsonline.com.au

Steven’s picture

Steven commented

You're wasting everyone's time by posting forum topics like this.

There is an easy to use upgrade script and tons of documentation on how to use it. Did you actually look around? Instructions are mentioned in the release announcement, in the handbooks and can be located with a simple search.

http://drupal.org/search/node/upgrade+drupal

wellsy’s picture

wellsy commented

I have been busy for a few days so not been back to see what has been happening on the forums.

So I eagerly check my recent posts and sure enough a kind soul has left me some pearls of wisdom for me to go checking in answer to my question.

So I have just ventured off and followed Steven's friendly advice and I 'make the effort' to do a search.

I might add Steven, I really do search for answers to my questions all the time here on drupal.org first...thank you very much. I must also confess that the new search is much better than the old version.
However....On resolving this issue I personally have found nothing useful so far...hence my present question.

On reading through some of the resulting search teasers I am a little confused and I begin to wonder why you suggest this search?
On spending some time to make the effort I eventually really do wonder if you did the same search (on the same website) as the list of results which I took the trouble to read through mentioned not a lot of positive results. In fact they did not inspire me to fully read beyond the first page of results.

I did click through to the third page of results and read the teasers but most of the results are old and outdated or have been read by me recently without gaining anything useful. After that I gave up.

So I came back to my question here and carefully read and digested your kind advice again and thought I must visit the release document for more clues.

First I visit Installation and configuration where I find nothing which leaps off the page to tell me how to upgrade from 4.6 to 4.7. I am getting a little impatient at this stage because I have visited these same pages before...in some cases many times.

So I click back and see what else may be new and useful. I see links to 'Module Upgrading Guide' and 'Theme Upgrading Guide' and 'Drupal issue tracker'. None of these links seems to be of much use to me in answer to the present question.

BUT then....there it is? I see another search link 'Please search' so I click this one and lo and behold....dead end....oh shit!

Go on click it and see.

I actually have said this before and here....I know....I just can't help myself because 4.7 sounds so cool.

I'll waste no further time of my own....or anyone elses here on this forum...I'll take your advice Steven.

For now, I'll just forget all aspirations of moving ahead to 4.7 and be happy with the marvellous tool which this community has provided to me which I have turned into something a great many visitors to my website seem happy to experience... and that is drupal 4.6.

Thanks everyone! Happy Easter!

wellsy

orchidsonline.com.au

[fixed anchors - Heine]

cel4145’s picture

cel4145 commented

First, if you visited the first search result and read more closely, you find that by looking in the book navigational structure, there is a page listing for additional information on updating to 4.7.

Second, I don't know why you would expect friendly assistance with a user profile that uses the Drupal contributions field to gripe. That's not what it is intended for, but of course you know that.

heine’s picture

heine commented

I did a local dry-run

  1. Logged in as admin (uid 1)
  2. Disabled extra, non-core modules
  3. Switched default theme to bluemarine
  4. Checked whether admin had default theme as well
  5. Prepared a 4.7 RC2 installation
  6. Deleted all old files
  7. Moved prepared 4.7 installation to site location
  8. Ran update.php (autodetected setting)
  9. Saw 1 inconsequential warning (a table was already in the correct layout)
  10. Browsed the site, submitted some stories, all well
  11. Installed upgrades of the two modules
  12. Installed 4.7 theme

Deja: http://drupal.org/node/49491#comment-93484
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

wellsy’s picture

wellsy commented

I can confirm that I have (in general) followed your steps up to 8 and found the update script either does not ever complete or scrambles the database rendering it unusable. Note though that the last attempt was Beta 2 I believe.

Over the next couple of weeks I may try again with the latest RC whatever that will be at the time and let you know how that goes. This depends on my workload here though so if the worst happens it may be 3-4 weeks.

wellsy

orchidsonline.com.au

wellsy’s picture

wellsy commented

On my test server where I have been migrating backups to a test area for quite some time with no trouble (same version of 4.6)

  1. Logged in as admin (uid 1)
  2. Disabled extra, non-core modules
  3. Switched default theme to bluemarine
  4. Checked whether admin had default theme as well
  5. Prepared a 4.7 RC2 installation
  6. Deleted all old files NOT DONE (see next step)
  7. Moved prepared 4.7 installation to a new directory on webserver
  8. Opened update.php Error message>>>>
    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\\"all\\";', timestamp = 1145267945 WHERE sid = '13e2d974ad6937d018b74503b693369e' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.', 2, '', '/interactive47rc2/update.php', '', '220.245.180.133', 1145267945) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120
  9. Ran update.php (autodetected setting)
  10. Saw an unrecoverable error >>>>
    An unrecoverable error has occured. You can find the error message below. It is advised to copy it to the clipboard for reference. Please continue to the update summary

    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'reset(): Passed variable is not an array or object in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/update.php on line 404.', 2, '', '/interactive47rc2/update.php?op=do_update', 'http://www.orchidauction.biz/interactive47rc2/update.php?op=selection', '220.245.180.133', 1145268168) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120
    { "status": true, "percentage": 100, "message": "Updating complete" }
    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:1:{s:5:\\"error\\";a:1:{i:0;s:150:\\"warning: reset(): Passed variable is not an array or object in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/update.php on line 404.\\";}}watchdog_overview_filter|s:3:\\"all\\";update_remaining|N;', timestamp = 1145268168 WHERE sid = '13e2d974ad6937d018b74503b693369e' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.', 2, '', '/interactive47rc2/update.php?op=do_update', 'http://www.orchidauction in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

    Starting updates

    Please wait while your site is being updated.

    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\\"all\\";update_remaining|a:29:{i:0;a:2:{s:6:\\"module\\";s:6:\\"system\\";s:7:\\"version\\";i:150;}i:1;a:2:{s:6:\\"module\\";s:6:\\"system\\";s:7:\\"version\\";i:151;}i:2;a:2:{s:6:\\"module\\";s:6:\\"system\\";s:7:\\"version\\";i:152;}i:3;a:2:{s:6:\\"module\\";s:6:\\"system\\";s:7:\\"version\\";i:153;}i:4;a:2:{s:6:\\"module\\";s:6:\\ in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

  11. So clicked the error summary >>>
    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'reset(): Passed variable is not an array or object in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/update.php on line 498.', 2, '', '/interactive47rc2/update.php?op=error', 'http://www.orchidauction.biz/interactive47rc2/update.php?op=selection', '220.245.180.133', 1145268265) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Cannot modify header information - headers already sent by (output started at /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc:120) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/common.inc on line 139.', 2, '', '/interactive47rc2/update.php?op=error', 'http://www.orchidauction.biz/interactive47rc2/update.php?op=selection', '220.245.180.133', 1145268265) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

    Drupal database update
    warning: reset(): Passed variable is not an array or object in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/update.php on line 498.
    warning: Cannot modify header information - headers already sent by (output started at /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc:120) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/common.inc on line 139.
    The update process was aborted prematurely while running update # in .module. All other errors have been logged. You may need to check the watchdog database table manually.

  12. clicked the link to the home page >>>
    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'n.vid' in 'field list'\nquery: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.moderate, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE n.nid = 1 in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.', 2, '', '/interactive47rc2/', 'http://www.orchidauction.biz/interactive47rc2/update.php?op=error', '220.245.180.133', 1145268321) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'n.vid' in 'field list'\nquery: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.moderate, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE n.nid = 3349 in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.', 2, '', '/interactive47rc2/', 'http://www.orchidauction.biz/interactive47rc2/update.php?op=error', '220.245.180.133', 1145268321) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

    repeated same error 10 times then

    Home
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    by Anonymousn/a
    123456789…next ›last »

    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\\"all\\";', timestamp = 1145268322 WHERE sid = '13e2d974ad6937d018b74503b693369e' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.', 2, '', '/interactive47rc2/', 'http://www.orchidauction.biz/interactive47rc2/update.php?op=error', '220.245.180.133', 1145268322) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120

  13. clicked through to admin area by adding the 'admin' to the url
  14. admin area has a watchdog table but no other formatting and the below error >>>
    Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'Unknown column 'cache' in 'field list'\nquery: UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\\"all\\";', timestamp = 1145268645 WHERE sid = '13e2d974ad6937d018b74503b693369e' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.', 2, '', '/interactive47rc2/admin', '', '220.245.180.133', 1145268645) in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120
  15. so I would call this a failed update all in all

Any ideas?

EDIT********************************************************************************************

Looks like no column 'referer' in watchdog table is the problem.

So I added that column to the table as per the 4.7 RC 2 sql file

Returned to update.php......no errors yet!

Ran update with seeming success....but no

I visit the logs of errors and there is

Unknown column 'cache' in 'field list' query: UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\"all\";', timestamp = 1145269910 WHERE sid = '13e2d974ad6937d018b74503b693369e' in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.

and also

Unknown column 'n.vid' in 'field list' query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.moderate, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE n.nid = 3379 in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.

Home page has no errors but consists of

Home
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
by Anonymousn/a
123456789…next ›last »

Looks to be a failure to me....out of time tonight so I guess I'll wait for some spare time to try to sort it out.
Maybe some answers from here as well?

EDIT#######################################################################

Decided to fix the 'cache' in sessions table as per sql file

Ran update again and this time it really semed to be going to succeed but!!!!

Unknown column 'n.vid' in 'field list' query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.moderate, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE n.nid = 3368 in /mounted-storage/home8/sub001/sc14839-HDBP/www/interactive47rc2/includes/database.mysql.inc on line 120.

Thats really it for tonight.

I think I'll restore the backup database and wait for some advice with this one.

wellsy

orchidsonline.com.au

heine’s picture

heine commented

First question, although I would expect to see other errors:
=>Does the database user have ALTER privileges?

It all starts with one error when you access update.php (before you even start updating). That error occurs when executing the query

UPDATE sessions SET uid = 1, cache = 0, hostname = '220.245.180.133', session = 'messages|a:0:{}watchdog_overview_filter|s:3:\\"all\\";', timestamp = 1145267945 WHERE sid = '13e2d974ad6937d018b74503b693369e'

Upon which MySQL complains about Unknown column 'cache' in 'field list' query: [snip].

Watchdog faithfully tries to insert this error in the error log using the query:

INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES [snip]

Upon which MySQL complains about Warning: Unknown column 'referer' in 'field list' query: [snip]

When updating you get a number of other watchdog errors when it tries to store the error:

reset(): Passed variable is not an array or object in [path]/update.php on line 404.

reset() is right. $_SESSION could not be saved to the database and can't be retrieved; the entire update will fail.

Why aren't the session and watchdog tables altered as they should be when update.php is accessed? Before even starting an update, update.php tries to fix several tables, so they can be used by the program:

// Errors switched off
  update_fix_system_table();
  update_fix_access_table();
// Error reporting on again
  update_fix_schema_version();
  update_fix_watchdog_115();
  update_fix_watchdog();
  update_fix_sessions();

Let's walk the different queries one by one and you can perhaps tell me whether the table modification was made.

The 4.6 system table doesn't contain a weight field (disregard the comment in update.php); it is added by update_fix_system_table()

ALTER TABLE {system} ADD weight tinyint(3) unsigned default '0' NOT NULL, ADD KEY (weight)

=> Do you see a 'weight' column in the system table after the failed update?

Then update_fix_access_table() converts the access table to UTF-8 if necessary.

The last three updates:

  update_fix_watchdog_115();
  update_fix_watchdog();
  update_fix_sessions();

depend on the schema_version:
update_fix_watchdog115 only alters tables when schema_version < 115 (and not already done)
update_fix_watchdog only alters tables when schema_version < 142 (and not already done)
update_fix_sessions only alters tables when schema_version < 130 (and not already done)

The detected schema_version depends on update_fix_schema_version. This function looks into the variable table for the value of update_start. On a pristine 4.6.6 install this is 2005-03-21 corresponding with schema_version 128.

=> Do you see a row 'update_start' in the table 'variable'? What is the value (before updating)?
=> Do you see other 'update_*' rows in the table 'variable' (before updating)? Which ones?

update_fix_schema_version then proceeds by adding a schema_version column to the system table:

ALTER TABLE {system} ADD schema_version smallint(3) not null default -1

The function then saves the determined schema_version as the schema_version of the system.module, then deletes update_start from the variable table.

=> Do you see a column 'schema_version' in the 'system' table after the failed update? What is the value for 'modules/system.module'?

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

wellsy’s picture

wellsy commented

Thanks very much for taking the time to detail this here Heine. Unfortunately, I have very little time here tonight now...I just clicked here for a brief look prior to heading off for the night so no time to really digest your train of thought above now.

=> Do you see a 'weight' column in the system table after the failed update? SW: Yep
weight tinyint(3) UNSIGNED No 0

=> Do you see a row 'update_start' in the table 'variable'? What is the value (before updating)? SW: Negative

I'll make sure I come by again tomorrow night much earlier so I can spend some time with this.

Yep....the two fields 'cache' and 'referer' seem to be the problem....I see that.

I was intending to reinstate another backup database and add those two fields first (prior to updating) would that work?

=>Does the database user have ALTER privileges? SW: I believe so....but will check with my host and repost

=> Do you see other 'update_*' rows in the table 'variable' (before updating)? Which ones? SW: No
Only two...namely
name varchar(48) No
value longtext No

=> Do you see a column 'schema_version' in the 'system' table after the failed update? SW: Yep

What is the value for 'modules/system.module'?

SW: modules/system.module system module Handles general site configuration for administrat... 1 0 0 0 178

Thanks again Heine! I'll be back with more tomorrow night.

wellsy

orchidsonline.com.au

heine’s picture

heine commented

Hi Wellsy,

Do you use phpmyadmin? When browsing to a table you have to select the tab 'Browse' to see the actual rows instead of the table structure.

The variable table for example has two fields (columns) 'name' and 'value' but the actual rows (name, value) are:

row 1: update_start	 s:10:"2005-03-21";
row 2: filter_html_1	i:1;
row 3: clean_url_ok	i:1;
row 4: site_name s:9:"DRUPAL4.6";
-> more

Alternatively, strip as much content from a copy of the backup database as you can (to reduce its size), but still reproducing the problem, change the admin account and mail me the compressed (7-zip) resulting file, so I can take a look.

Edited to add: you have to delete old drupal files before moving a 4.7 installation in.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

wellsy’s picture

wellsy commented

I have had a hellish long day today so nothing more done.

I'll see what I can do tomorrow before I start nightshift and get back if I progress.
Thanks again Heine!

wellsy

orchidsonline.com.au

Bèr Kessels’s picture

Bèr Kessels commented

It seems I am getting the same problems, so here are my details:
=>Does the database user have ALTER privileges?
Yup. And AFAIK drupal or Mysql will trow errors that tell you about this problem.

=> Do you see a 'weight' column in the system table after the failed update?
Yes. It is not there before, and there after the upgrade.

=> Do you see a row 'update_start' in the table 'variable'? What is the value (before updating)?
No. See below
=> Do you see other 'update_*' rows in the table 'variable' (before updating)? Which ones?
Yes, two, see below. 

mysql> select * from variable where name like '%update%';
+---------------+--------------------+
| name          | value              |
+---------------+--------------------+
| update_start  | s:10:"2005-04-14"; |
| update_80_fix | b:1;               |
+---------------+--------------------+

The weird thing, is that Drupals update.php has 133 as default update step set. It lokos to me like this is part of the problem.

=> Do you see a column 'schema_version' in the 'system' table after the failed update? What is the value for 'modules/system.module'?

It is already there before I even POSTed the update. So just visiting the update page creates this column:
query: ALTER TABLE system ADD weight tinyint(2) default '0' NOT NULL, ADD KEY (weight)
query: ALTER TABLE access DEFAULT CHARACTER SET utf8
query: ALTER TABLE access CHANGE `mask` `mask` varbinary(255) DEFAULT '' NOT NULL, CHANGE `type` `type` varbinary(255) DEFAULT '' NOT NULL
query: ALTER TABLE access CHANGE `mask` `mask` varchar(255) CHARACTER SET utf8 DEFAULT '' NOT NULL, CHANGE `type` `type` varchar(255) CHARACTER SET utf8 DEFAULT '' NOT NULL

Some more interesting facts:
AFTER visiting update.php, but without POSTing any update yet, update did some destructive queries on its own alread, though they all seem to have been done without errors. Variables now are:

mysql> select * from variable where name like '%update%';
+-----------------------+-------+
| name                  | value |
+-----------------------+-------+
| update_watchdog_fixed | b:1;  |
| update_80_fix         | b:1;  |
| update_access_fixed   | b:1;  |
| update_132_done       | b:1;  |
| update_170_done       | b:1;  |
+-----------------------+-------+

Why 170 is there is abve me, but I guess that is alright.

---
Professional | Personal

Bèr Kessels’s picture

Bèr Kessels commented 
drupal_get_installed_schema_version('system') < 130

Evaluates to FALSE if that variable does not exist at all!

Running 

      db_queryd("ALTER TABLE {sessions} ADD cache int(11) NOT NULL default '0' AFTER timestamp");

By hand before the updates makes it all go well.

Bèr

---
Professional | Personal

nathandigriz’s picture

nathandigriz commented

I my case there is no way to test or migrate to 4.7 because there is no i18n module to speak of and Jose has stated that there will not be one until 4.7 is finished. Catch22.

sepeck’s picture

sepeck commented

Read the update.txt included with the download. For a more general guideline, click the best practices link in my sig. The update proceedure hasn't changed significantly in many versions.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

wellsy’s picture

wellsy commented

but really I see quite a few seemingly important steps are missing when you compare it to Heines proceedure above.

***************************************************************************************************
from the update text file

// $Id: UPGRADE.txt,v 1.2 2005/12/10 19:26:47 dries Exp $

UPGRADING
---------

1. Backup your database and Drupal directory - especially your
configuration file in 'sites/default/settings.php'.

2. Log on as the user with user ID 1.

3. Remove all the old Drupal files then unpack the new Drupal
files into the directory that you run Drupal from.

4. Modify the new configuration file to make sure
it has the latest and correct information.

5. Run update.php by visiting http://www.example.com/update.php.
***************************************************************************************************

Maybe this text file should itself be updated?

I am also wondering is it that when update runs for me that the size of my database (varies between 10-15mB) could be causing some problems?

Has anyone updated successfully a reasonable size database?

wellsy

orchidsonline.com.au

icenogle’s picture

icenogle commented

wellsy,

I don't know what you consider reasonable size. I have 400 or so nodes. I initially got stuck at 4.7beta2. After that things were wacky for quite a while. At 4.7beta5 the update script started hanging. It wouldn't finish up, and the results were unusable. I was unsuccessful with beta3, beta4, beta5, beta6, and RC1.

HOWEVER, everything cooked with RC2. The update proceeded without a problem. So I encourage you to give it another go.

Generally, expect that the experienced people on this site have forgotten what they didn't know when they started. And expect them to give you a hard time for not knowing what they have forgotten to tell you. That, I'm afraid, is human nature.

D Icenogle

wellsy’s picture

wellsy commented

I think that this may be at least some of the reason update fails for me.

I'll definitely try the process again with RC2 after reading your experience.

wellsy

orchidsonline.com.au

venkat-rk’s picture

venkat-rk commented

No offence intended to anyone, but I agree with you that the existing upgrade handbook is very confusing for people without much techie skills.

I have committed myself to try and write a clearer one with help from people on these forums and the doc list, although I haven't sent a page yet to Sepeck. I have a reasonable outline in place, though and it is now mostly rearranging, rewriting and adding stuff and sending it out for review.

Regarding your question about upgrading a large db, in response to one of my posts, Zen pointed me to the bookpage on the 4.7 .install file that had some interesting things to say about upgrading a large database (read the section about Multi part updates). But, I don't really know if that is how the upgrade script handles stuff in 4.6

sepeck’s picture

sepeck commented

My notes on my upgrade here: http://www.blkmtn.org/node/325
I literally followed the upgrade.txt instructions using a database back per http://drupal.org/node/29161
That's it, nothing fancy or techie.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

xMarc’s picture

xMarc commented

Followed instructions EXACTLY 3 times:
1) as explained in INSTALL.txt and UPGRADE.txt
2) as in Introduction to Upgrading..., AND
3) nifty little Upgrading to Drupal 4.7 video.

Exact same result every time I run update.php:

Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog... (5 times), followed by a number of
user warning: Unknown column 'weight' in 'order clause' query: SELECT name, filename, throttle, bootstrap FROM system ....and
The update process was aborted prematurely while running update # in .module. ......, etc., etc., etc.

This pattern of warning, errors and aborts have surfaced numerous times in posts.

Any progress on this ongoing problem?

grcm’s picture

grcm commented

On one test site, the watchdog insertion error went away when I re-opened the page.

Odd.

-- Version Control your Drupal web site with The File High Club's Free Trial!