hi,
i am using moodle 1.7 and xampp package.
when i refresh the page two three times in simultaneously,moodle is getting stuck,it is not loading any pages.
please help me in this matter.
any help wiould be highly appreciable.
apache crashing
Number of replies: 11Re: apache crashing
My OS is windows 2003 server Pop up window comes saying Apache is shut down and moodle stops working
Re: apache crashing
Anil,
There are many things that could be at fault, but if you could share some more information it might help... for instance what EXACT versions of PHP, and Apache are you using on your Window 2003 server and how much RAM do you have?? Also, have you looked at your Apache Server logs for errors?
We setup about 10-12 "versions" of PHP/Moodle and Apache last summer using Windows 2003 server. Apache and PHP under Windows 2003 is often very, very picky. Search theses forums for other windows 2003 setups that are successful and copy the exact versions of PHP/Apache they use. Our experience with fairly extensive testing was that many versions of PHP/Apache under windows would eat RAM, (i.e. use it and NOT release it) and the HTTPD.exe process RAM use would grow until the server stopped responding and had to be rebooted.
Again, this may be or may not be your issue. You can find out VERY easily, just do these steps:
1. Stop and Restart apache server
2. on Apache server Window2003, open TASK MANAGER, go to processes/Memory TAB and locate the Apache Process (i think HTTPD.exe for Apache 2.x.x) and see the base amt of RAM used before users access Moodle
3. Next go to lab or other workstation and start logging in, viewing pages, refreshing, using Moodle, etc.
4. ON Apache server track RAM use by HTTPD.exe process, if RAM use just grows & grows (may start at 40+MB and grow to 800+MB!!) and RAM is NEVER released you wil see your server become NON-RESPONSIVE, then... your combination of PHP and Apache suffers the mem-leak and you need change to a stable, proven combination of PHP and Apache that does NOT have the issue.
If your Apache process uses and releases memory normally as users access Moodle (e.g.RAM use fluctuates normally according to Moodle use -i.e. grows and shrinks ) then your lockups are due to other issue(s) , But, this is a simple thing to check. If it is your issue search these forums for stable, successful PHP/Apache version combinations. I know PHP 5.2.1 had a good rep when matche with certain Apache version.
There are many things that could be at fault, but if you could share some more information it might help... for instance what EXACT versions of PHP, and Apache are you using on your Window 2003 server and how much RAM do you have?? Also, have you looked at your Apache Server logs for errors?
We setup about 10-12 "versions" of PHP/Moodle and Apache last summer using Windows 2003 server. Apache and PHP under Windows 2003 is often very, very picky. Search theses forums for other windows 2003 setups that are successful and copy the exact versions of PHP/Apache they use. Our experience with fairly extensive testing was that many versions of PHP/Apache under windows would eat RAM, (i.e. use it and NOT release it) and the HTTPD.exe process RAM use would grow until the server stopped responding and had to be rebooted.
Again, this may be or may not be your issue. You can find out VERY easily, just do these steps:
1. Stop and Restart apache server
2. on Apache server Window2003, open TASK MANAGER, go to processes/Memory TAB and locate the Apache Process (i think HTTPD.exe for Apache 2.x.x) and see the base amt of RAM used before users access Moodle
3. Next go to lab or other workstation and start logging in, viewing pages, refreshing, using Moodle, etc.
4. ON Apache server track RAM use by HTTPD.exe process, if RAM use just grows & grows (may start at 40+MB and grow to 800+MB!!) and RAM is NEVER released you wil see your server become NON-RESPONSIVE, then... your combination of PHP and Apache suffers the mem-leak and you need change to a stable, proven combination of PHP and Apache that does NOT have the issue.
If your Apache process uses and releases memory normally as users access Moodle (e.g.RAM use fluctuates normally according to Moodle use -i.e. grows and shrinks ) then your lockups are due to other issue(s) , But, this is a simple thing to check. If it is your issue search these forums for stable, successful PHP/Apache version combinations. I know PHP 5.2.1 had a good rep when matche with certain Apache version.
Re: apache crashing
Thankx Mark for the Response Sorry for late reply My
PHP Version 5.1.4
| Apache Version | Apache/2.2.2 (Win32) mod_ssl/2.2.2 OpenSSL/0.9.8b mod_autoindex_color PHP/5.1.4 |
My system Ram on Windows 2003 server is 1GB
Total users are 450+
Simultanious users are almost 120+
Functioning is quite normal
But Apache crashes and i have to restart Xampp
The site works well for intranet as well as internet have a public domain name also.
But when apache crashes have to manage the server by romote login if am not present in the campus and restart Xampp.
Thanks for the reply
Regards
Anil Karwankar
Re: apache crashing
Anil,
One quick point, 1GB of RAM is a bit skimpy for a production Moodle server if it has Apache, MySQL, and PHP on it... increase it if you can!
I just read another forum post by Ryan Smith recently where he has has good luck with this combination of widows/apache/php listed below.
You don't say how often your apache crashes, but you may want to try his configuration versions. My suggestion would be try them on a test machine first. I have NOT tried these, but Ryan S. claims they work for him. Looking on the web It looks like he is using the latest versions of the main components. This is the first listing of this successful setup I have seen. I have NOT seen your version of PHP used by other large windows production sites.
-------------------------------------------------------------------------------
Ryan Smith said:
The latest versions of all of the WAMP software are working fine here.
Apache 2.2.8
MySQL 5.0.51a
PHP 5.2.5
eAccelerator 0.9.5.2
Our production and dev server have each been up for 34 days with no Apache restarts. Our production site serves a little over 1000 logins a day
--------------------------------------------------------------------------------
good luck Anil... If you search there are other listings for Stable WAMP here as well... one by Ken Wilson (UK) also has a proven track record
Mark
One quick point, 1GB of RAM is a bit skimpy for a production Moodle server if it has Apache, MySQL, and PHP on it... increase it if you can!
I just read another forum post by Ryan Smith recently where he has has good luck with this combination of widows/apache/php listed below.
You don't say how often your apache crashes, but you may want to try his configuration versions. My suggestion would be try them on a test machine first. I have NOT tried these, but Ryan S. claims they work for him. Looking on the web It looks like he is using the latest versions of the main components. This is the first listing of this successful setup I have seen. I have NOT seen your version of PHP used by other large windows production sites.
-------------------------------------------------------------------------------
Ryan Smith said:
The latest versions of all of the WAMP software are working fine here.
Apache 2.2.8
MySQL 5.0.51a
PHP 5.2.5
eAccelerator 0.9.5.2
Our production and dev server have each been up for 34 days with no Apache restarts. Our production site serves a little over 1000 logins a day
--------------------------------------------------------------------------------
good luck Anil... If you search there are other listings for Stable WAMP here as well... one by Ken Wilson (UK) also has a proven track record
Mark
Re: apache crashing
Anil,
If you are successful with the newest WAMP config I forwarded, PLEASE take minute and post your results here (and maybe EVEN as a stand-alone new thread in Moodle Windows forum).
It is just as important to post SUCCESSES here as it is to post problems!
And, since the WAMP setup has such a troubled history, a SUCCESSFUL setup could save a lot of pain and frustration for other new WAMP users.
Good luck I hope it works for you, and again bump your RAM up from 1GB as much as you can! 2-4GB RAM will serve you and your students well!!
Mark
Mpls, MN
If you are successful with the newest WAMP config I forwarded, PLEASE take minute and post your results here (and maybe EVEN as a stand-alone new thread in Moodle Windows forum).
It is just as important to post SUCCESSES here as it is to post problems!
And, since the WAMP setup has such a troubled history, a SUCCESSFUL setup could save a lot of pain and frustration for other new WAMP users.
Good luck I hope it works for you, and again bump your RAM up from 1GB as much as you can! 2-4GB RAM will serve you and your students well!!
Mark
Mpls, MN
Re: apache crashing
hi Anil,
Mate - Mark is spot-on here... 1GB is far from sufficient - especially if you're dreaming of having 120 concurrent users (which coincidentally seems to high if you have a total of 450 users). Simply running Win2K3 + Apache + MySQL should be using all/most of this even before you start serving client sessions..
Be careful too about running very old (5.1.4 is almost 2 years old) versions of PHP.
Good luck getting it sorted.
Myles C.
Mate - Mark is spot-on here... 1GB is far from sufficient - especially if you're dreaming of having 120 concurrent users (which coincidentally seems to high if you have a total of 450 users). Simply running Win2K3 + Apache + MySQL should be using all/most of this even before you start serving client sessions..
Be careful too about running very old (5.1.4 is almost 2 years old) versions of PHP.
Good luck getting it sorted.
Myles C.
Re: apache crashing
120 simultaneous users is actually quite a lot. As everybody else has said you have no chance with 1GB of RAM. You need at least 4GB, but you have the compounded problem that there are well known memory leak problems with Apache on Windows. You should consider in order of sanity...
* switch to Linux
* switch to IIS
* research which combinations of PHP and Apache are stable on Windows (there was a thread about this recently)
At the very least make sure your Apache setup is well tuned. There's plenty of information in Moodle Docs and elsewhere on the Net. Don't use xampp for a production server - even it's website says that it is only intended for test and demonstration use.
Honestly, Moodle 1.7 wasn't really Moodle's finest hour. I would *strongly* with bells on suggest that you upgrade to at least 1.8.4 and you could even consider 1.9Beta (which seems very stable now).
* switch to Linux
* switch to IIS
* research which combinations of PHP and Apache are stable on Windows (there was a thread about this recently)
At the very least make sure your Apache setup is well tuned. There's plenty of information in Moodle Docs and elsewhere on the Net. Don't use xampp for a production server - even it's website says that it is only intended for test and demonstration use.
Honestly, Moodle 1.7 wasn't really Moodle's finest hour. I would *strongly* with bells on suggest that you upgrade to at least 1.8.4 and you could even consider 1.9Beta (which seems very stable now).
Re: apache crashing
Hi Am also facing same problem am using Moodle 1.7.2 and apache crashes typically when there are no. of login errors. If you find any soltution please convey me at karwankar@yahoo.com I have to restart xampp
typicallyy i have nade a batch file a.bat which has
xampp_stop
xampp_start
at dosprompt but the problem is that the dos prompt window has to be kept open else moodle wont work
Re: apache crashing
If you subscribe to this forum you'll get emailed 
See my reply above somewhere.....
See my reply above somewhere.....