View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
15806 | Bug reports | _ Unknown | public | 2020-01-31 16:37 | 2020-03-14 15:46 |
Reporter | adelphi_user | Assigned To | c_schmitz | ||
Priority | high | Severity | partial_block | ||
Status | closed | Resolution | fixed | ||
Product Version | 4.1.0 | ||||
Summary | 15806: Upgrade from 3.21 to 4.1 - upgrade Database error | ||||
Description | Hi, I have just tried to upgrade LimeSurvey to version 4.1. Unfortunately I cannot upgrade the database. I get the following errors: First error: An error occurred during the database update. Error information: Second Error: Ein Fehler trat während des Datenbankupdates auf. Fehlerinformation: See more in my screenshots | ||||
Steps To Reproduce | I have tried to upgrade Limesurvey from version 3.21.4+200108 to 4.1. The upgrade of my database does not work then. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Bug heat | 22 | ||||
Complete LimeSurvey version number (& build) | 3.21.4+200108 to 4.1.0+200128 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | CHrome, Firefox | ||||
Database type & version | mysql Ver 15.1 Distrib 10.1.41-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 | ||||
Server OS (if known) | Debian 9.11 | ||||
Webserver software & version (if known) | Server version: Apache/2.4.25 (Debian) Server | ||||
PHP Version | PHP 7.2.27-1+0~20200123.34+debian9~1.gbp63c0bc | ||||
Can you give us a screenshot of the error you get when debug = 2? |
|
CDbException /srv/www/test/home/www/framework/db/CDbCommand.php(358) 346 {
|
|
Is that what you need? |
|
Yes, thank you. Will have a look. |
|
This will be hard to debug without the complete database. Can you run |
|
Thank you very much. If you need anything else, please let me know. |
|
My only explanation is that the update broke in the middle of an update, which is not supposed to be possible since it uses transaction. Do you have a table called questions_update400 in your database? |
|
Also run this SQL: |
|
So I have the following database table "answers_update400", but not the "questions_update400". Thx |
|
Do you have groups_update400? |
|
olle, imo, transactions will not work here as limesurveys tables are myisam and not innodb |
|
This page might explain the problem: https://dev.mysql.com/doc/refman/8.0/en/implicit-commit.html |
|
"Groups_update400" is not in my database. So what am I supposed to do? |
|
I am inclined to close this issue for the following reason: |
|
Alle Tabellen benutzen "utf8mb4_general_ci". Die Unterschiede sind beim Typ der Datenbank. Dort gibt es die Typen "MyISAM" oder "InnoDB". |
|
All tables use "utf8mb4_general_ci". The differences are in the database type. There are the types "MyISAM" or "InnoDB". |
|
Seems transaction didn't work good on 400 upgrade … with mysql and debug = 2. I see an upgrade result where : lime_labels are not updated (broke during update), but lime_question was updated. Mayvbe we need for this single part : separate in X instcructions (one for each table) 400.1, 400.2 etc … |
|
Hello, we have exactly the same problem here. After the update files have been copied, you can update the DB. Then came the error: An non-recoverable error happened during the update. Error details: regards |
|
Transactions don't work AT ALL when creating new tables in MySQL. See my link above about implicit commit. |
|
Yes, the drop tables commands should happen last in the update. |
|
@CarmIT This is a new error. Do you mind filing a separate bug report for it, please? |
|
ok i will create a Bugreport |
|
Right , sorry :)
It's a quick solution … my oipinion is more : separate 400 upgrade in multiple upgrade is the best solution … If we rename : maybe need to check if exist before starting again 400 ? |
|
Little bit too late now. :| |
|
Too late at the 1st update part … i think mantios have some informlation abouyt this. I kno DBversion must be an integer : but why not 400.1 for question, 400.2 for group , 400.3 for answers 400.4 for label ? |
|
Sounds messy... Would it really add anything? |
|
I make a quick draft pull request … |
|
Open for discussion : https://github.com/LimeSurvey/LimeSurvey/pull/1384 BUT : there are integer between 369 and 400 … |
|
I have this same issue as opening poster, I tried to upgrade to Ver4. stable and it stuck at DB Upgrade, with exact same errors, I have had LimeSurvey for years and years and there is 2 collations types in my ver.3, which may be from old old versions of tables. When I tried updating, it ended up having to be restored, both Site and Database. As said on Github, I can supply my current database which I restored from, if needed for bug tracking. Current (Working) Running LimeSurvey: Version 3.17.1+190408 /Steven |
|
Can you please update to the latest LS3 version and then check your collation again? Thank you. |
|
@explorerdk Can you upload your database dump to this ticket? Mark the message as private if so. |
|
@ollehar Do you want me to Update it first or have the one it errored with ? |
|
@explorerdk The one before the update, so we can run the update and test. |
|
"Databasen has been updated from 356 to version 359." I just updated to 3.22. The Database from above is from LimeSurvey: Version 3.17.1+190408. Ps. @ollehar - can you say when you have retrieved the Database, so I can remove it again. /Expdk |
|
I have marked the message with the database as private, so if it's OK for you, leave it up for now. |
|
@Ollehar, Thanks for that :) I will keep it up, as it is now private. I am now at Version 3.22.2+200204, do you want the DB from here as well ? |
|
No, that's not necessary, I think. |
|
I am closing this issue. I checked using the attached database and had no problems. If you still can reproduce an issue with updates using the latest version please open a new bug report. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2020-01-31 16:37 | adelphi_user | New Issue | |
2020-01-31 16:37 | adelphi_user | File Added: limesurvey-admin-1.png | |
2020-01-31 16:37 | adelphi_user | File Added: limesurvey-admin-2.png | |
2020-01-31 16:37 | adelphi_user | File Added: limesurvey-admin-3.png | |
2020-01-31 16:37 | adelphi_user | File Added: limesurvey-admin-6.png | |
2020-01-31 16:37 | adelphi_user | File Added: limesurvey-admin-5.png | |
2020-01-31 16:37 | adelphi_user | File Added: limesurvey-admin-4.png | |
2020-01-31 16:38 | ollehar | Note Added: 55600 | |
2020-01-31 16:41 | adelphi_user | Note Added: 55601 | |
2020-01-31 16:42 | adelphi_user | Note Added: 55602 | |
2020-01-31 16:42 | ollehar | Assigned To | => ollehar |
2020-01-31 16:42 | ollehar | Status | new => feedback |
2020-02-03 07:55 | CarmIT | Issue Monitored: CarmIT | |
2020-02-03 09:43 | ollehar | Note Added: 55629 | |
2020-02-03 11:07 | ollehar | Note Added: 55632 | |
2020-02-03 11:10 | ollehar | Priority | none => high |
2020-02-03 11:10 | ollehar | Description Updated | |
2020-02-04 11:44 | adelphisurveys | File Added: limesurvey_sql.png | |
2020-02-04 11:44 | adelphisurveys | Note Added: 55693 | |
2020-02-04 13:56 | ollehar | Note Added: 55695 | |
2020-02-04 13:59 | ollehar | Note Added: 55696 | |
2020-02-04 14:55 | adelphisurveys | File Added: limesurvey_dbversion.png | |
2020-02-04 14:55 | adelphisurveys | Note Added: 55698 | |
2020-02-04 16:24 | ollehar | Note Added: 55701 | |
2020-02-04 16:36 | bismark | Note Added: 55702 | |
2020-02-04 16:41 | ollehar | Note Added: 55704 | |
2020-02-04 16:49 | ollehar | Assigned To | ollehar => c_schmitz |
2020-02-04 16:53 | adelphisurveys | Note Added: 55709 | |
2020-02-04 16:58 | c_schmitz | Note Added: 55710 | |
2020-02-05 17:01 | adelphisurveys | File Added: LimeSurvey-DB2.png | |
2020-02-05 17:01 | adelphisurveys | File Added: LimeSurvey-DB.png | |
2020-02-05 17:01 | adelphisurveys | Note Added: 55766 | |
2020-02-05 17:02 | adelphisurveys | Note Added: 55767 | |
2020-02-06 07:56 | DenisChenu | Note Added: 55770 | |
2020-02-06 08:06 | CarmIT | Note Added: 55773 | |
2020-02-06 10:21 | ollehar | Note Added: 55781 | |
2020-02-06 10:22 | ollehar | Note Added: 55782 | |
2020-02-06 10:23 | ollehar | Note Added: 55783 | |
2020-02-06 10:45 | CarmIT | Note Added: 55784 | |
2020-02-06 10:50 | DenisChenu | Note Added: 55785 | |
2020-02-06 10:59 | ollehar | Note Added: 55786 | |
2020-02-06 12:16 | DenisChenu | Note Added: 55789 | |
2020-02-06 12:16 | DenisChenu | Note Edited: 55789 | |
2020-02-07 03:52 | explorerdk | Issue Monitored: explorerdk | |
2020-02-07 10:23 | ollehar | Note Added: 55795 | |
2020-02-07 11:15 | DenisChenu | Note Added: 55796 | |
2020-02-07 11:58 | DenisChenu | Note Added: 55797 | |
2020-02-10 15:02 | explorerdk | Note Added: 55833 | |
2020-02-10 15:04 | ollehar | Note Added: 55834 | |
2020-02-10 15:58 | ollehar | Note Added: 55838 | |
2020-02-10 16:05 | explorerdk | Note Added: 55839 | |
2020-02-10 16:07 | ollehar | Note Added: 55840 | |
2020-02-10 16:31 | explorerdk | File Added: db_fssurv.zip | |
2020-02-10 16:35 | explorerdk | Note Added: 55842 | |
2020-02-10 16:36 | ollehar | Note Added: 55843 | |
2020-02-10 16:39 | explorerdk | Note Added: 55844 | |
2020-02-10 16:40 | ollehar | Note Added: 55845 | |
2020-03-07 00:59 | Keisial | Issue Monitored: Keisial | |
2020-03-14 15:45 | c_schmitz | Note Added: 56539 | |
2020-03-14 15:46 | c_schmitz | File Deleted: db_fssurv.zip | |
2020-03-14 15:46 | c_schmitz | Note Edited: 56539 | |
2020-03-14 15:46 | c_schmitz | Status | feedback => closed |
2020-03-14 15:46 | c_schmitz | Resolution | open => fixed |