Recent Topics

1 Aug 10, 2015 01:38    

I try to upgrade from 5.08 to the latest 6.6.2 and the database reorganizing gets stuck with the error

Table 'b2eWald_links__vote' already exists(Errno=1050)

This seems strange, as in the 5.08 version there is a table named like that. Why doesn't it like this table or why does it get stuck?

 Checking files...

Preparing to install /.htaccess in the base folder... Already installed.
Upgrading data in existing b2evolution database...
Loading module: _core/model/__core.install.php
Loading module: collections/model/_collections.install.php
Loading module: files/model/_files.install.php
Loading module: sessions/model/_sessions.install.php
Loading module: messaging/model/_messaging.install.php
Loading module: maintenance/model/_maintenance.install.php

Checking DB schema version... 11110 : OK.
Upgrading comments table... OK.
Convert email addresses to lowercase... OK.
Upgrading blogs table... OK.
Updating general settings... OK.
Upgrading blogs table... OK.
Upgrade table of base domains... OK.
Create table for file links voting...
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!

Table 'b2eWald_links__vote' already exists(Errno=1050)

Your query:

CREATE TABLE b2eWald_links__vote (

        lvot_link_ID       int(11) UNSIGNED NOT NULL,

        lvot_user_ID       int(11) UNSIGNED NOT NULL,

        lvot_like          tinyint(1),

        lvot_inappropriate tinyint(1),

        lvot_spam          tinyint(1),

        primary key (lvot_link_ID, lvot_user_ID)

      ) ENGINE = innodb

2 Aug 10, 2015 16:33

Looks like a bug. We'll check it and fix in the next couple of days.

3 Aug 12, 2015 15:19

Actually it seems there is no bug. The table links__vote is not part of v 5.0.8.

Did you try another upgrade before this one that you may have aborted. Maybe you have restored a backup of a 5.0.8 DB in a mysql DB that was not empty, and you have some tables that should not be there.

(In this case, you should manually clean up your DB so it looks like a 5.0.8 DB before trying to upgrade.)

4 Aug 12, 2015 16:20

I already thought of the option you mention, unfortunately i can not verify 100 percent, as things are not well documented and we are several people working on this.

Where would i find a documentation about what is part of a 5.0.8 DB and what does not belong to it? Is there a table list available somewhere?

And sorry for causing this trouble ...

5 Aug 12, 2015 20:09

@ramadama I'm afraid there is no info in the manual regarding database schemas by version. However, please check that attached file, it is a DB dump of a fresh 5.0.8 install. Maybe it could help you.

Please see comment below.

7 Aug 13, 2015 01:18

Or you install a fresh copy of 5.0.8 in a separate DB and then compare both databases.

8 Aug 13, 2015 01:21

thanks a lot @mgsolipa, this helped. After deleting some of the tables the db-upgrade got beyond the exit point of before. However the process ended with an 'Upgrade failed!' message.
The three last lines have been:

ALTER TABLE b2eWald_files CHANGE COLUMN file_desc file_desc text

ALTER TABLE b2eWald_track__goalhit CHANGE COLUMN ghit_params ghit_params TEXT default NULL

ALTER TABLE b2eWald_messaging__message CHANGE COLUMN msg_text msg_text text

and I don't know, if this is it or if some more should have come?

I can log in now, but am confused having seen the 'Upgrade failed!' notification

What happens, if in this situation I press the 'Upgrade database!' button, offered there just above the 'Upgrade failed!'-message? Probably will do no harm? Should I do it?

9 Aug 16, 2015 22:05

@ramadama 1) what update method are using? 2) did you get any other error message during the upgrade process? 3) Does your b2evolution keep offering the option to upgrade the database? Can you do it and take a screenshot of that?, maybe seeing what you mentioned here:

What happens, if in this situation I press the 'Upgrade database!' button, offered there just above the 'Upgrade failed!'-message?

would made easier to identify where is your site stucked.

You can also check the record db_version in the table T_settings of your database, its value for version 6.6.2 is 11480

10 Aug 24, 2015 20:58

@ramadama wrote earlier:

What happens, if in this situation I press the 'Upgrade database!' button, offered there just above the 'Upgrade failed!'-message? Probably will do no harm? Should I do it?

Yes you should. That is b2evolution trying to help you repair your DB so it matches 100% of what is expected.

PS: I would love a full screenshot of that place where it's not clear you should press the button so we can work on better wording.


Form is loading...