Upgrade Fails

I've upgraded successfully a couple of times... Are these messages shown on your update.php run, or afterwards on the site itself? If the latter, what update.php said (any error messages, failures on the results page)? You executed update.php immediately after replacing the code, right? Also your configuration might be useful to know, if the above didn't suggest anything.

You should go to update.php directly, i.e. type in your browser something like www.example.com/update.php - if you try to access the actual site before update.php, then you'll get all sorts of errors, that's just natural. You're not supposed to visit the site before update.php.

Documentation: http://drupal.org/upgrade/tutorial-introduction

Honestly, I see now, that this aspect is probably not emphasized enough on that page... Perhaps you can add a comment in there.

Otherwise I assume this is 'fixed', because we already found the cause of your problem. Feel free to change status if you think otherwise.

Hmm, this smells to me like some re-appearance of the bug http://drupal.org/node/179143 (which got fixed already, though)

Which modules are enabled on your site? Are they only core modules? Can you try with the latest development version (6.x-dev) ?

The error message clearly shows that the system attempts to read menu items and some node (the last error is on node_load() ), but that should definitely *not* happen on update.php run. Your configuration must be different from what we tested here.

This is all funny, I can't make any sense in that...

Are you sure that:
- The site was OK before upgrade?
- You followed the documentation at http://drupal.org/upgrade/tutorial-introduction ?
- You disabled all non-core modules and themes (and better removed entirely) before update?
- Your server environment is compatible (might be good to know the config)

The old menu links are a known problem, not solvable in any other way than manual deleting, according to the author of that patch: http://drupal.org/node/196043

Otherwise Bluemarine or Garland are recommended for upgrade ;)

Great, the comment is in right place :)

As for the menu items, you're not the only one disliking it. I'm quite annoyed myself, going to identify and delete tens of old entries. There was quite a bit of discussion at http://drupal.org/node/196043 - some users disliked the situation so much, that discussion slipped to offending tones and got some comments unpublished even - and according to that issue, the problem is that you need to have your contributed modules disabled before update.php, so then update can't have a full information on your modules' links, and so can't know what's a link from contributed module you're about to enable again after update, and what's outdated link (core even) that will never be active again. There was also an idea of a clean-up script/feature to delete orphan links AFTER you enabled all contributed modules later (I might even suggest to include some list of known stale links for core), but with this stuff, you should go to that issue, not here (duplicate issues are not good practice). I have neither time nor knowledge on that stuff, to fix this.

any activity??

im running into several problems when upgrading d5.10 to d6.4

on opening http://www.mysite.com/update.php i get an error

