Thanks for trying to help. But as I'm the only user on a local version on my hard disk (I'm only using about 20% of it at the moment) I don't see how it can be a memory problem.
But maybe I didn't understand all the thread. I'm not a programmer.
You say, you are the only user. Do you have to restart, even if nobody uses the machine?
Tell us what installation procedure you followed and what version of the software are installed.
I am having this same problem and I have the Moodle 2.3.1 Install package installed on a server. I access it from my PC and thus far three times in the last two weeks while using moodle I will execute a request and IE would return saying cannot display page. I would then have to log into the server and restart moodle to regain access. I am the only user so far.
Glenys, Johanne, there is no Moodle.exe in Moodle. These installs would suggest to me that they are XAMPP installs, in which case there is a flaw in the Xampp modules. Nothing to do with Moodle I am afraid. This same thing left me gasping and in the end, it caused so many issues for me that I dumped the Xampp installation and went to a WAMP. Johanne, if I am right about the Xampp and you are using Xampp on a server then I must ask why put yourself through that?
Yes it is the XAMPP installation and we used it because we were looking for something to give us a quick install for testing and that one click package gave everything in one. For production we were always intending to use the standard package so if the problem is with the XAMPP module then we need not expect to get that problem if we go to production.
That is certainly correct Johanne. I know it is a simple thing, using the Xampp release, but it is also a tricky thing., I used it on a standalone for two years, updating and using, but in the end, it became a nightmare.
There is also the issue that using the Xamp release can give a false impression of Moodle. Moodle, like any PHP app, can be a little resource hungry, but adding in the Xampp installer as well can mean that it wont scale up as well as you might think. Try about 25 connections at once and see how slow it gets. try 30 and the lag becomes a real issue. Obviously the more RAM you have the better, but sooner or later, it becomes a serious issue.
I really could use help since I have barely installed Moodle on a stand alone server running Windows Server 2008. I have been encountering this issue as well in having to restart the Moodle service, it appears every few hours or so the Moodle service just stops and will not let me access the server anymore until I physically go to the server and restart the service. I read the above thread and yes, I used the complete install of Moodle which comes with XAMPP for Apache. The complete version of Moodle I have installed is 1.9, evrything is running fine with the exception of having to restart the service. If I need to do anything specific, please explain in detail the steps or procedures I need to make. Thank you for your help!
I've posted this up before, so it should be familiar to some people...
The XAMPP install for Windows is utterly useless for its stated purpose. We fought valiantly for weeks to get Apache's httpd daemon to stabilize without success, finally performing an emergency data migration to an IIS7 installation of Moodle. The combined download is here and we've had nothing but joy since.
Save your sanity and, if you're on the Windows platform, use the IIS version.
Steve, the XAMPP install is limited, true, I found it in the end to be not what I wanted. It will not run properly if you try to set it up in an established Apache server. That is just a foolish thing to do, so why even try it? I cannot believe that anyone with any experience with Server technologies would not immediately recognise the problem and know how to resolve it.
The Xampp installer was designed for people who have little or no experience with server technologies so it is a one-stop installer. Setting up PHP and MySQL on IIS is just as much of a nightmare as using XAMPP. We, or more accurately I, opted for the WAMP option and have never regretted it. I administer two small installations as well as my private ones without problems, Three WAMPs, one LAMP, but I cannot get access to the Linux server, only the Moodle folders. (Can't say that I blame them, who wants me stomping around inside their server when I know so little about Linux?)
There are lots of XAMPP installs out there running, but bein' as this package is NOT a production platform (they say as much), it really doesn't make much sense to even start with it. WAMPServer2 seems a little more dependable as an install (of course, Moodle goes in separately), but even so, it does make sense to just get to know the pieces individually anyway.
As for IIS, we moved to IIS this year, and although, overall, it's done fairly well, there are lots of WIndows "gotchas" we've been gradually wading through. As an Internet service, Apache seems a lot more stable, dependable, and simple. We moved 'cause nobody around here seems to want to support it (we're an all-Windows house), and we were worried about PHP acceleration (we're a big install).
Thank you very much for the information! I have upgraded and Moodle is up on my server. Now, I just need to find out how to change the default loclahost/moodle url to the IP address I want to assign to it. Do you have any suggestions? Again, Thank you for your help.
Go into the config.php file and edit to reflect the changed URL. It should read:
or something that reflects your url.
Once done, then log into your Moodle and go to the address bar of your browser, add in the bit that says:
This brings up a screen you can put in the old URL and replace it with the new URL.
This should all work as it is supposed to.