View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
16172Bug reportsOtherpublic2020-04-22 17:072020-05-06 16:12
Reporterritapas Assigned Tocdorin  
PrioritynoneSeverityminor 
Status closedResolutionsuspended 
Product Version3.19.2 
Summary16172: taking non active survey causes error reporting in logs as if there was a corruption in the database
Description

This is related to version 3.15.5, I don't know if it has been fixed in following releases.

If someone sends invitations for a still non-active database and the participant tries to respond, the software logs a message like the following:

2020/04/22 12:41:01 [error] [system.db.CDbCommand] CDbCommand::fetchAll() failed: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'limesurvey.survey_753773' doesn't exist. The SQL statement executed was: SHOW FULL COLUMNS FROM survey_753773.

This is very alarming but it is indeed harmless.
Maybe it could logged be at [info] level.

Steps To Reproduce

create a survey and invite participants without prior activation. Then, as a participant , try to answer (one must change browser or remove cookies and section before).

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)3.15.5 (build 181115)
I will donate to the project if issue is resolvedNo
Browser
Database type & versionmariadb-5.5.60
Server OS (if known)Red Hat Enterprise Linux Server release 7.5 (Maipo)
Webserver software & version (if known)httpd-2.4.6
PHP Versionrh-php71-1-1

Users monitoring this issue

There are no users monitoring this issue.

Activities

ritapas

ritapas

2020-04-23 08:53

reporter   ~57331

The same happens if, for istance, a user creates a survey or template with a reference to a non-existant resource.
In case of minor elements missing like e.g. favicons we would prefer the application to log the events as info or if at all as a warning.
cdorin

cdorin

2020-05-06 16:12

reporter   ~57595

I see - it may be something to be discussed in the future, but now there are other issues we need to tackle.

Issue History

Date Modified Username Field Change
2020-04-22 17:07 ritapas New Issue
2020-04-22 20:14 ollehar Product Version => 3.19.2
2020-04-23 08:53 ritapas Note Added: 57331
2020-05-06 16:12 cdorin Assigned To => cdorin
2020-05-06 16:12 cdorin Status new => closed
2020-05-06 16:12 cdorin Resolution open => suspended
2020-05-06 16:12 cdorin Note Added: 57595