View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
20095Bug reportsComfortUpdatepublic2025-05-08 09:122025-05-08 16:15
Reportergreiling Assigned Totibor.pacalat  
PrioritynoneSeverityblock 
Status closedResolutionwon't fix 
Summary20095: DB Update test fails in ComfortUpdate
Description

Since 6.11 -> 6.12 or DB Version 627 -> 628 test run ended with Gateway Timeout and enormous CPU Load - only reboot recovers normal functionality.
If DB changing is provided in Comfort Update (like 6.13.1 -> 6.13.2) it hangs - without DB change act normally.
I have to go the classy way https://www.limesurvey.org/manual/Upgrading_from_a_previous_version/de
After first login in newly updated system it takes a time - and shows up "success db n -> n+1"

A second - smaller - instance on the same server shows no problem

Steps To Reproduce

try to generate a DB like this:

Users: 885
Surveys: 2908
Active surveys: 1748
Deactivated result tables: 251
Active survey participants tables: 185
Deactivated survey participants tables: 176

2873 tables InnoDB utf8mb4_general_ci data size 1 065 252 404 index size 189 578 240

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)LimeSurvey Community Edition Version 6.13.2+250506
I will donate to the project if issue is resolvedNo
Browser
Database type & versionMariaDB: 10.5.28-MariaDB-0+deb11u2
Server OS (if known)debian
Webserver software & version (if known)
PHP VersionPHP Version 8.3.16

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2025-05-08 11:34

developer   ~82606

627 to 628 ?
https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/update/updates/Update_628.php
Just deletion

Even the other are not heavy ? No Survey table update for example ????
greiling

greiling

2025-05-08 11:55

reporter   ~82607

It happens between these two steps Bildschirmfoto 2025-03-12 um 14.13.09 -> Bildschirmfoto 2025-03-12 um 14.22.01
and kills the entire machine. Not heavy: no db update. - Testing in comfort update - or whatever it does at this point.

Bildschirmfoto 2025-03-12 um 14.13.09.png (43,980 bytes)   
Bildschirmfoto 2025-03-12 um 14.13.09.png (43,980 bytes)   
Bildschirmfoto 2025-03-12 um 14.22.01.png (24,130 bytes)   
Bildschirmfoto 2025-03-12 um 14.22.01.png (24,130 bytes)   
tibor.pacalat

tibor.pacalat

2025-05-08 16:15

administrator   ~82612

I spoke with Carsten and his best guess is that the script tries to create the backup and this is where it fails. It is possible that @greiling's database is simply too big. There is a parameter in config-defaults to disable the backup during Comfortupdate.

Issue History

Date Modified Username Field Change
2025-05-08 09:12 greiling New Issue
2025-05-08 11:34 DenisChenu Note Added: 82606
2025-05-08 11:34 DenisChenu Bug heat 0 => 2
2025-05-08 11:55 greiling Note Added: 82607
2025-05-08 11:55 greiling File Added: Bildschirmfoto 2025-03-12 um 14.13.09.png
2025-05-08 11:55 greiling File Added: Bildschirmfoto 2025-03-12 um 14.22.01.png
2025-05-08 11:55 greiling Bug heat 2 => 4
2025-05-08 16:15 tibor.pacalat Note Added: 82612
2025-05-08 16:15 tibor.pacalat Bug heat 4 => 6
2025-05-08 16:15 tibor.pacalat Assigned To => tibor.pacalat
2025-05-08 16:15 tibor.pacalat Status new => closed
2025-05-08 16:15 tibor.pacalat Resolution open => won't fix