 | |||||||||||||||||||||||||||
| |||||||||||||||||||||||||||
| |||||||||||||||||||||||||||
Ready. You successfuly upgraded XAMPP. By the way: the upgrade will stop a running XAMPP and will start XAMPP as soon as the upgrade is finished. XAMPP will be started after an upgrade even if it was not running before.
Step 4: TestingNow use your favourite web browser and test the new XAMPP version by accessing your web site. For example simply type http://localhost in the location bar of your browser window.After upgrading you can delete the lampp-upgrade directory; it isn't needed any more.
Under special circumstances you can get the following warning message: |
Author:
|
The upgrade program carefully tried to upgrade one of your configuration files. In order to upgrade the file, the program had to edit some lines you had already changed. Seeing as nobody wants to lose valuable configuration information, the upgrade program decided not to change the file but save a copy of the new file in addition to the original one.
2. Starting XAMPP
What's the meaning of the messages while starting XAMPP?
You may get three error messages while starting XAMPP:
LAMPP-Apache is already running.
An Apache daemon is already running.
The LAMPP startup script did not start XAMPP-Apache because there is an Apache instance already running. To start XAMPP properly, first you have to stop this daemon.
LAMPP-MySQL is already running.
A MySQL daemon is already running.
Mostly due to the same reasons as the above error. The LAMPP startup script found a MySQL daemon already running on your system. To start LAMPP properly, you have to stop this daemon first.
I got the error "/lib/libc.so.6: version `GLIBC_2.2' not found". What now?
|
Your Linux system is too old. XAMPP needs a newer Linux distribution that uses the glibc 2.1 version.
What's the secret about "Error 1"?
Good question :) This error can exist for multiple reasons.
Apache spits out this error under several circumstances. To
find the exact reason we have some exploring to do:
tail -2 /opt/lampp/logs/error_logIf you now see "Invalid argument: Could not set permissions on ssl_mutex" or "Invalid argument: Unable to create scoreboard" please take a look at answers below. If you see another error message please email it to me. Maybe we can solve the problem together. My email address is oswald@apachefriends.org.
Apache doesn't seems to starting. What can I do?
Good question :) This error can exist for multiple reasons. Apache spits out this error under several circumstances. To find the exact reason we have some exploring to do:
tail -2 /opt/lampp/logs/error_logIf you now see "Invalid argument: Could not set permissions on ssl_mutex" or "Invalid argument: Unable to create scoreboard" please take a look at answers below. If you see another error message please email it to me. Maybe we can solve the problem together. My email address is oswald@apachefriends.org.
What do I do if the error message is "Invalid argument: Could not set permissions on ssl_mutex"?
The whole error message is:
|
In this case you have to change the Group directive (about line 318) in /opt/lampp/etc/httpd.conf.
You should find there something like:
|
Change the "..." to "nobody", "nogroup" or #-1. One of these three possibilities should work.
What do I do if the error message is "Invalid argument: Unable to create scoreboard"?
The whole error message is:
|
In this case you have to remove the hash (#) in front of the Scoreboard directive (about line 71) in /opt/lampp/etc/httpd.conf.
There, you should find something like:
|
Simply remove the hash at the beginning of this line:
|
Now this error message should not bother you anymore.
What do I do if the error message is »Invalid argument: Configuration failed«?
In this case, Apache is unable to get the IP address for your
host name. It should normally work but sometimes (mostly if
you're using DHCP) this situation could happen.
Solution:
Simply call the following command (Please use copy&paste. The ` characters are mandatory):
echo 127.0.0.1 `hostname` >> /etc/hosts
This will fix the configuation error of your system and the »Configuration failed« error should dissapear.
What do I do if the error message is »The configuration file now needs a secret passphrase (blowfish_secret)« shows up?
This message may appear since XAMPP for Linux 1.2 was
released. Since version 2.5.2, phpMyAdmin supports the
encryption of cookie-saved passwords.
Solution:
Edit config.inc.php at line 60. You find this file in the phpmyadmin directory of your XAMPP installation. The line should look like this:
|
Enter in this line a password-like word or phrase, for example:
|
That's all. You should now be able to use phpMyAdmin in the same way as before.
What do I do if the error message is »cannot restore segment prot after reloc: Permission denied«?
I assume you are using Fedora? Since version 4 - I think - SELinux is activated by default and this is preventing the succesful start of XAMPP.Solution:
At the moment I only know one solution - deactivating SELinux:
|
Now XAMPP works fine again. If you know a better solution, please email me. I'm no SELinux expert and the only I know about SELinux is how to disable it. ;)
3. Running XAMPP
After I rebooted my Linux box XAMPP stopped running! How can I fix this?
Correct. That's normal Linux behaviour (which applies to any
other Unix-like system. It's the admin's job to make sure a
particular application is started at bootup.There is no real standard way to configure the boot process of a Linux system, but most of them should allow you to start XAMPP at boot time using the following steps.
-
First, find out your default runlevel.
Simply type egrep :initdefault: /etc/inittab.
You should no see a line containing a number between two colons.
In most cases 3 or 5 (2 if you're using Debian). - Go into the directory which configures this runlevel.
If for example your runlevel is 3, then you have to
change into the /etc/rc.d/rc3.d directory.
If your system didn't provide /etc/rc.d/rc3.d please try also /etc/init.d/rc3.d and /etc/rc3.d.
- Now carry out the actual configuration by typing:
ln -s /opt/lampp/lampp S99lampp
ln -s /opt/lampp/lampp K01lampp
ln -s /opt/lampp/lampp /etc/init.d/lampp
And than use the runlevel editor (expert mode) from YaST to activate XAMPP for the specific runlevels.
How can I make my XAMPP installation more secure?
In the default installation, XAMPP has no passwords set and
it is not recommended to run XAMPP with this configuration
accessible by others (e. g. on the Internet).Simply type the following command (as root) to start a simple security check:
/opt/lampp/lampp security
Now you should see the following dialog on your screen (user input is highlighted):
LAMPP: Quick security check...
LAMPP: Your LAMPP pages are NOT secured by a password.
LAMPP: Do you want to set a password? [yes] yes (1)
LAMPP: Password: ******
LAMPP: Password (again): ******
LAMPP: Password protection active. Please use 'lampp' as user name!
LAMPP: MySQL is accessable via network.
LAMPP: Normaly that's not recommended. Do you want me to turn it off? [yes] yes
LAMPP: Turned off.
LAMPP: Stopping MySQL...
LAMPP: Starting MySQL...
LAMPP: The MySQL/phpMyAdmin user pma has no password set!!!
LAMPP: Do you want to set a password? [yes] yes
LAMPP: Password: ******
LAMPP: Password (again): ******
LAMPP: Setting new MySQL pma password.
LAMPP: Setting phpMyAdmin's pma password to the new one.
LAMPP: MySQL has no root passwort set!!!
LAMPP: Do you want to set a password? [yes] yes
LAMPP: Write the passworde somewhere down to make sure you won't forget it!!!
LAMPP: Password: ******
LAMPP: Password (again): ******
LAMPP: Setting new MySQL root password.
LAMPP: Setting phpMyAdmin's root password to the new one.
LAMPP: The FTP password is still set to 'lampp'.
LAMPP: Do you want to change the password? [yes] yes
LAMPP: Password: ******
LAMPP: Password (again): ******
LAMPP: Reload ProFTPD...
LAMPP: Done.
(1) Setting a password will protect the XAMPP demo pages (http://localhost/xampp/) using this password. The user name is 'lampp'!
After calling this command your XAMPP installation should be "secure". For my part I've no idea what else could be insecure.
How do I activate eAccelerator?
(since XAMPP for Linux 1.4.12)To activate eAccelerator simply find the following lines in your /opt/lampp/etc/php.ini:
|
Remove the semicolon at the beginning of each line and restart XAMPP. eAccelerator is now active. For more information
about eAccelerator, check the eAccelerator home page:
http://eaccelerator.net.
How do I activate the OCI8/Oracle extension for PHP?
(since XAMPP for Linux 1.3)To activate the OCI8/Oracle extension for PHP please execute the following command:
/opt/lampp/lampp oci8The following dialog will start:
|
Now the extension should be active. I have only had a few chances to test this feature, so please report if this worked for you or not: oswald@apachefriends.org.
How do I backup/restore my XAMPP system?
Since XAMPP for Linux 1.4.2 you can make easily backups of your XAMPP data.| Warning: The backup and restore functionality is still under development and may not work correctly.
Attention: There is a small but annoying bug in version 1.4.2 of XAMPP. Please take a look |
here
That's a special problem with some Linux systems. Please open your /opt/lampp/etc/httpd.conf and look for these two lines:
|
|
Step 2: Take care of your backuped data
The file /opt/lampp/backup/xampp-backup-22-01-04.sh (in the example above) contains your backuped data. Get this file to a save place.Step 3: Restore your backuped data
On the new machine you need the same version of XAMPP as on your original/source machine.Call (as root):
sh xampp-backup-22-01-04.sh
You shoud see something like this:
|
That's all. As you can read you may need to restart XAMPP.
It should work perfectly (I tested it many times) but remember it's a beta feature.
4. Stopping XAMPP
5. Deinstall XAMPP
6. XAMPP's future
Whats about JSP support in XAMPP?
Nein, jedenfalls mit grösster Wahrscheinlichkeit nicht. XAMPP würde dabei um
etwa 42 MB auf über 60 MB anwachsen (38 MB fürs Java 2 SDK und 4 MB für Tomcat).
Im Moment bin ich davon überzeugt, dass es das nicht wert ist.
What brings the future?
In one of the next releases I will include a first version of my
Apache administration tool called Apanatschi. At the moment I'm still developing so
the exact release date is still unknown. In the first step it would be possible to do some
basic configuration (like virtual hosts) with Apanatschi and in the later releases support
for BIND and Postfix will follow.
