Puppy Linux Discussion Forum

[prit1]

What are the outputs from

[prit1]

Thom,

What version of Puppy are you using? I tested this on 4.2.1 and 4.3 Beta and it works well. However I tested this on 4.2 SMP and it did not work. It gives a error "error redirecting stdout".

[tlchost]

[prit1]

I just finished testing in 4.2retro and 4.21retro and it worked fine.

[tlchost]

[prit1]

Thom,

Can you post the output from running /etc/init.d/rc.httpd stop and /etc/init.d/rc.httpd start ?

[growler]

A few thoughts:

1. Check that mysql is running - check the processes and see if there is a mysql - or from a command line rxvt try

ps -ef|grep mysql

or type

mysql -uroot -pwoofwoof

this should return the mysql client program for entering sql to administer databases.

I am wondering if the .pet that you installed is in fact the full LAMP one or just the hiawatha - this would explain why you get the static hiawatha test page but not the php one. If you have mysql going then this confirms you have the LAMP .pet

2. We know hiawatha is running because you have output of index.html hiawatha test page. Are the three php daemons running type

#ps -ef|grep php

at the command line - there should be three lines showing php-fcgi processes. I suspect these kids are not running for some reason.
If not....
type:

#/etc/init.d/rc.httpd stop
#/etc/init.d/rc.httpd start

to stop then start hiawatha (and associated php-fcgi daemons)

check to see if php-fcgi is now going

#ps -ef |grep php

look for the three php-fgi processes

still no go?

3. Check the output of attempting to run php-cgi from the command line - type

#php-cgi > /root/outputofphp.txt

Then post the output here.

[growler]

double post whoops!

[growler]

three times just to be sure!

[tlchost]

[growler]

Is your LAMP_6.16-5.1.35-5.2.9.pet around 11 Meg!

Hiawatha on its own is just 116k so there would be quite a size difference between a hiawatha.pet and the "whole enchilada" - the real meat (do enchiladas contain meat?) is in mysql - PHP would be about a Meg compressed.

You can have a look at the contents of the .pet you are running by making a copy of it and renaming it - taking off the .pet and adding .tar.gz then looking at the archive in archiver. This will tell you if you have mysql files and php in there. If you are not running the above .pet then it is unlikely you'll have the files

/etc/init.d/rc.mysqld
/etc/init.d/rc.httpd

these kids are the ones that start the daemons on boot and are only part of the LAMP .pet above.

Just to confirm the PHP Mysql Hiawatha (LAMP) pet is at:

http://dotpups.de/puppy4/dotpups/Internet/LAMP-6.16-5.1.35-5.2.9.pet

[tlchost]

[growler]

Running out of ideas - I need to try to install on a USB stick and see if I get the same error.

Looks like there may be some permissions issue with USB install for hiawatha - it runs as nobody - there could be permissions issues. I am not too clear on the inner workings of USB installs but I am thinking this is a factor.

[prit1]

Uually I've seen the "error binding to port 80" error when an instance of Hiawatha is already running or when some other program is using to serve through port 80.

[tlchost]