Upgrade error #230
Upgrade error #230
Comments
More info. I'm trying to upgrade from 1.0.3 to 2.0.2 |
You can hover your mouse over the X which will provide the database error. Most likely you will have a different database error after a retry than the original. If we can't resolve the current error, you might need to restore your database and try again to see what the first failure was. I'm still surprised to see an upgrade error at all. |
Thanks for the support. But that table haven't any primary key. I've restored the db from backup, but the error is the same. |
I've performed a new installation (2.0.2) and i've seen that: CREATE TABLE But in my db i see: CREATE TABLE skip_id in missing and is not primary key. I don't know if this info can help to solve the problem. |
Thanks for this information. I'm not yet sure why skip_id would not get created. What version of MySQL are you using? |
mysql Ver 14.14 Distrib 5.5.35, for debian-linux-gnu (x86_64) using readline 6.2 I can create that and push "Try again"? Do you think that is a good idea? |
I see there is a problem in the upgrade script in that there are two attempts to drop PRIMARY KEY on that table. Please comment out line 1186 in fm-modules/fmDNS/upgrade.php (inside function upgradefmDNS_130) which looks like this:
Then you should be able to try again. |
Yeah. Thats right! Thanks man! |
Good to hear - adding this fix for 2.0.3 and beyond. |
Hi,
i followed the upgrade instructions, but i've received this error:
Upgrading Core Schema -> GREEN MARK
Upgrading fmDNS Schema -> RED MARK
Database upgrade failed. Please try again.
How can i have more info about the error?
The text was updated successfully, but these errors were encountered: