Page 1 of 1

XAMPP Status - DEACTIVATED but all working fine

PostPosted: 09. December 2011 05:40
by stewfeed
MySQL database DEACTIVATED
PHP DEACTIVATED
Perl DEACTIVATED
Common Gateway Interface (CGI) DEACTIVATED
Server Side Includes (SSI) DEACTIVATED

Is this normal for XAMPP for linux? All were mark as "DEACTIVATED" but when I access the site including phpmyadmin and https:// - all are working fine.

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 09. December 2011 09:42
by JonB
A. No, that is not 'normal' if LAMPP is running correctly.

B. Beyond that it is pretty hard to guess any more, as you didn't mention either your Linux Distribution or the version of XAMPP/LAMPP you are running. Please add that info to your profile in the User Control Panel, thanks...

C. I 'might have a thought', but it's a bit dependent on the missing info.

Good Luck
8)

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 09. December 2011 11:48
by stewfeed
I am running CentOS 5 and running XAMPP 1.7.7 and no problem during installation

Thanks.

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 09. December 2011 11:52
by Sharley
stewfeed wrote:I am running CentOS 5 and running XAMPP 1.7.7 and no problem during installation
Would you be so kind as to add your XAMPP version and Operating Sytstem to your profile as JonB requested:
viewtopic.php?f=17&t=48626
Thanks. :)

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 09. December 2011 12:17
by JonB
My LAMPP box is down for maintenance at the moment, so I can't test anything until later in the day. - but -

A. - how did you get to the XAMPP welcome page?

B. - by any chance did you change permissions, ownership or 'move' any of the 'lampp' components???

Thanks & good luck

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 10. December 2011 15:39
by JonB
try using this command to see what 'nobody' is really doing -

Code: Select all
sudo ps aux | grep nobody


[root@localhost ~]# ps aux | grep nobody
nobody 1345 0.0 0.5 46424 10804 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
nobody 1520 0.0 0.6 52572 12436 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
nobody 1524 0.0 0.6 52928 14132 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
nobody 1525 0.0 0.6 52928 14132 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
nobody 1526 0.0 0.6 52704 13672 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
nobody 1528 0.0 0.6 52572 12436 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
nobody 1610 0.0 1.4 193052 29588 ? Sl Dec09 0:27 /opt/lampp/sbin
/mysqld --basedir=/opt/lampp --datadir=/opt/lampp/var/mysql --plugin-dir=/opt/la
mpp/lib/mysql/plugin --user=nobody --log-error=/opt/lampp/var/mysql/localhost.lo
caldomain.err --pid-file=/opt/lampp/var/mysql/localhost.localdomain.pid --socket
=/opt/lampp/var/mysql/mysql.sock --port=3306
nobody 1647 0.0 0.0 8404 1424 ? Ss Dec09 0:00 proftpd: (accep
ting connections)
nobody 13190 0.0 0.6 52572 12456 ? S Dec09 0:00 /opt/lampp/bin/
httpd -k start -DSSL -DPHP5 -E /opt/lampp/logs/error_log
root 22818 0.0 0.0 4436 756 pts/1 S+ 09:36 0:00 grep --color=au
to nobody
[root@localhost ~]#


Good Luck
8)

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 08. March 2012 00:06
by dnsplus
I have the same problem. All the features of the XAMPP installation appear to to be working, however from the status page via a remote web browser, all items have the status of DEACTIVATED.

Several hours on google has not helped me clear this up.

Re: XAMPP Status - DEACTIVATED but all working fine

PostPosted: 08. March 2012 15:20
by JonB
I didn't get a reply on this other issue - so its not really a 'solved issue'.

I have a few questions -

1. Is this installation on a remote VPS?

2. Did you use the XAMPP/LAMPP security fix?

3. When you go to the XAMPP Welcome page, are you prompted for a password?

4. Does phpMyAdmin work correctly?

Good Luck
8)

Re: XAMPP Status - DEACTIVATED but all working fine [SOLVED]

PostPosted: 08. March 2012 18:41
by dnsplus
Hello Jon,
1. Yes, its a VM running on ESXi 4.1
2. Yes, i have run the ./lampp security script to set the permissions
3. Yes, i am prompted for the lampp user password
4. Yes, i am able to access the phpMyAdmin application using the credentials I created when i ran the security script.

I am using the SuseStudio service to create my appliance. As part of the configuration, I have uploaded the tar.gz package into the system, and I allow it to do the package extraction for me. Scripting the complete install and configuration has not been successful, so I just copy an xampp.txt file from my laptop (via scp) into the /etc/init.d folder. I chown and chmod the file, then chkconfig -add xampp and insserv xampp. After i do that, my services successfully start upon boot.

I think I am going to try a slightly different method here, and see what happens. Rather than upload the 1.7.7 archive into the studio before the appliance is built, I am going to manually copy, install and configure after the applicance has been built, downloaded, and converted into the virtual environment. I am certain that the installation will be successful, and if all the components are reported as activated, we will be able to conclude that there is 'something' about letting the studio do the work that is the cause of the issue. At least, the issue as i am experiencing it.

-- update --

I built a new VM without the archive prestaged. The manual installation was successful, however all the components are still showing deactivated.

-- update 2 --

Names matter. I had been under the impression that apache was going to answer to any name I put in my URL bar. Since this is a POC system, none of my application names have DNS entries. So, i happily edited my hosts file so that I could emulate actual DNS names.

The problem: Apache could not resolve the FQDN, or even the host/alias name of the URL i was using to connect. This resulted in rendering problems with some of the pages.

The solution: ADD the FQDN and Alias information into the local hosts file on the XAMPP server.

That's it. Thank you, drive through.