Comparing the database of

http://www.comiclist.com

to my test blog, which is

http://www.comiclist.com/btetwotest/

it looks like part of the problem is, the first blog does not have "evo_items__item", it has "evo_posts."

And here is how my main, comiclist.com/ blog, looks right now:

Table Records Type Size Comments
evo_antispam 5,187 MyISAM 359.4 KiB
Creation: Dec 31, 2007 at 01:01 PM
Last update: Feb 09, 2008 at 12:10 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_basedomains 2,212 MyISAM 177.9 KiB
Creation: Dec 31, 2007 at 01:01 PM
Last update: Mar 27, 2008 at 06:52 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_bloggroups 1 MyISAM 2.0 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_blogs 10 MyISAM 9.6 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_blogusers 13 MyISAM 2.2 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_categories 226 MyISAM 24.2 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM
Last check: Mar 28, 2008 at 07:46 AM

evo_coll_settings 50 MyISAM 5.9 KiB
Creation: Dec 31, 2007 at 01:01 PM
Last update: Mar 28, 2008 at 07:46 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_comments 67 MyISAM 29.0 KiB
Creation: Mar 28, 2008 at 08:38 AM
Last update: Mar 28, 2008 at 08:38 AM

evo_cron__log 2 MyISAM 4.2 KiB
Creation: Dec 31, 2007 at 01:01 PM
Last update: Jan 02, 2008 at 10:09 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_cron__task 4 MyISAM 2.3 KiB
Creation: Dec 31, 2007 at 01:01 PM
Last update: Jan 02, 2008 at 10:09 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_files 513 MyISAM 44.6 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_filetypes 12 MyISAM 2.7 KiB
Creation: Dec 31, 2007 at 01:01 PM
Last update: Mar 28, 2008 at 07:46 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_groups 4 MyISAM 2.1 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_hitlog 2,815,635 MyISAM 435.2 MiB
Creation: Mar 28, 2008 at 08:39 AM
Last update: Mar 28, 2008 at 08:39 AM
Last check: Mar 28, 2008 at 08:40 AM

evo_item__prerendering 3,452 MyISAM 27.0 MiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Mar 27, 2008 at 04:49 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_links 0 MyISAM 1.0 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Jan 02, 2008 at 10:10 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_locales 43 MyISAM 4.4 KiB saves available locales
Creation: Dec 31, 2007 at 01:03 PM
Last update: Jan 02, 2008 at 10:10 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_pluginevents 82 MyISAM 7.6 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Feb 10, 2008 at 08:57 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_plugins 27 MyISAM 5.5 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Feb 13, 2008 at 02:33 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_pluginsettings 24 MyISAM 29.4 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Mar 28, 2008 at 07:31 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_pluginusersettings 6 MyISAM 2.2 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Mar 26, 2008 at 05:58 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_plugin_acrolink_43_Keywords 45 MyISAM 3.6 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Jan 07, 2008 at 03:29 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_plugin_captcha_img_36_data 719 MyISAM 620.9 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Mar 28, 2008 at 07:33 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_plugin_captcha_img_36_trackbacks_wl 0 MyISAM 2.4 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Mar 27, 2008 at 08:44 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_plugin_gallery 2,607 MyISAM 895.4 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Jan 16, 2008 at 04:38 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_postcats 5,020 MyISAM 211.1 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Mar 27, 2008 at 04:43 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_posts 2,829 MyISAM 21.5 MiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM
Last check: Mar 28, 2008 at 07:46 AM

evo_poststatuses 0 MyISAM 1.0 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Jan 02, 2008 at 10:10 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_posttypes 3 MyISAM 2.1 KiB
Creation: Dec 31, 2007 at 01:03 PM
Last update: Jan 02, 2008 at 10:10 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_sessions 2,897,023 MyISAM 220.4 MiB
Creation: Mar 28, 2008 at 08:38 AM
Last update: Mar 28, 2008 at 08:38 AM

