Upgrade to 5.1.0 failed (app not responding)
-
Hi,
I tried to upgrade LS from version 5.0.10 to 5.1.0. Upgrade run normally but the app ended unresponsive (from status "starting" to "not responding"). I rolled back to the previous version and it works again. Any thoughts?
Thank you.
Martin@neki What you can do is to clone the app and then update the clone. Can you paste the logs into https://paste.cloudron.io and link it here? In the meantime, you can disable automatic updates for the current app.
-
@neki What you can do is to clone the app and then update the clone. Can you paste the logs into https://paste.cloudron.io and link it here? In the meantime, you can disable automatic updates for the current app.
-
@girish Thank you for your response. I am a free user running two apps so I can't clone LS (thinking about paid version from September). Pasbin link is https://paste.cloudron.io/jisulihagu.coffeescript
@neki thanks for the logs, this kindof looke like an upstream bug with some value in your database causing trouble in the data migration.
This would be good to have reported upstream at https://forums.limesurvey.org/forum/installation-a-update-issues where the actual bug is somewhere at https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/update/updatedb_helper.php#L5087
I assume they would need some info from you about the dataset you have in your instance, possibly in some private communication channel, since this issue looks data related (maybe a special character or missing encoding for the sql query)
Please let us know the link if you create a forum entry there, so we can track an help out as well.
-
@neki thanks for the logs, this kindof looke like an upstream bug with some value in your database causing trouble in the data migration.
This would be good to have reported upstream at https://forums.limesurvey.org/forum/installation-a-update-issues where the actual bug is somewhere at https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/update/updatedb_helper.php#L5087
I assume they would need some info from you about the dataset you have in your instance, possibly in some private communication channel, since this issue looks data related (maybe a special character or missing encoding for the sql query)
Please let us know the link if you create a forum entry there, so we can track an help out as well.