Suddenly this morning, I was unable to login to the system with any of the users, including 'admin'. The message on the login page states "Your session has timed out. Please login again." I've spent the day reviewing this forum, checked Google for other references and have failed to find an answer.
Has anyone found a way to get past this problem? The solutions presented in other forums (clear cookies, etc.) haven't worked and many of the posts were from late last year.
This is a very nice system and any help would be appreciated.
Thanks in advance.
In firefox you can select just the cookies related to the moodle server, not sure in IE. However in IE you can clear the cookies with the browser closed from Internet Options in the Control Panel.
What browser are you using?
What was the exact sequence you used to clear the cookies and attempt to login again?
What about logging in from another machine?
I have experienced the problem of being locked out from logging in with the message "Your session has timed out. Please login again" I cleared all the cookies. I even used another browser. And of course students at a distance are have the same problem.
So is there another solution? One solution from a major university that had the same problem was that they had to blow Moodle off and reinstall.
I hope that's not the only solution.
First check your moodledata/sessions directory. New file should be created after first access from browser. If they do not appear, fix your permissions.
I am rather new to all this: I could not find the folder you refered to.
I did find a sessions folder here:
/ public_html / web / moodle / uploadata / sessions /
All the files were set to 600.
There are about 20 of them. There are no dates to discover when they were created.
BTW: The site has been running for about a year with no problems, out of the clear blue this problem appears.
Just a shot in the dark here, but I have experienced a similiar problem after setting up a second moodle install with the same sessioncookie in Moodle config. If you have installed a second copy of Moodle recently you may want to log in as the admin and go to configuration/variables and make sure you have different sessioncookie names in each install.
Again, just a long shot...
So some suggestions:
1. If you are using database sessions, use MySQL COntrol centre or some other utility and delete the records in the sessions table in the database, the worst that should happen is that logged in users would be logged out.
2. Try logging in with a different browser, if you can try changng the 'session' method. There may be a way to do this without logging in by going to the command line on the server, but I don't know it.
3)restarting firefox browser
4)using another browser (safari)
5)checking server space (i have plenty left)
Nothing seems to work regarding , "Your session has timed out. Please login again."
Please offer guidance.
I’ve been having this problem for a while and the only way I’m able to resolve it “temporarily” is to delete all the files in the Moddle “sessions” directory; needless to say, this has become a very frustrating situation. I have set the “sessions” directory permission to 777 as well as tried all the other suggestions in this forum and none seems to bring a permanent solution to this problem…anything else I should try?
I was also having the same issues, please you do not have to re-install. All you need to do is follow these simple steps:
1. Click on site administration (assuming you are logged as an administrator) under Administrator
3.Click on "Session Handling"
4.Under Timeout, adjust Timeout to 2hours or 4hours as the case may be
You see, the problem is actually a session problem.
This JUST started happening to us about 2 weeks ago
sometimes deleting cookies helps, sometimes not...what's goig on?
my moodle data dir is set to 777...
this is making our school very unhappy and really messing with courses
Same problem here.... everything was working perfectly till last night.
- Moodle 1.71
- mysql version 5.0.24
- php version 5.2.1
- IE 6.0
Per the multiple emails in both this forum and the Bug Tracker, I followed all suggestions and sequentially:
- Navigated to a non-"My Moodle" site, then cleared all cookies from the browser
- Closed out the browser
- Ensured Moodledata permissions were 777
- Cleared all session data from my Moodledata file; and - just for good measure - cleared out the temp files
- PHPAdmin'd to my SQL dbase and changed my dbase sessions to yes (1)
- Opened my browser and navigated to my root; then chose "Login"
I can now login. All that being said, I'd really rather not make this a regular part of my unplanned maintenance activities.
To echo Ms. Constant, "What's going on?"
Same problem here also. Started yesterday. I tried all the things Deborah suggested and still I cannot login. Firefox and Opera works fine, but IE 7 and 6 gives the error message in login. The version of the Moodle is 1.6.4.
Solved by changing ownership of the session directory to apache:
chown apache:apache /yourdir/moodledata/sessions
That's all it took and it looks like everything is working fine now.
This sounds promising. I have to confess that I don't know how to change the session directory ownership as you described. Could you please offer more detail on how to do that?
you may want to include the -R option to recurse the directory as well (chown all dirs under that dir as well)
chown command is supposed to be issued from linux command line, aka console.
There is no way (that I'm aware of) to do it using FTP.
And another problem, if you are using windows hosting, then you can forget about file/folder ownership, and concentrate on read/write permissions.
We had the same problem (user received "Your session has timed out. Please login again." and when they logged in it asked to login again if incorrect password was used but was taken back to the "front page" with "you are not logged in" if correct pw was used) when we restored the moodle and moodledata files from a back up copy to a new install of RHEL5 64bit (we were on 32bit but had to install new drives for space so figured I would go 64bit while I was at it).
I spent the better part of the day (and now late evening) looking for this fix. I knew it was a file permissions issue but I did not know which file/s (I also had to change the ownership of the /usr/moodledata/moodle01/temp directory along with the 'sessions' directory). Once I chown'd the files for apache all appears well...
Running Moodle 1.9.8+ (Build: 20100407) from two (applications server and DB(Mysql)) servers.
R. A. Wilhite
We were having the same problem "Your session has timed out. bla bla"
Write permissions of sessions-directory were OK, and each time someone tried to log in a file was written into this directory BUT the files were 0 bytes. Problem: disk quota on the server exceeded! Thrown away some files and now everything works fine again.
I had the same problem.... the problem was that the disk was full
Just check if you have enought space in the disc
I had this problem multiple times on my first attempt at installing and configuring Moodle via Fanastico on Cpanel. Every navigation required re-login. So I wiped the install and started again. On my third install, I was able to get everything working just fine. I created a Course with one topic and a Powerpoint converted with PPT2Flash Wondershare works well, However..f
My second course has a Sessions problem. This course is a Topic list of 6 Links to Resources (media files wmv and jpgs)
Links to Resources
Pressed Upload File button.
FTP uploaded files into correct folder
Choose (chose) the specific file for each Topic.
User login ok. Enroll and view course ok.
User clicks on Linked Resource link,
User watches Resource view.php. User presses Jump to Next Topic arrow.
The user is forced to login again in order to continue to the next link.
Worth a try.....
I had same problem. I had moodle site was running but all the courses were gone.
One thing I had to do was reboot the server and our school server admin ran the fsck(i think it stands for file system check?). After that it some how fixed everything. Eventhough, I don't think disk fault would hve caused anything.
So try to reboot your server and if it asks to run the fsck do it so.
1) Deleted all files in moodledata/sessions
2) chmod 777 moodledata/sessions
What were your settings for session timeouts?
Do you have a proxy/load balancer/cache server in front of moodle that may be overidding your moodle settings?
Hello everyone ! Hope I'm posting this msg in the correct forum,but I'm trying to install moodle using Rediff web hosting.Here goes the steps I followed while installing :
1. Dowloaded a standard package from downloads secn in moodle.org.
2. Extracted the moodle folder from it.
3. Uploaded the contents of the folder on the server.
4. Created a new database(My sql ofcourse !).
5. After all done, I tried opening the site,providing the URL : http ://mydomain.com/moodle .
6. Everything was fine and I was redirected to get on with the installation.But.....
I got an error message that Data directory was not found(something like that...)
Tried solving that problem by manually creating a "moodledata" folder outside my website's folder,gave it all pemissions(777).Did a little bit changes in the config.php file:
$CFG-> dataroot : 'moodledata'.
And tried installing again with the data directory path as "moodledata" only and nothing else. I think this is the point to be noted while finding what went wrong.
BUT I was allowed to continue with the installation,upto the step of agreeing with the Terms&conditions .
After this,I was expecting to be redirected to the page where I can Set-up the administrator's account.But instead I was taken to the "index.php" page with a message "Your session has timed out. Please login again". And I can do nothing further !!!!!
I'd tried installing the whole thing with new database and all. But nothing worked.I'm new to moodle.Can't figure out what created the mess... What went wrong? Kindly,someone help me out regarding this.
To give you a concrete example, this is how my dataroot and dirroot are specified:
$CFG->dataroot = '/home1/langconc/moodledata'
$CFG->dirroot = '/home1/langconc/public_html/moodle
If your dirroot is specified correctly, then you should be able to set up your moodledata specification in a manner parallel to the above example.
This is probably the cause of your "timed out" message because data concerning current logins is kept within the moodledata folder and it was not accessible.
Hope this helps!
Thanks for the quick response Thomas !
Moodledata folder was given full access permissions,as I'd mentioned.
My actual concern is about why i'm not given to create the admin account and instead redirected to the login page with a timed out message.
Doing the same thing locally,we generally create the admin account first,and then move on for further proceedings. Isn't the procedure same for installing moodle on web?
I meet the same problem as Rachna, But your tip did not help!
My datroot is: ' myurl_name'
And my dirrot is:'myurl.name/moodledata/moodle-weekly-19/moodle'.
Is ther annyone who can help?
I have tried to change permissions and lots of tips found here but not yet made it run.
Running on One.com webhost
I had a lot of cookie problems with my site because there was an underscore character in my subdomainname. This problem only manifested itself when trying to login with Internet Explorer 7, not in other browsers. The warning I got was "Unfortunately, cookies are currently not enabled in your browser".
test_test.example.com did not work
testtest.example.com did work
Pretty strange but I've pinned this down exactly, having two identical installs on two identically configured subdomains (except for the name ofcourse).
The problem I came across with the error "Your session has timed out. Please login again." I solved setting the permissions on the moodledata folder and all files in them to 777. There's probably a better setting for this, but in my case the moodledata folder was outside of the public folder, so there was no problem.
My understanding is that the underscore character is technically invalid for DNS based host names.
What are the valid characters for a domain name and how long can it be ?
When choosing the name for your domain, always remember that: - you *can't* use stressed vowels (such as à, é, ò, etc.); - you *can't* use symbols (such as ' + . , | ! " £ $ % & / ) ( = ? ^ * ç ° § ; : _ > ] [ @ ); - the name's length must range between 3 and 63 characters (excluding the extension); - the name can neither start nor end with the character "-", although the character "-" is allowed inside the name. So, to name your domain you can use any letter, numbers between 0 and 9, and the symbol "-". .
Length may vary, from 3 to 63 types.
For domain names registered under the geographical structure, the limit is between 1 and 63 types.
Got this error recently when migrating moodle to another machine. In my case the problem was solved by deleting 'sessions' directly completely and recreating it. Cleaning it of files & setting correct permissions didn't seem to help :-\
I had exactly the same thing. Was not able to create the sessionvariables
I was on a shared server - Said I ran out of disk space, but actually I had too many iNodes.
All I did was delete my old files and folders
Here is the documentation from my isp
Hope this helps someone else
Just had this problem...couldn't login, or login and no access. We had blown max inodes on shared server....
So I deleted files and reduced inodes to an acceptable level.
Now I can login, but now resources are available...Gives message Stream not found.
This is happening in the 2.7 live site, 2.7 Test site and the 1.9 original site.
I've verified all the resourcs are there, It doesn't make any sense to me that the original 1.9 system doesn't work now because it hasn't been used. Any ideas???