Recent Topics
  1. b2evolution CMS Support Forums
  2. b2evolution Support
  3. General Support
  4. Can't upgrade from 5.2.2 to 6.5.0 - myql error

Can't upgrade from 5.2.2 to 6.5.0 - myql error

1 Jul 02, 2015 17:41    

I get this error and I am stuck:

An unexpected error has occurred!

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

Go back to home page
Additional information about this error:

MySQL error!

Incorrect key file for table 'evo_items__item'; try to repair it(Errno=1034)

Your query:

ALTER TABLE evo_items__item

CHANGE post_ptyp_ID post_ityp_ID int(10) unsigned NOT NULL DEFAULT 1,

DROP INDEX post_ptyp_ID ,

ADD INDEX post_ityp_ID ( post_ityp_ID )

and

Database schema is not up to date!

You have schema version «11350», but we would need «11440».

and this If I use the Normalizing DB option from the installer:

Additional information about this error:

MySQL error!

Unknown column 'ityp_use_title' in 'evo_items__type'(Errno=1054)

Your query:

ALTER TABLE `evo_items__type`

MODIFY ityp_use_title ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'required',

MODIFY ityp_use_url ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_text ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_excerpt ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_title_tag ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_meta_desc ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_meta_keywds ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_tags ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional',

MODIFY ityp_use_country ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'never',

MODIFY ityp_use_region ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'never',

MODIFY ityp_use_sub_region ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'never',

MODIFY ityp_use_city ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'never',

MODIFY ityp_use_coordinates ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'never',

MODIFY ityp_use_comment_expiration ENUM( 'required', 'optional', 'never' ) COLLATE ascii_general_ci DEFAULT 'optional'

I use my own server (linux) with MariaDB 10.0.20

Back to top

2 Jul 02, 2015 20:48

I had a similar problem upgrading to 6.4.3 I hope you make regular copies of your database.

> "Prompted to update database as some characters were not UTF-8 but it failed so decided to upgrade anyway which worked."
>http://rogerlovejoy.net/blog/b2evo.php/upgrade-o-6-4-3

In the end I installed the new version with a new blank database and then imported the data from my old one. It took me four attempts over many hours.which I then had to upgrade to UTF-8 even though it already was.

Please don't follow my example I'm just detailing what I remember from my problem.
Hopefully some proper boffin will give proper advice

Back to top

3 Jul 03, 2015 01:19

@zebulon8 the key information in your error message is:

> Incorrect key file for table 'evo_items__item'; try to repair it(Errno=1034)

This means your MySQL DB is broken. This must be fixed outside of the scope of b2evolution. For example with PhpMyAdmin which your webhost probably offers in your control panel.

Back to top

4 Jul 06, 2015 12:55

Thanks

Reverted back to 5.2.2 since I could not do anything to repair the db. (there where no error(s) reported anyway when using phpmyadmin). Reverting with the backup db was no problem, Using the db backup to continue with 6.5.0 was still the same problem.

I might wait for the next update to upgrade to. Can't figure out what and where I did something wrong (if at all).

Back to top

5 Jul 06, 2015 22:47

It has nothing to do with b2evolution 6.5. Your DB has a problem and you need to repair it before attempting upgrade. You can do that using the check/repair tools in PhpMyAdmin, even if PhpMyAdmin doesn't report errors .

If you don't repair, it's only a matter of time before you see errors in PhpMySQL too and in b2evo 5.2.2 too.

Again:

MySQL error!

Incorrect key file for table 'evo_items__item'; try to repair it(Errno=1034)

This is a serious internal MySQL error. This cannot be created by any PHP script (including the b2evolution upgrade)

Back to top

6 Jul 07, 2015 00:45

Note though: still having the same error after a restore is weird. Did you completely delete your DB before restoring?

Back to top

7 Jul 07, 2015 02:01

First I tried to repair the db with phpmyadmin. Result message was that repair was successful; no error when using the check db option from phpmyadmin.
Using again the b2evo 6.5 installer / db check it was still the same result (error like in first post)

Than I tried to revert to 5.2.2 and also a error that the db was not correct.
So I tried again to use 6.5 with my conf and with a new db created - imported the backup data and tried again a 6.5 upgrade - same thing with the error like above.

At last I deleted everyting again; put the 5.2.2 with conf back into place, created a new db, imported the backup data into the db and 5.2.2 was again up and running with no problems.

That's it so far.

Linux webserver with php 5.4.20 and MariaDB 10.0.20

Back to top

8 Jul 08, 2015 17:16

I found out at the last restart of the webserver that de file system had some errors - which are now fixed.

I will give the update another try and will let you know how that worked out.

Kind regards.

Back to top

9 Sep 19, 2015 18:39

Hi,
I had the same problem yesterday, Sepember 19, 2015 on the upgrade and got Error 1034.

After trying things I gave up.

Then later ..since I have 3 hosting sites with some B2Evolution blogs ....
I downloaded the database from Hosting site 1 to my computer and then uploaded to Hosting site 2 ..renames the database and tried the upgrade on site 2. Same Error 1034.

Then i tried PHPadmin database tool and copied stuff ..still no luck.

Then after sleeping this ..... I awoke with a bright idea.
Why would 2 different hosting sites ..create the same error 1034 ..involving database engine.

So I looked at Cpanel ...and both sites use MySql version 10.0.21 maria DB.

Then I wondered . .what does my 3rd Hosting site use?
They had 5.5.4.5 Maria DB

So I uploaded the database to hosting site 3 ...and renamed it ..and attached to the Be2 evolution region i created for this test installation ...........and It worked. .... the upgrade worked ..the blog post appeared in good order.

FIne .... so I am leaving that in position.

Since, I didn't want to loose any VIEWERS on my original hosting site 1 ..... I wanted to get that working.
I took the good database from Hosting site 3 ...and downloaded it to my computer ..... uploaded to hosting site 1 ..renamed the file and activated database USER ID (very important) ...and now hosting site is a working, happy site.

So, I don't know who fixes these database engines ..... you might tell them ..something is wrong with version 10.

Back to top


Form is loading...