user warning: Table 'cache_block' already exists query: CREATE TABLE cache_block ( `cid` VARCHAR(255) NOT NULL DEFAULT '', `data` LONGBLOB DEFAULT NULL, `expire` INT NOT NULL DEFAULT 0, `created` INT NOT NULL DEFAULT 0, `headers` TEXT DEFAULT NULL, `serialized` SMALLINT NOT NULL DEFAULT 0, PRIMARY KEY (cid), INDEX expire (expire) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /usr/local/www/mysite/www/drupal-6.4/includes/database.inc on line 514.

when i delete the table cache_block and reload the http://www.mysite.com/update.php the message disappears

so issue #1 would be: why this message?

i disabled all and uninstalled almost all contrib modules

the update screen still shows them in the list "select versions"

system module:
comment module:
book module:
statistics module:
image module:
image_gallery module:
image_import module:
views module:
admin_menu module: 

issue #2: why do i see modules that are disabled?
(because the database tables still exist?)

for the modules i disabled earlier on, i choose "no update available" so they don't interfere

on the 3rd update screen i see the progress bar and after wards a long list of errors like:

    * user warning: Table 'menu_router' already exists query: CREATE TABLE menu_router ( `path` VARCHAR(255) NOT NULL DEFAULT '', `load_functions` VARCHAR(255) NOT NULL DEFAULT '', `to_arg_functions` VARCHAR(255) NOT NULL DEFAULT '', `access_callback` VARCHAR(255) NOT NULL DEFAULT '', `access_arguments` TEXT DEFAULT NULL, `page_callback` VARCHAR(255) NOT NULL DEFAULT '', `page_arguments` TEXT DEFAULT NULL, `fit` INT NOT NULL DEFAULT 0, `number_parts` SMALLINT NOT NULL DEFAULT 0, `tab_parent` VARCHAR(255) NOT NULL DEFAULT '', `tab_root` VARCHAR(255) NOT NULL DEFAULT '', `title` VARCHAR(255) NOT NULL DEFAULT '', `title_callback` VARCHAR(255) NOT NULL DEFAULT '', `title_arguments` VARCHAR(255) NOT NULL DEFAULT '', `type` INT NOT NULL DEFAULT 0, `block_callback` VARCHAR(255) NOT NULL DEFAULT '', `description` TEXT NOT NULL, `position` VARCHAR(255) NOT NULL DEFAULT '', `weight` INT NOT NULL DEFAULT 0, `file` MEDIUMTEXT DEFAULT NULL, PRIMARY KEY (path), INDEX fit (fit), INDEX tab_parent (tab_parent) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /usr/local/www/mysite/ww/drupal-6.4/includes/database.inc on line 514.
    * user warning: Table 'menu_links' already exists query: CREATE TABLE menu_links ( `menu_name` VARCHAR(32) NOT NULL DEFAULT '', `mlid` INT unsigned NOT NULL auto_increment, `plid` INT unsigned NOT NULL DEFAULT 0, `link_path` VARCHAR(255) NOT NULL DEFAULT '', `router_path` VARCHAR(255) NOT NULL DEFAULT '', `link_title` VARCHAR(255) NOT NULL DEFAULT '', `options` TEXT DEFAULT NULL, `module` VARCHAR(255) NOT NULL DEFAULT 'system', `hidden` SMALLINT NOT NULL DEFAULT 0, `external` SMALLINT NOT NULL DEFAULT 0, `has_children` SMALLINT NOT NULL DEFAULT 0, `expanded` SMALLINT NOT NULL DEFAULT 0, `weight` INT NOT NULL DEFAULT 0, `depth` SMALLINT NOT NULL DEFAULT 0, `customized` SMALLINT NOT NULL DEFAULT 0, `p1` INT unsigned NOT NULL DEFAULT 0, `p2` INT unsigned NOT NULL DEFAULT 0, `p3` INT unsigned NOT NULL DEFAULT 0, `p4` INT unsigned NOT NULL DEFAULT 0, `p5` INT unsigned NOT NULL DEFAULT 0, `p6` INT unsigned NOT NULL DEFAULT 0, `p7` INT unsigned NOT NULL DEFAULT 0, `p8` INT unsigned NOT NULL DEFAULT 0, `p9` INT unsigned NOT NULL DEFAULT 0, `updated` SMALLINT NOT NULL DEFAULT 0, PRIMARY KEY (mlid), INDEX path_menu (link_path(128), menu_name), INDEX menu_plid_expand_child (menu_name, plid, expanded, has_children), INDEX menu_parents (menu_name, p1, p2, p3, p4, p5, p6, p7, p8, p9), INDEX router_path (router_path(128)) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /usr/local/www/mysite/www/drupal-6.4/includes/database.inc on line 514.

and 

<code>    * user warning: Unknown column 'serialized' in 'field list' query: SELECT data, created, headers, expire, serialized FROM cache_views WHERE cid = 'views_default_views:en' in /usr/local/www/mysite/www/drupal-6.4/includes/cache.inc on line 26.
    * user warning: Unknown column 'serialized' in 'field list' query: UPDATE cache_views SET data = 'a:5:{s:9:\"frontpage\";O:4:\"view\":21:{s:8:\"db_table\";s:10:\"views_view\";s:10:\"base_table\";s:4:\"node\";s:5:\"built\";b:0;s:8:\"executed\";b:0;s:4:\"args\";a:0:{}s:10:\"build_info\";a:0:{}s:8:\"use_ajax\";b:0;s:5:\"pager\";a:5:{s:9:\"use_pager\";b:0;s:14:\"items_per_page\";i:10;s:7:\"element\";i:0;s:6:\"offset\";i:0;s:12:\"current_page\";i:0;}s:17:\"attachment_before\";s:0:\"\";s:16:\"attachment_after\";s:0:\"\";s:12:\"exposed_data\";a:0:{}s:13:\"exposed_input\";a:0:{}s:3:\"vid\";s:0:\"\";s:4:\"name\";s:9:\"frontpage\";s:11:\"description\";s:119:\"Emulates the default Drupal front page; you may set the default home page path to this view to make it your front page.\";s:3:\"tag\";s:7:\"default\";s:8:\"view_php\";s:0:\"\";s:12:\"is_cacheable\";s:1:\"0\";s:7:\"display\";a:3:{s:7:\"default\";O:13:\"views_display\":8:{s

so my issue #3 is: why these errors?

about the installation. this site was originally a d4.x site.
as for the database: i installed schema and saw there were differences but they all seemed trivial

i can provide you with more details if necessary

i attached some screenshots

this site was originally a d4.x site.

My preliminary guess is that a straight upgrade from version 4.x is not possible (as I couldn't find any information whatsoever about it). Have you tried to upgrade to 5.x and then 6.x? I have posted a forum post to see if I'm right or wrong.

Looking in the upgrade documentation, especially this page, makes me pretty confident to say that a straight upgrade is not possible.
Edit: See comment #21. I apologize for not reading carefully.

the problems mentioned in #18 occur in an upgrade from 5.10 to 6.4

I solved this problem on a site by dropping the existing cache_block table and rebuilding it by running these queries:

DROP TABLE IF EXISTS `cache_block`;
CREATE TABLE `cache_block` ( 
  `cid` varchar(255) NOT NULL default '', 
  `data` longblob, 
  `expire` int(11) NOT NULL default '0', 
  `created` int(11) NOT NULL default '0', 
  `headers` text, 
  `serialized` smallint(6) NOT NULL default '0', 
  PRIMARY KEY  (`cid`), 
  KEY `expire` (`expire`) 
) ENGINE=MyISAM DEFAULT CHARSET=utf8; 

I think maybe this problem only comes up if you used the block_cache module for 5.x and didn't uninstall it prior to upgrading?

Looking at the age of the last posts and the fact that greggles provided a possible solution I'm going to assume this issue was resolved and set it to fixed.

Feel free to reopen if you think that is wrong.

- Arie

@NancyDru: Are you experiencing the same bug or a different one when upgrading to 6.4 (from which version?)?