I'm an old dog (75) not very good at learning new tricks.
I still use Coral_8_0_0 to create my WAMP server and am comfortable with it, so please don't tell me to upgrade to 13_3_2_ZeroXIII.
I have tried that and haven't yet worked out how to have several websites in the vhosts folder and get to them via the localhost.
I promise that I will sort that out - but, meanwhile, I have another more pressing problem:
I am running Windows 10 on a desktop computer, and I have Apache running as a service and I can :
Stop it when I like and restart it when I want;
Maintain 13 websites in the vhosts folder;
Look at each site via the localhost.
A few weeks ago the Windows 10 OS was upgraded for April 2018 to version 1803, and my setup stopped working :
I could not stop or start apache either as a service or as a programme;
I could not look at my local sites via localhost.
This was really annoying as I update most of these sites on a daily/weekly basis.
Also Dreamweaver did not work properly as it could not access the local site.
I uninstalled the version 1803 upgrade and - magic - Apache and Dreamweaver and the localhost worked perfectly again.
HOW CAN I OVERCOME THIS PROBLEM ?
I sync everything to my laptop which also has windows 10 (not yet upgraded) where everything works as I like.
Today - the 1803 upgrade arrived and I installed it to see what would happen.
Alas - Apache and localhost stopped (like on the desktop machine) so I uninstalled the upgrade and everything reverted back to normal.
I would like to solve this problem before I get stuck into sorting out the latest version of WAMP.
Any help will be gladly received. Thanks in advance.
I am running wampserver and have reinstalled the latest version today. Apache is reportedly running (although actually appears in the process list twice??) but when I visit a basic HTML or PHP page the page just can't load. It spins round and round and then crashes. I've been looking at this for the last hour and can't figure it out. I've reinstalled it, copied the icu.* files to apache\bin.
If I look in the resource monitor, I see httpd.exe and also an entry with - as the Image and PID? What could be causing Apache to be running but not serving up webpages - even basic ones?
I could ping my websites but I got a 404 going there.
My server was running normally, no new mail for root.
Is there a service to alert you when your websites are down ?
What do you usually do to understand why it's down?
I took a look at the apache2/error.log and saw that it couldn't access one of the website I had deleted a few hours ago. I just did a a2dissite and restarted and it was fixed, I could access my websites.
I either got lucky or I postponed a problem. Any idea what I should do next to make sure everything is alright? (I'm on debian by the way)
I'm running XAMPP on my windows machine and experiencing a problem with Apache crashing a couple times a day. When it does, a dialog pops up and I have to manually tell windows to end the program. After I do that, XAMPP automatically starts it back up in a couple of seconds with no issues. When it crashes while I'm not home though, the server is down until I get back. So I have two questions:
Are periodic crashes something that should be expected, or is this indicative of another issue I should be trying to pinpoint?
If this is something I should just learn to deal with, is there a way to automatically restart httpd.exe when these issues occur, so I don't experience down time when I'm away from home?
You'd look into log files, especially the Apache access and error logs, to see what happened, when you are not at home. I've met some similar situation: I have a problematic PHP script hosted on my server, when someone visits the page, it leads to an Apache crash.
I'd suggest you do the investigation as follows:
Search the timestamp of recent Apache restart.
Check the Apache access log to see whether there are some scripts have been accessed.
Manually access these scripts in your browser (to see if Apache will crash again)
You'd better check the PHP error log as well.
If there is really nothing suspicious, you can try WAMP bundle alternatively, which is also a very popular PHP development environment and it is stable.
Although there aren't many cases in which one should "expect" periodic crashes, in this case you are better of reconsidering your setup. From the frontpage of the XAMPP site:
XAMPP is the most popular PHP development environment
Sure, you can use it as "production" server, but XAMPP isn't build for hosting websites, it is intended as development server, so you don't have to manually setup Apache, PHP and MySQL on you dev machine. If you actually want to run your website for the public, setup Apache/IIS, MySQL and PHP manually, those products on there own are made for running in production. Or you can consider getting some cheap shared hosting somewhere, so you don't need to setup anything.
I finished coding my website for awhile and would like to stop Apache from starting when my computer boots because it slows down my other startup applications. I have looked through the Apache Wiki, the source files, and the htaccess file. Maybe I am not finding it, but is there any way to do this without uninstalling Apache?
I am using Windows 7 as an OS.
*I just want to mention that this is different than simply stopping or starting or restarting Apache. I know how to do that. I would just like it not to start up on boot until I start working on my website again.
Thanks
Open msconfig (start->type "msconfig"->click "msconfig.exe")
Check "Startup" tab for Apache or "Services" tab if you can't find it, and disable it.