View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
19385 | Bug reports | ComfortUpdate | public | 2024-01-31 14:43 | 2024-02-01 12:27 |
Reporter | cavo789 | Assigned To | |||
Priority | none | Severity | block | ||
Status | new | Resolution | open | ||
Product Version | 6.4.x | ||||
Summary | 19385: UpdateDB via console fail without showing the issue | ||||
Description | Hi all
In short: I've five running LS v3.x instances on our servers. I've succeed to upgrade from v3.x to v6.2.4 for four instances but not for the last one; the biggest one. I've made a mysqldump, got a 340MB .sql file and copy that file to a new server (self-hosted) where I've LS v6.2.4. I then run There is perhaps something with the db but I can't share it. I've successfully dump it and import it in my new MySQL server (using mysql CLI statements). The crash concern the | ||||
Steps To Reproduce | Dump a working LS v3.x instance, (The same thing for my four first instances was OK, just my last instance, bigger in size, crash) | ||||
Additional Information | Steps to reproduceDidn't know here Expected resultWhen DB issue happen : have the DB error. Actual resultWhen DB issue happen : No DB error | ||||
Tags | No tags attached. | ||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | 6.2.4+230825 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | Edge | ||||
Database type & version | MySQL8.0.32 | ||||
Server OS (if known) | Red Hat Enterprise Linux 8.9 | ||||
Webserver software & version (if known) | Apache | ||||
PHP Version | 8.1.27 | ||||
For info, connecting to the database using |
|
This is another issue here : can you try again ? |
|
Thanks to Denis Chenu, the root cause has been identified. So, for me, the issue is solved but the "bug" is well there. I've posted the solution I've used here : https://forums.limesurvey.org/forum/installation-a-update-issues/145651-php-application-commands-console-php-updatedb-fails#255297 The main problem is thus that update script like https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/update/updates/Update_419.php#L9 is creating a table that is already present in my database. I had multiple issues during my updatedb execution and for each of them, I had to identify which tables were mentionned in the /updates/update/Update_999 script then go to my MySQL console and drop the table (all tables were empty). I've no idea why these tables were already present. The database comes from a LimeSurvey v3; version 359. As a fix, perhaps add a "If table didn't exists then create it" in the multiple updates; if not already done in LS since I'm using LS 6.2.4 right now. Many thanks and bip up Denis. |
|
Concerning your point here above Denis: it's just a web timeout. Running a so long script in a web page ends with a timeout. That's why I need to run updatedb using CLI. |
|
Yes, but we optimize a lot some part, the big part are 400 update, but with 1000 sureys it take less than 2 minutes on my computer. PS : sometime : i do my update in 2 times : 3 to 5 and 5 to 6. |
|
Using CLI upgrade, it already takes minutes before a crash. This is why I don't use web interface anymore. As said earlier, I've more than 13,000 tables in that db. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2024-01-31 14:43 | cavo789 | New Issue | |
2024-01-31 14:47 | cavo789 | Note Added: 79365 | |
2024-01-31 14:47 | cavo789 | Bug heat | 0 => 2 |
2024-01-31 15:20 | DenisChenu | Summary | Php Application/Commands/Console.Php Updatedb Fails => UpdateDB via console fail without showing the issue |
2024-01-31 15:20 | DenisChenu | Additional Information Updated | |
2024-01-31 15:22 | DenisChenu | Note Added: 79370 | |
2024-01-31 15:22 | DenisChenu | Bug heat | 2 => 4 |
2024-02-01 10:58 | cavo789 | Note Added: 79384 | |
2024-02-01 11:01 | cavo789 | Note Added: 79385 | |
2024-02-01 11:59 | DenisChenu | Note Added: 79387 | |
2024-02-01 12:27 | cavo789 | Note Added: 79388 |