View Issue Details

This issue affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
05963Bug reportsOtherpublic2012-03-30 14:31
ReporterKingKorn Assigned Toc_schmitz  
PriorityhighSeverityblock 
Status closedResolutionunable to reproduce 
Product Version1.91+ 
Summary05963: 50 "Session Expired" Errors at the Same Time
Description

Hello,

we are using LimeSurvey 1.91+ (build 12416) and the survey in question has a total of 309 variables. What happened is that when we did the survey with 50 participants on 50 different PCs at the same time from the same PC lab, all of their sessions expired at the same time (showing the "session expired" error page when clicking on next). A few hours before that, 50 different participants had succesfully completed the same survey on the same machines. Do you have any idea how this can happen?

Thanks and best regards, MK

Steps To Reproduce

Error could not be reproduced in controlled settings.

Additional Information

What we tried was this (while a survey was being taken on a client):

1) Restarting the web server and/or the mysql service on the server -> had no effect and LimeSurvey still continued to run and save date. If data was sent from the client to the server while the service was down, the regular error messages (can't contact web server/database) were shown).
2) Changing the clients IP address -> as the PC lab used a single router to the internet with NAT, we thought this could have an impact, too. It had not.

We also contacted IT and there was no indication that the server or services necessary for the web page to run were interrupted. Following other bug reports (like 04970 or 05173) we also checked our version (which is fine) and our PHP settings (which seem to be fine, too, e.g. register_globals is off and we don't use any security mods like SUHOSIN etc.).

What PHP settings could cause this? Could the Internet Explorer version used be responsible? But how could 50 sessions expire simultaneously?

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)12416
I will donate to the project if issue is resolvedNo
BrowserInternet Explorer
Database type & versionMySQL 5.0.51
Server OS (if known)CentOS
Webserver software & version (if known)Apache 2.2.3
PHP Version5.2
Git branch / Pull Request URL

Users monitoring this issue

KingKorn

Activities

KingKorn

KingKorn

2012-03-30 11:19

reporter   ~18129

Last edited: 2012-03-30 11:52

To clarify: The "sessions expired" errors happened roughly at the same time, about half an hour into the survey, not when answering the same question (some participants were one question group ahead of the others and answering one of the question groups took about 2 to 8 minutes).

We also checked the following possible error sources:

3) Changing the time on the client or the server -> which had no effect on a running survey.
4) Deleting all cookies and temporary internet data etc. on the client's browser, while taking the survey -> which also had no effect and the survey could still be continued (though the active cookies and data shouldn't be deleted anyway).

All in all, I am amazed how robust against all these possible hazards LimeSurvey actually is (like the web server restarting etc.). And the more I think about this, I'm guessing that a global server error or misconfiguration is the source of the problem - but where should we look? Which PHP configuration settings for example could cause 50 (nearly simultaneously started) sessions to expire at the same time?

Or am I missing something fundamental? :D

c_schmitz

c_schmitz

2012-03-30 14:31

administrator   ~18133

This is not a support tracker.
Please use the community forums instead ( http://www.limeurvey.org/en/forums ) or consult one of our official LimeSurvey Professional Partners ( http://www.limesurvey.com)

Issue History

Date Modified Username Field Change
2012-03-30 10:30 KingKorn New Issue
2012-03-30 10:30 KingKorn Issue Monitored: KingKorn
2012-03-30 11:19 KingKorn Note Added: 18129
2012-03-30 11:20 KingKorn Note Edited: 18129
2012-03-30 11:21 KingKorn Note Edited: 18129
2012-03-30 11:52 KingKorn Note Edited: 18129
2012-03-30 14:31 c_schmitz Note Added: 18133
2012-03-30 14:31 c_schmitz Status new => closed
2012-03-30 14:31 c_schmitz Assigned To => c_schmitz
2012-03-30 14:31 c_schmitz Resolution open => unable to reproduce