View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
15843 | Bug reports | Installation | public | 2020-02-11 13:57 | 2020-04-14 12:53 |
Reporter | reinhards | Assigned To | c_schmitz | ||
Priority | normal | Severity | partial_block | ||
Status | closed | Resolution | fixed | ||
Product Version | 4.1.2 | ||||
Fixed in Version | 4.1.17 | ||||
Summary | 15843: unable to run db migration via command line | ||||
Description | probably Bug 13744 re-appeared I was upgrading vom Version 2.72 to Version 4.1.2 and ran into this: php application/commands/console.php updatedb | ||||
Additional Information | fixed it by adding the patch from Bug 13744 to the file UpdateDbCommand.php | ||||
Tags | No tags attached. | ||||
Bug heat | 8 | ||||
Complete LimeSurvey version number (& build) | 4.1.2+200210 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | mariadb-5.5.64-1.el7 | ||||
Server OS (if known) | CentOS 7.7 | ||||
Webserver software & version (if known) | |||||
PHP Version | 7.1.33 | ||||
I was about to report the same thing. Updating from 3.22 branch to 4.1.8 Just replacing the files doesn't work (complains about missing columns, etc.) Following the instructions https://manual.limesurvey.org/Upgrading_from_a_previous_version $ php application/commands/console.php updatedb I need to actually look at ./application/commands/UpdateDbCommand.php
which is completely unhelpful. I need to go into (./application/helpers/update/updatedb_helper.php (and add a few debug prints in order to find out that my current version is previous to the critical database version update 400. Looking at the code of db_upgrade_all, it seems that on error at the update it is expected to show the error message via Yii::app()->user->setFlash. My guess is that it is not doing anything when run from console. A second issue would be why it wasn't updated (a misconfiguration in my environment, perhaps) and why it ended up in an inconsistent state, with the old DBVersion but post-400 tables (I suspect that due to mysql forcing a commit after a DDL statement, and thus the final rollback actually not being helpful), but that's likely to be 15806. |
|
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=29818 |
|
Fixed in Release 4.1.17+200414 |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2020-02-11 13:57 | reinhards | New Issue | |
2020-03-07 01:01 | Keisial | Issue Monitored: Keisial | |
2020-03-07 01:02 | Keisial | Note Added: 56358 | |
2020-03-18 12:55 | cdorin | Assigned To | => cdorin |
2020-03-18 12:55 | cdorin | Status | new => confirmed |
2020-03-18 12:55 | cdorin | Priority | none => normal |
2020-04-08 13:14 | c_schmitz | Changeset attached | => LimeSurvey master 6998921b |
2020-04-08 13:14 | c_schmitz | Note Added: 57030 | |
2020-04-08 13:14 | c_schmitz | Assigned To | cdorin => c_schmitz |
2020-04-08 13:14 | c_schmitz | Resolution | open => fixed |
2020-04-08 13:15 | c_schmitz | Status | confirmed => resolved |
2020-04-08 13:15 | c_schmitz | Fixed in Version | => 4.1.17 |
2020-04-14 12:53 | lime_release_bot | Note Added: 57117 | |
2020-04-14 12:53 | lime_release_bot | Status | resolved => closed |
2021-08-02 17:18 | guest | Bug heat | 6 => 8 |