evo_settings 44 MyISAM 5.3 KiB
Creation: Dec 31, 2007 at 01:04 PM
Last update: Mar 28, 2008 at 07:46 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_skins__container 32 MyISAM 2.6 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_skins__skin 10 MyISAM 4.3 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM

evo_subscriptions 18 MyISAM 2.2 KiB
Creation: Dec 31, 2007 at 01:04 PM
Last update: Jan 02, 2008 at 10:10 PM
Last check: Jan 02, 2008 at 10:11 PM

evo_useragents 33,716 MyISAM 3.8 MiB
Creation: Dec 31, 2007 at 01:04 PM
Last update: Mar 28, 2008 at 07:28 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_users 30 MyISAM 10.8 KiB
Creation: Dec 31, 2007 at 01:04 PM
Last update: Feb 28, 2008 at 08:57 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_usersettings 33 MyISAM 3.0 KiB
Creation: Dec 31, 2007 at 01:04 PM
Last update: Mar 28, 2008 at 07:46 AM
Last check: Jan 02, 2008 at 10:11 PM

evo_widget 162 MyISAM 17.9 KiB
Creation: Mar 28, 2008 at 07:46 AM
Last update: Mar 28, 2008 at 07:46 AM
38 table(s) 5,769,861 -- 710.3 MiB

Sounds like you're still running 1.9.whatever and testing upgrading it? If so can you "restore" your test installation to match your current 1.9 installation, then try upgrading it to 1.10.2 (or 1.10.3 but I think there is no database change there). The idea being incremental SUCCESSFUL steps up instead of making the leap all the way across.

IF you get 1.10.2/3 running, I would try skipping up to 230. If that works great because 241 isn't too far away. If not then - again - go back to 1.10.2/3 and see about each tiny step up the ladder.

Hope it helps.

Oh and keep an eye on the date stamps on each release at http://b2evolution.net/downloads/index.php because that would give an idea if any step is worth stopping at. Like for example 200 lasted ten days before 201 came out, so I wouldn't even bother with 200 as an incremental step - if required.

Since I seem to be caught in between 1.9 and 2.4, what now? I've backed up the database as it is now, but unfortunately, I did not before I attempted the upgrade.

And, to be honest, I believe I was using 1.10.2, not 1.9. I never did go to 1.10.3.

Okay that sucks, but it proves a theory of mine: upgrading will fail if you don't have a backup, but will work without issue if you do.

Hey does your host do a daily backup of databases? That'd get you back to whatever it was before your upgrade efforts, assuming you have a copy of the files you used back then.

Tell ya what: I have a 241 installation that I play with a lot. I'll do the "reset the database" thing then snag out all the details of all the tables. That will give you a comparison point that hopefully can pin down a detail to focus on.

And I'll see what 9409 translates to in the upgrader portion of the installer. Hopefully between the two we can take the smallest possible action required to get 'er done.

	if( $old_db_version < 9410 )
	{
 		echo 'Updating columns... ';
		$DB->query( "ALTER TABLE T_comments CHANGE COLUMN comment_status comment_status ENUM('published','deprecated','protected','private','draft','redirected') DEFAULT 'published' NOT NULL" );

		$DB->query( "ALTER TABLE T_sessions CHANGE COLUMN sess_data sess_data MEDIUMBLOB DEFAULT NULL" );

		$DB->query( "ALTER TABLE T_hitlog CHANGE COLUMN hit_referer_type hit_referer_type ENUM('search','blacklist','spam','referer','direct','self','admin') NOT NULL" );

		echo "OK.<br />\n";

		set_upgrade_checkpoint( '9410' );
	}

That's where you're stuck, so let's see what we can figure out inside those three little steps... Do me a favor: use phpmyadmin to EXPORT your evo_comments and evo_hitlog and evo_sessions table, and uncheck the box for "Data". You can then compare yours to this one:

