Xampp runs old version of Apache

[ivanberti]

I am running on Windows Vista.

I already had version 2.2.6 of Apache running (located in c:/Apache).

I installed version 1.7.3 of xampp (via a Google Chrome window). The installation all seemed to go smoothly and installed the package under c:/xampp.

However, even on system restart, it is my previous version of Apache that is running, on port 80. http://localhost maps onto the htdocs dir in my old installation. There is no mapping for http://localhost/xampp.

The xampp control panel allows me to stop and start the OLD Apache service; obviously i am surprised that it is not pointing at the new version installed with xampp. Can I rectify? Or do I have to uninstall xampp (if so, how?), stop old Apache before completing install? And/or configure something else?

Probably irrelevant but this link... http://www.nat32.com/xampp/index.htm says the files xampp.exe and service.exe should be copied to c:\xampp, but these don't seem to have been downloaded.

[JonB]

Uninstall - read the XAMPP for Windows page

http://www.apachefriends.org/en/xampp-windows.html

Top Secret Explanation:

The 'other' Apache install is a true Windows install of Apache, so it starts the service.
XAMPP, on the other hand, is Windows agnostic, that why it needs a control panel. XAMPP does everything with command line calls to executables that are not registered with Windows. The 'other' httpd.exe (your original Apache) is running, and has a path, so when XAMPP does issue a call, Windows politely serves up the running instance of httpd.exe (the command syntax is the same).

OK?

[ivanberti]

Thanks for the explanation. I don't fully understand it but...

I have uninstalled xampp, stopped the original Apache server, and re-installed xampp.

All now appears to be OK, via the xampp control panel.

BTW, I couldn't find any documentation about uninstall, the batch file uninstall_xampp.bat, which is a bit of a give-away!

[JonB]

?
http://www.apachefriends.org/en/xampp-windows.html#524

Glad it worked out.

[rmwiseman]

I have had a similar problem, but on Windows XP.

XAMPP wants to use the Apache service (and the MySQL service actually) that is already installed. I'd like to say not to use the Apache service at all, since that's for my usual Apache installation, but when I try to untick the "Svc" box for Apache, it wants to actually uninstall the Apache service! (I had hoped that the tickbox was just to say whether to use the service or not.)

I also uninstalled and reinstalled XAMPP but I think the only reason that works is that it also uninstalls the existing Apache service (and MySQL service). When I realised it did that, I repaired my existing Apache and MySQL installations, stopped their services, reinstalled XAMPP and tried again. The result was the same, though: it controls and shows the status of the existing Apache & MySQL services, not the XAMPP ones.

Seems I have to uninstall the existing installations or at least their services. Is that a correct assumption?

Thanks!

[JonB]

You can either uninstall or disable (uninstall as service) the 'old' versions.

http://httpd.apache.org/docs/2.0/platform/windows.html

The Apache docs explain how to 'turn off' the service instance.

MySQL is 'more persitent' than Apache.

http://www.phpbuilder.com/board/archive ... 54006.html

If you have databases you wish to preserve, BE SURE TO DUMP THEM (backup to .sql files) - mysqldump.exe is often used for this.

Unless you plan to use the old installs in the future, uninstall both completely. It will cause less headaches.

This should be done while XAMPP is NOT installed. You need to have your machine so neither Apache or MySQL starts as a service before you try to install XAMPP (provided you wish XAMPP to be peristent as a service).

Good Luck

[rmwiseman]

Thanks for the speedy reply JonB!

I feared that would be the case. I do use my existing Apache installation pretty often and starting it as a service is most convenient. Ideally, I didn't want to uninstall Apache or its service.

I was really just wanting to try XAMPP so that I could install Joomla! without having to mess about with my existing Apache configuration.

Not to worry - at least I now know.

Thanks again!

PS - Actually, what I might do is rename the Apache service so that XAMPP hopefully isn't aware of its existence. I'll use

Code: Select all

httpd -k uninstall

to uninstall the service and then something like

Code: Select all

httpd -k install -n "ApacheMain"

to reinstall it with a different name. Perhaps that will work. MySQL doesn't matter so much to me!

[JonB]

Good thinking

LOL - that's why I lead you to that page.

XAMPP (other than the installer) is 100% Windows registry agnostic, that's why the Control Panel is needed, all CLI driven batches.

SO - you can indeed run both, as long as YOU know what they are doing. I have two Apaches and two Perls. I don't run two MySQL instances however, you could do that as well. If its only for testing, you might consider changing the default ports so you can have consistent shortcuts.

A couple thoughts. You could track down the batchfiles used to start the Specific XAMPP services you want, and make them into a shortcut, so you lauch them only when you want to work on Joomla. Even easier, you could also put all the Joomla specific Apache conf directives into a 'httpd-joomla-extras.conf' along with notes on what you disabled in the main httpd.conf (just a thought, as I said)

The thing is all the options and defaults are different (as you know), and at some point, you just wind up scratching your head, LOL.

Good Luck

[rmwiseman]

Thanks again - things are going more smoothly now!

[milesahead01]

I know this is a different sense of "old version of Apache", but it seemed close enough to tag along...

I am running the current Xampp (1.7.3) on WinXP. This includes Apache 2.2.14. I get complaints from my watchdog Secunia PSI that Apache 2.2.14 is insecure. I would like to upgrade to the current Apache, 2.2.15. I'm reluctant to muck up Xampp 1.7.3 by trying to slide Apache 2.2.15 under it. The obvious approach is to sit tight and wait for the new Xampp to come along and update Apache. Is this the wise thing to do considering 2.2.14 being "insecure"?

[JonB]

There is not a straightforward way to upgrade the Apache by itself. All you will do is likely break everything.

If your machine is behind a router, and you have not done port forwarding or created a DMZ to deliberately expose XAMPP/Apache to the internet (you are not publishing your site) -- there is nothing to worry about as no one can see your installation == they can't attack it. -- chill out and have a cool one of your choice...

If you have made your site available using XAMPP/Apache -

Are you using XAMMP to host a very active website that has valuable or controversial data on it? (you shouldn't be if you don't know what you are doing) - If not, probably don't worry about a DDOS attack. No one is going to turn a bot-swarm lose on you for no return.

Are you using ISAPI modules? (you may not even know what they are) - this is wholly unlikely AND XAMMP does not come with any. (You can turn this off by disabling mod_perl in the Control Panel if you aren't using mod_perl to devlop scripts.)

If these last two are no - chill out and have a cool one of your choice...

[milesahead01]

Thanks, JonB. Very helpful, that's just what I needed. No, I'm not publishing the Xampp site, so I'll breathe easier. All chilled out...