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.
Related
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'm having a bit of trouble with Xampp. Apache keeps stopping and starting again every time I try to load a page. It changes ports and PID's every second and in the end, I'm lucky if the page loads at all. I have no idea what causes this, it wasn't doing that a few hours ago, and I didn't touch Xampp or Apache's configuration. I tried reinstalling xampp but the problem remains.
Skype isn't on, I know that's not the problem.
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 am using Apache Tomcat 6.0.18, I am running on Windows XP
I have a web application which I place it's war file under webapps folder. The web application runs fine, its just when I run the shutdown.bat the application still runs (as in I refresh the page and it doesn't come up not found).
I check the localhost:/8080 and webpage cannot be found comes up
but when I run localhost:/8080/myapp my application comes up.
I have tried this in both IE and Firefox
Thank you for any help.
I had this similar problem, This can only happen if Apache Tomcat is not configured properly. Best way is to check build path and look for exact directory of Apache.
Example
i.e C:\Program Files (x86)\apache-tomcat-7.0.27
Also look for windows service for start, restart or stop
Run - services.msc
You may want to check this link
i.e
Verify that tomcat is actually down (simplest way is via task manager)
The issue sounds like a caching issue. Try deleting your cache.
after copying zend library in my zend proj and refresh the page Apache wont start.
it show me this error : Appache Http Server has stopped working
i use of xampp , version 1.7
Your question is really vague. There can be a number of things that went wrong and you didn't give us enough background information on the install. (like config files you changed, directories you renamed, etc.)
If you cannot start Apache, the first place to check is the Apache error log file for problems. It will most likely have an error that we can help you troubleshoot.
I am not familiar with xampp directory paths but will take a guess that you need to look here: /xampp/apache/logs/error.log.
i`ve change my xampp version to 1.7.3 , now it work nice