-- phpMyAdmin SQL Dump
-- version 2.11.5
-- http://www.phpmyadmin.net
--
-- Host: localhost
-- Generation Time: Mar 28, 2008 at 09:02 AM
-- Server version: 5.0.45
-- PHP Version: 5.2.3

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";

--
-- Database: `removed_by_me_just_because`
--

-- --------------------------------------------------------

--
-- Table structure for table `evo_comments`
--

CREATE TABLE IF NOT EXISTS `evo_comments` (
`comment_ID` int(11) unsigned NOT NULL auto_increment,
`comment_post_ID` int(11) unsigned NOT NULL default '0',
`comment_type` enum('comment','linkback','trackback','pingback') NOT NULL default 'comment',
`comment_status` enum('published','deprecated','protected','private','draft','redirected') NOT NULL default 'published',
`comment_author_ID` int(10) unsigned default NULL,
`comment_author` varchar(100) default NULL,
`comment_author_email` varchar(255) default NULL,
`comment_author_url` varchar(255) default NULL,
`comment_author_IP` varchar(23) NOT NULL default '',
`comment_date` datetime NOT NULL default '2000-01-01 00:00:00',
`comment_content` text NOT NULL,
`comment_rating` tinyint(1) default NULL,
`comment_featured` tinyint(1) NOT NULL default '0',
`comment_nofollow` tinyint(1) NOT NULL default '1',
`comment_karma` int(11) NOT NULL default '0',
`comment_spam_karma` tinyint(4) default NULL,
`comment_allow_msgform` tinyint(4) NOT NULL default '0',
PRIMARY KEY (`comment_ID`),
KEY `comment_post_ID` (`comment_post_ID`),
KEY `comment_date` (`comment_date`),
KEY `comment_type` (`comment_type`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

-- --------------------------------------------------------

--
-- Table structure for table `evo_hitlog`
--

CREATE TABLE IF NOT EXISTS `evo_hitlog` (
`hit_ID` int(11) NOT NULL auto_increment,
`hit_sess_ID` int(10) unsigned default NULL,
`hit_datetime` datetime NOT NULL,
`hit_uri` varchar(250) default NULL,
`hit_referer_type` enum('search','blacklist','spam','referer','direct','self','admin') NOT NULL,
`hit_referer` varchar(250) default NULL,
`hit_referer_dom_ID` int(10) unsigned default NULL,
`hit_blog_ID` int(11) unsigned default NULL,
`hit_remote_addr` varchar(40) default NULL,
`hit_agnt_ID` int(10) unsigned default NULL,
PRIMARY KEY (`hit_ID`),
KEY `hit_agnt_ID` (`hit_agnt_ID`),
KEY `hit_blog_ID` (`hit_blog_ID`),
KEY `hit_uri` (`hit_uri`),
KEY `hit_referer_dom_ID` (`hit_referer_dom_ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `evo_sessions`
--

CREATE TABLE IF NOT EXISTS `evo_sessions` (
`sess_ID` int(11) unsigned NOT NULL auto_increment,
`sess_key` char(32) default NULL,
`sess_lastseen` datetime NOT NULL,
`sess_ipaddress` varchar(15) NOT NULL default '',
`sess_user_ID` int(10) default NULL,
`sess_data` mediumblob,
PRIMARY KEY (`sess_ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

The idea here is to see if ANY of the three steps within that little code block got accomplished. Ultimately once you know which exact bit isn't happening, we can work up a way to accomplish the remaining bits.

Oh and if you don't mind, EMPTY your hitlogs table. Heck EMPTY your sessions table while you're at it. Nothing in there is worth losing the whole blog over eh?

-- phpMyAdmin SQL Dump
-- version 2.11.4
-- http://www.phpmyadmin.net
--
-- Host: localhost
-- Generation Time: Mar 28, 2008 at 10:08 AM
-- Server version: 5.0.45
-- PHP Version: 5.2.3

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";

--
-- Database: `removed_by_me_just_because`
--

-- --------------------------------------------------------

--
-- Table structure for table `evo_comments`
--

CREATE TABLE `evo_comments` (
`comment_ID` int(11) unsigned NOT NULL auto_increment,
`comment_post_ID` int(11) unsigned NOT NULL default '0',
`comment_type` enum('comment','linkback','trackback','pingback') NOT NULL default 'comment',
`comment_status` enum('published','deprecated','protected','private','draft','redirected') NOT NULL default 'published',
`comment_author_ID` int(10) unsigned default NULL,
`comment_author` varchar(100) default NULL,
`comment_author_email` varchar(255) default NULL,
`comment_author_url` varchar(255) default NULL,
`comment_author_IP` varchar(23) NOT NULL default '',
`comment_date` datetime NOT NULL default '0000-00-00 00:00:00',
`comment_content` text NOT NULL,
`comment_karma` int(11) NOT NULL default '0',
`comment_spam_karma` tinyint(4) default NULL,
`comment_allow_msgform` tinyint(4) NOT NULL default '0',
PRIMARY KEY (`comment_ID`),
KEY `comment_post_ID` (`comment_post_ID`),
KEY `comment_date` (`comment_date`),
KEY `comment_type` (`comment_type`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=7217 ;

-- --------------------------------------------------------

--
-- Table structure for table `evo_hitlog`
--

CREATE TABLE `evo_hitlog` (
`hit_ID` int(11) NOT NULL auto_increment,
`hit_sess_ID` int(10) unsigned default NULL,
`hit_datetime` datetime NOT NULL default '0000-00-00 00:00:00',
`hit_uri` varchar(250) default NULL,
`hit_referer_type` enum('search','blacklist','spam','referer','direct','self','admin') NOT NULL,
`hit_referer` varchar(250) default NULL,
`hit_referer_dom_ID` int(10) unsigned default NULL,
`hit_blog_ID` int(11) unsigned default NULL,
`hit_remote_addr` varchar(40) default NULL,
`hit_agnt_ID` int(10) unsigned default NULL,
PRIMARY KEY (`hit_ID`),
KEY `hit_blog_ID` (`hit_blog_ID`),
KEY `hit_agnt_ID` (`hit_agnt_ID`),
KEY `hit_uri` (`hit_uri`),
KEY `hit_referer_dom_ID` (`hit_referer_dom_ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=6465492 ;

-- --------------------------------------------------------

--
-- Table structure for table `evo_sessions`
--

CREATE TABLE `evo_sessions` (
`sess_ID` int(11) unsigned NOT NULL auto_increment,
`sess_key` varchar(32) default NULL,
`sess_lastseen` datetime NOT NULL default '0000-00-00 00:00:00',
`sess_ipaddress` varchar(15) NOT NULL default '',
`sess_user_ID` int(10) default NULL,
`sess_data` mediumblob,
PRIMARY KEY (`sess_ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=6391316 ;

Or PM me some login credentials that'll let me get my keyboard on your cpanel. I'm bored is the thing, and haven't completely ruined anyone's day by totally trashing their server yet today ;)

Okay that's weird but cool. Looks like both comments and hitlog have the desired changes, but sessions isn't quite right.

Via phpmyadmin see about editing the sess_data field in the evo_sessions table to have DEFAULT NULL. It'll be a selector that says either "null" or "not null" so you select "null" and don't put anything in the field for "default value".

And empty that table! It's HUGE and the only price you'll pay is probably have to log in again. Hitlog too, even though most of us like to see our stats. Even if you're making money off it somehow, EMPTY it because you're getting no traffic until we get 'er runnin' again.

We might also have to manually craft up the SQL statement equal to those three commands, then manually up-tick your upgrade checkpoint to 9410. Dunno which will be the best course of action, but to me the minimum interference model is the ideal model.

Done, I believe, and thank you very much.

Cool. I'm in. I'll play for a while and get back to you here.

EDIT: hey you got the fancy cpanel. I sorta like it :)

Okay I got a little bit further. Currently jacked up at 9412 due to

Checking DB schema version... 9412 : OK.
Renaming tables...
An unexpected error has occured!

If this error persits, please report it to the administrator.

Go back to home page
Additional information about this error:

MySQL error!

Table 'evo_items__prerendering' already exists(Errno=1050)

Your query:

RENAME TABLE evo_item__prerendering TO evo_items__prerendering,
evo_poststatuses TO evo_items__status,
evo_posttypes TO evo_items__type,
evo_posts TO evo_items__item

Not a show stopper of course. Just info for when this is resolved and the next person with huge tables has issues in this area.

BTW I emptied your hitlog table and deleted sessions older than 3/21 of this year. That got rid of ~7 million entries in that table.

EDIT: doing a backup before I get any deeper into it. Seems to be taking quite some time to download ... Must be like a million gigabytes or something ... either that or I need to upgrade my dialup connection ;)

EdB wrote:

Not a show stopper of course. Just info for when this is resolved and the next person with huge tables has issues in this area.

BTW I emptied your hitlog table and deleted sessions older than 3/21 of this year. That got rid of ~7 million entries in that table.

Please tell me the actual posts are still there... 8|

cslepage wrote:

EdB wrote:

Not a show stopper of course. Just info for when this is resolved and the next person with huge tables has issues in this area.

BTW I emptied your hitlog table and deleted sessions older than 3/21 of this year. That got rid of ~7 million entries in that table.

Please tell me the actual posts are still there... 8|

Absolutely still there. Er... assuming they were there before I started :lol:

Yeah for sure. That's partially why I'm backing up right now before the next interaction with your database. I'm not sure if I want to delete the tables it found as already there, or advance the checkpoint and let it move on. Problem with deleting is that the old tables have to (a) be there and (b) have the proper contents. Problem with advancing is that I don't know when it will jettison the old tables and don't want to leave them laying about if they're not needed.

STILL downloading the backup... BTW doing a backup will chew up a bunch of time going forward because I won't take another step without another backup. Don't care if I make 2 or 5 or 12 to get 'er done yah? Because remember rule #1: without a backup it'll fail.

Oh, you should know as you are sifting through my mess, I made a copy of "evo_posts" named "evo_items__item" hoping that would fix things. Obviously it did not. You can delete or clear "evo_items__tag" as well, as clearly i haven't had a chance to make any tags this morning. :)

Okay cool. Good info to have. Currently backing up both sets of tables it is stuck trying to rename to see if in fact they are identical contents. WinMerge will tell me that yah? If the new tables are in fact copies of the old ones then I'll delete the old ones and advance the checkpoint. NO wait: delete the new tables and allow the installer to do it's thing.

I will also dig on the tags table because it is next in the upgrader procedure.

Okay both backups are done, so a few minutes to compare them and we'll be on our way.

I feel like we are moving from a crippling disease that, even after recovery, leaves one permanently hobbled, to a broken bone, that ultimately heals and leaves one wiser and stronger.

It seems like someone is trying to upgrade for you. Half way through attempting to restore your posts they all disappeared. I changed a filename to stop that from happening again.

Back to square one I'm afraid.

EDIT: which pretty much is my fault. I should have hidden the appropriate file at the beginning of this process. But still it pisses me off >:-<

EdB wrote:

It seems like someone is trying to upgrade for you. Half way through attempting to restore your posts they all disappeared. I changed a filename to stop that from happening again.

Back to square one I'm afraid.

EDIT: which pretty much is my fault. I should have hidden the appropriate file at the beginning of this process. But still it pisses me off >:-<

Yikes!

Are they still restorable?

Actually, all seems quite well at this time. Like, it's done. Except sit down before you take a peek at your web because ... well ... okay it's a 2.* thing: everything looks like evopress.

Skins got totally different ways of being now, so all upgrades have to be switched to a skin that is compatible with the new way of doing things.

http://www.comiclist.com/ is, at the very least, running.

I was very much concerned with your post statuses. If you had draft or deprecated or private posts in your installation do try to find them ASAP and see if they are still that way.

Oh and anything that was posted in something other than blog #1 will not be seen in blog #1 anymore. Another change is that you have to tell it what blogs you want aggregated into which blog.

And I don't know what happened to your comments. I assume there have been comments yah?

Yes, not a lot of comments, but there were some.

Is it safe to change things via the administration panel?

Yes, but certainly please do a backup first. I have a backup of when I started playing, so you should get a database backup when you start playing ;)

BTW I'm out of your cpanel and see no need to go back in. PMs will be destroyed in a moment or two.

Looks the links are gone too?

As in "linkblog links"? If so you have to install the linkblog widget.

Blog settings, pick a blog, widgets, identify a container - probably sidebar, click install new on the right, find linkblog widget, click it, select the blog you want to use as your linkblog, and then position it in your sidebar container.

TOTALLY different way of doing things :)

Pretty much say goodbye to hacking files to move stuff around :D

Ah, I see the linkblog now. I have so many blogs, there's a drop down box. Didn't have that in my "test blog", as I only had a few blogs there.

If all I lost was the comments, I can live with that. Ed, you are spectacular. I'd like to mention your assistance on my website. What's the best URL to use when referencing you? And can you post or PM me your email address?

http://wonderwinds.com works for me. I'll PM you an email addy, but if you post it somewhere I'll find where you live, hunt you down, and wag a finger at you while stomping my foot in anger. ;)

Hey that was amazingly quick on the skins work. You've been planning this eh? sam2kb is pretty good at that stuff, but I'd change the footer a bit ...

I've been planning the move using this blog as a testing ground:

http://www.comiclist.com/b2etwotest/

Of course, I didn't think to back up my database in case the actual upgrade didn't work.

What would you do the footer?

i am sorry i didnt read all of the thread, but did you import from the previous backup anything after upgrading ?

The bottom line on this "upgrade gone wrong" is that two MASSIVE files that needed something done were, apparently, too much for either the upgrader or the server to handle.

I forget now ... somewhere around upgrade checkpoint 9412 there is a three line step that affects hitlog and sessions and ... something else. Given that hitlog and sessions can easily be the biggest tables in there this is sort of asking for a bottle neck.

Again I already forget, but the size of hitlog made me think "yeah that's the problem" until I saw the size of sessions. 7 MILLION rows in the table. WOW! I did an EMPTY to the hitlog table, and deleted anything in sessions with a lastseen date of "prior to 3/23/08" - which still left the table with something like 93,000 rows.

After that it was cleaning up some tidbits that I don't really know how it happened but it did. For example the step after dealing with these three tables involves renaming 4 tables. Both old and new names existed and were virtually identical. So of course that became a problem - but the set_upgrade_checkpoint() after the three table deal and before the four table rename never happened. Weird, but lesson learned:

EMPTY the hitlog and sessions table BEFORE upgrading. Probably could empty basedomains and useragents tables as well, but since they didn't cause a problem it's not a focus.

When dealing with the database MySQL has a max proces time. It simply stops half way the job. Problems arise if you try to redo the job. Now other errors take place, like the script trying to CREATE tables that already exist.
If you haven't got a [url=http://forums.b2evolution.net/viewtopic.php?t=14421]backup[/url] you are in serious troubles (but it still can be mended).

Yes, 7 million rows will be the cause for MySQL to time out. So the advise from EdB is very valuable: decrease the database before you process it. For the hitlogs, there is a link in the Dashboard.

Thanks EdB for your story.

Good luck