View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
13991Bug reportsOtherpublic2018-08-22 15:202021-03-12 11:04
Reportergslines Assigned ToLouisGac 
PrioritynoneSeveritypartial_block 
Status closedResolutionno change required 
Product Version3.13.x 
Summary13991: Data integrity check broken on LS instance with a lot of surveys
Description

After upgrading from 2.73 to 3.x (currently at 3.14.5), the "Check data integrity" option doesn't work anymore in our Limesurvey installation. This is a rather big instance, with more than 3800 surveys. When clicking on "Check data integrity", the spinning wheel goes on for a while and the results page never comes up, finishing with a blank screen and nothing logged on the browser console nor the LS log file. It worked fine when we were running 2.73, with the same amount of surveys.

Increasing the php timeout limit doesn't make a difference.

I then decided to set debug to 2 in LS's config.php, hoping to get more feedback about the problem, and after that change, the data integrity check ran and generated the results page as expected. I was also able to delete all the old tables reported, with no issues.

After that, I set debug back to 0 and tried running the integrity check again. And again the problem showed up: no results (empty page) and no errors in the browser console nor the system logs.

Steps To Reproduce
  1. On a LS instance running version 2.73 and a fairly large amount of surveys (~ 3000), upgrade to 3.x using comfort update
    2 . Click "Check data integrity" option
TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)Version 3.14.5+180815
I will donate to the project if issue is resolvedNo
BrowserFirefox Quantum 61.0.1 (64-bit)
Database type & versionMySQL Ver 14.14 Distrib 5.5.60, for Linux (x86_64) using readline 5.1
Server OS (if known)CentOS 6.9
Webserver software & version (if known)Apache 2.2.15
PHP Version5.6.36

Users monitoring this issue

There are no users monitoring this issue.

Activities

ollehar

ollehar

2021-03-10 16:51

administrator   ~63024

You're using an outdated version of LimeSurvey. Please update to the latest version and check if the bug can still be reproduced. Thank you.
gslines

gslines

2021-03-11 21:41

reporter   ~63321

We have gone through a few updates since I created this ticket. I can confirm this problem doesn't exist in the current 3.x version.

Thanks!

Ginet

Issue History

Date Modified Username Field Change
2018-08-22 15:20 gslines New Issue
2018-08-22 15:21 LouisGac Assigned To => LouisGac
2018-08-22 15:21 LouisGac Status new => assigned
2021-03-10 16:51 ollehar Status assigned => feedback
2021-03-10 16:51 ollehar Note Added: 63024
2021-03-11 21:41 gslines Note Added: 63321
2021-03-11 21:41 gslines Status feedback => assigned
2021-03-12 11:04 ollehar Status assigned => closed
2021-03-12 11:04 ollehar Resolution open => no change required