Now refresh or close/open your services window and you'll see it`s gone.ĭO THIS for all services that XAMPP finds as running with an incorrect path. If the service has spaces such as Apache 2.1 then enter it in quotes, i.e. It should be exactly as it appears in your services. on command prompt type sc delete service, where service is the service you're wanting to delete, such as apache2.1 (or sc delete Apache2.4). Got to command prompt (run as administrator): Start > all programs > Accessories > right click on Command Prompt > Select 'run as administrator'ī. In either case, you need to delete those incorrect services.Ī.
APACHE WON T START XAMPP INSTALL
Even if you only see one, look at the path, chances are it's from a previous install and causing your install not to work. Chances are that you have Apache listed twice, one from your correct install and one from a previous install.
APACHE WON T START XAMPP PATCH
Look at the patch indicated in the description (right click on service then click on properties).
Start Services via Control Panel>Admin Tools (also with Ctrl+ R and services.msc) I even manually uninstalled but still had issues. I did install XAMPP once before, uninstalled and reinstalled. Then port 80 should be available again.Had the same problems as stated above, made sure nothing was using port 80 and still not working and getting the message that Apache and Mysql were detected with the wrong path. So in this case, the lowest number process in the list is 2204, so just run this command: kill 2204Īnd then the parent process is killed and all child processes should drop away as well. Now looking at that list, typically the lowest number in that process list will be the parent-since it starts up before the other child process of course-so you should kill that to kill all processes. So if you kill a child process, the parent process notices it & respawns a new child. Apache runs on the concept of there being one parent process with many child processes spawned to deal with traffic.
The list should look something like this: httpd 2204 jake 2w REG 1,2 24685 17953784 /Applications/MAMP/logs/apache_error.log Note the two grep commands piped together? What I am doing is getting the list of open files, then filtering those which have a file path connected to MAMP-or in your case change that to XAMPP or whatever folder/directory you have it running in-and the I am filtering the apache in the pathname.
That said, if this is basically a “zombie” instance of Apache running after some XAMPP tweaks, the best bet is to do something like the following:įirst, run lsof (list open files) which will list all of the files actively open on the system. Once there, uncheck Web Sharing-which is basically just Apache httpd-and your problem should be solved. If this is caused by Apple’s web sharing you can handle this all by going to System Preferences… and then selecting Sharing. There are two things that could be causing the issue: Apple’s built in web sharing service being active or zombie XAMPP processes still being active.
0 kommentar(er)
