witch Posted March 20, 2013 Posted March 20, 2013 (edited) Recently our Moodle has given us some problems related to sessions timing out. Sometimes when a user logs on, they are unable to and get the message that the session has timed out even though they havent managed to logon. Or, when they are working on it, suddenly when they click on anything it becomes obvious that they have been logged out. The server is set to the maximum time allows - 2 hours I think I don't know much about Moodle, can anyone give me any pointers? We upgraded to 2.2 at Christmas and it has been fine until now. Nothing else has changed. Edited March 20, 2013 by witch
Geoff Posted March 20, 2013 Posted March 20, 2013 Is the system time set correctly on the Clients and the Moodle server?
witch Posted March 20, 2013 Author Posted March 20, 2013 Is the system time set correctly on the Clients and the Moodle server? The moodle is on our main - and only -server and the system time is definitely OK there and on the clients as well.
penfold_99 Posted March 20, 2013 Posted March 20, 2013 I would check the permissions of the moodle data folder, if it can't write sessions data then it would give you your session has timed out.
witch Posted March 20, 2013 Author Posted March 20, 2013 I would check the permissions of the moodle data folder, if it can't write sessions data then it would give you your session has timed out. But then it wouldn't work for everyone and this is only sometimes and some (different) people?
markwilfan Posted March 20, 2013 Posted March 20, 2013 Are they all using the same browser? Possibly a cookie issue on the client side? Are you using database or files sessions. Try switching to the other to see if it changes anything. We use file sessions and have no probs Are the cookie domain details ok? Are the clients that have the probs with sessions accessing inside your network? Do you have any funny dns kiddnapping going on? Just out of interest why didn't you go to 2.4 at chrimble?
witch Posted March 21, 2013 Author Posted March 21, 2013 Are they all using the same browser? Possibly a cookie issue on the client side? Are you using database or files sessions. Try switching to the other to see if it changes anything. We use file sessions and have no probs Are the cookie domain details ok? Are the clients that have the probs with sessions accessing inside your network? Do you have any funny dns kiddnapping going on? Just out of interest why didn't you go to 2.4 at chrimble? We didnt go to 2.4 because it wouldnt allow it in one jump. And since the person doing it was mrwITch, free, at home in his own time, after going to 2.2 caused issues that took a while to sort, he wasn't keen to do it all again. No idea if we are using database or file sessions. How do I find out and how do I change? Other people have suggested cookie issues but we can find nothing wrong with that side. Where would you look? I have only been told about issues here on the network. No dns kidnapping that I am aware of!
markwilfan Posted March 28, 2013 Posted March 28, 2013 Hey wITch Did you get this sorted? Don't mind having a look if you want.
witch Posted March 28, 2013 Author Posted March 28, 2013 @markwilfan Oh wow, would you? That would be great. I'm not back in till after Easter now. PM me with a list of what you need and I will do my best
markwilfan Posted March 28, 2013 Posted March 28, 2013 Of course we all play for the same team. I'll pm you over the weekend or on Tues when I'm back in
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now