PHP not working still... WHY NOT FIX????

[rastoma]

WHY??????

WHY?????? can't someone tell me WHY PHP is not working on new installs?

2 more servers today wiped clean, fresh install of RH, install cpanel, everything works but PHP not parsing!

loaded buildapache afterwards... still no apache.... COME ON!!! I'M LOSING CUSTOMERS!!!!!!!!!

there have been too many people with this problem and ask questions with NO answers. the answers that have been given I have followed the links and tried the suggestions which basically involve reinstalling cpanel and/or buildapache... which DOESN'T WORK.

PLEASE.... can anyone offer any suggestions PLEASE?

 

[AlaskanWolf]

is it a dedicated server? if so from who?

 

[rastoma]

these are servers i'm colocating myself.

it just doesn't make sense. 2 weeks ago i start loading cpanel and everything went fine... php worked. i haven't changed anything by the way i'm setting these up and now php doesn't work! (meaning new installs... the first machines php is still working of course)

 

[moronhead]

[quote:235a519d5a][i:235a519d5a]Originally posted by rastoma[/i:235a519d5a]

WHY??????

WHY?????? can't someone tell me WHY PHP is not working on new installs?

2 more servers today wiped clean, fresh install of RH, install cpanel, everything works but PHP not parsing!

loaded buildapache afterwards... still no apache.... COME ON!!! I'M LOSING CUSTOMERS!!!!!!!!!

there have been too many people with this problem and ask questions with NO answers. the answers that have been given I have followed the links and tried the suggestions which basically involve reinstalling cpanel and/or buildapache... which DOESN'T WORK.

PLEASE.... can anyone offer any suggestions PLEASE?[/quote:235a519d5a]

Have you checked your httpd.conf for all the relevant lines after the Cpanel install (you don't actually need to install buildapache to make PHP work)? For example:

AddType application/x-httpd-php .php .phtml .php4
AddType application/x-httpd-php-source .phps

LoadModule php4_module libexec/libphp4.so

AddModule mod_php4.c

 

[rastoma]

yes, i have looked at all those components. i've also compared the httpd.conf from another cpanel server that is parsing php correctly and everything matches as far as loaded modules and directives.


it just doesn't make any sense.

 

[totalufo]

PHP is not working, I added the application ypes and HTTP started ok. After adding the module lines, HTTP fails. Any ideas? No error in the messages.

 

[feanor]

More than likely when these machines are actually compiling the guts of PHP and the related modules that cpanel provides in those builds by default, they are not making it THROUGH. Hence in the end PHP is non-existant coz the compiling is failing on various steps.

If you want help HERE, we'll need to see specific lines in which the compile is failing, OR tidbits of an error_log.... anything besides vague descriptions will be helpful, and the only way for someone here to have an epiphany of how to possibly help.

 

[totalufo]

Here's the error log at the time of the problem

[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_env.so uses plain Apache 1.3 API, this module might c$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_log_config.so uses plain Apache 1.3 API, this module $
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_mime.so uses plain Apache 1.3 API, this module might $
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_negotiation.so uses plain Apache 1.3 API, this module$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_status.so uses plain Apache 1.3 API, this module migh$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_include.so uses plain Apache 1.3 API, this module mig$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_autoindex.so uses plain Apache 1.3 API, this module m$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_dir.so uses plain Apache 1.3 API, this module might c$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_cgi.so uses plain Apache 1.3 API, this module might c$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_asis.so uses plain Apache 1.3 API, this module might $
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_imap.so uses plain Apache 1.3 API, this module might $
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_actions.so uses plain Apache 1.3 API, this module mig$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_userdir.so uses plain Apache 1.3 API, this module mig$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_alias.so uses plain Apache 1.3 API, this module might$
[Fri Feb 8 19:58:45 2002] [warn] Loaded DSO libexec/mod_access.so uses plain Apache 1.3 API, this module migh$

 

[feanor]

Backup your apache config and domlogs and anything else vital you have under /usr/local/apache , and then remove that directory altogether.

Then, install buildapache.sea and afterwards append your httpd.conf virtual host area to the end of the new httpd.conf (the fresh one)..... and put anything else back into the /usr/local/apache hierarchy that you may have needed to save.

bdraco uses this method and I have always had luck with it as well- I think he makes reference to it in other posts related to this.....

g00d luck

 

[totalufo]

What would you consider being valueable besides the obvious? Can I just tar up the apache directory? What's the best way to do this? I don't want to make any mistakes.

 

[feanor]

Tar'ing it up is a very good idea.
You'll need domlogs / the config files, and any certs/keys you might have within.....

Tar'ing is the best safeguard.

 

[bdraco]

AddType application/x-httpd-php .php3
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps


Make sure the above is in httpd.conf

 

[rego]

I had the same problem and found that the AddType lines were missing in httpd.conf. Once I added them and restarted services, php started working fine.