If you're going to run 4.x, at least run the latest versions of it.
4.4.x is stable enough, has been out for months already. NOT running 4.4.x means you are indeed running a vulnerable setup. Plenty of holes were fixed and found in the 4.4 series.
As far as why the alert? Not sure, really. I'm running php 5.0.5 (modernbill doesn't support 5.1.x and completely craps out when it's used) and get it myself, soooo, I doubt it's a php5 warning. Recompiling apache now, we'll see if that helps
This thing is crazy. I have a VPS test bed I run the latest of everything on an it upgrade3d to XX.36 but still has the red box. My dedicateds running latest php 4.4.x don't show the red box or warnings at all. Only difference is they are on RedHat and the VPS is a CentOS.
Gee I wish the cPanel folks would let us know what EXACTLY is going on...
I also got a new set of errors on the VPS build
make: *** [sapi/cgi/php] Error 1
make: *** Waiting for unfinished jobs....
make: *** [sapi/cli/php] Error 1
make php-5.1.4...(install).... . . . . . . . . .
But it doesn't upgrade to 5.1.4 for love nor money nor retries! Still at 5.0.5
Gee I wish the cPanel folks would let us know what EXACTLY is going on...
I also got a new set of errors on the VPS build
make: *** [sapi/cgi/php] Error 1
make: *** Waiting for unfinished jobs....
make: *** [sapi/cli/php] Error 1
make php-5.1.4...(install).... . . . . . . . . .
But it doesn't upgrade to 5.1.4 for love nor money nor retries! Still at 5.0.5
Last edited:
Yeah, I was getting ready to really have a sucky night if I had to make sure php5 worked on my client sites.
So very glad some of your are running the guantlet for us
Z
So very glad some of your are running the guantlet for us
Z
A few of us have already noticed that it wanted to select PHP5 by default as well as Frontpage. I recompiled again selecting PHP 4.4.2 instead of the 4.4.1 that I was running and the "unlock" icon for PHP changed to locked. So apparently it wants you to use the latest version of PHP, whether it be 4 or 5. So if you use PHP4, use 4.4.2 and that should fix that part of the error message.
The Frontpage error is different, at least for me. So I recompiled again with Frontpage disabled in the selection list, and the error message went away! So now I am compiling it AGAIN with Frontpage enabled to see if will force the newest Frontpage module to update and keep the error message away.
Your mileage may very...
The Frontpage error is different, at least for me. So I recompiled again with Frontpage disabled in the selection list, and the error message went away! So now I am compiling it AGAIN with Frontpage enabled to see if will force the newest Frontpage module to update and keep the error message away.
Your mileage may very...
We have had a number of clients attempt to upgrade to PHP 5.1.4 as a result of this, and things didn't look too good afterwards When downgrading to PHP 4.4.2, note that cPanel doesn't always seem to re-enable the mod_php4 module in the Apache configuration file (/usr/local/apache/conf/httpd.conf), and as a result you may need to edit this file to uncomment the relevant lines to fix things. If this happens, you'll know because all PHP files become downloadable, as they are no longer parsed.
It really would be good to see cPanel think about their releases in more detail. For a start, the message that appears in WHM is outdated, confusing and causes panic amongst clients. As system administrators, if we don't happen to login to WHM on a server very shortly after the "alert" appears, the first we know of it is when clients get in touch having broken their servers due to the bugs in the cPanel EasyApache system. It does seem that we spend a larger amount of time than should be necessary running around after cPanel attempting to resolve issues that really shouldn't have existed in the first place.
Craig.
When downgrading to PHP 4.4.2, note that cPanel doesn't always seem to re-enable the mod_php4 module in the Apache configuration file (/usr/local/apache/conf/httpd.conf), and as a result you may need to edit this file to uncomment the relevant lines to fix things. If this happens, you'll know because all PHP files become downloadable, as they are no longer parsed.It really would be good to see cPanel think about their releases in more detail. For a start, the message that appears in WHM is outdated, confusing and causes panic amongst clients. As system administrators, if we don't happen to login to WHM on a server very shortly after the "alert" appears, the first we know of it is when clients get in touch having broken their servers due to the bugs in the cPanel EasyApache system. It does seem that we spend a larger amount of time than should be necessary running around after cPanel attempting to resolve issues that really shouldn't have existed in the first place.
Craig.
Last edited:
It's bound to be something with latest php. I got the FrontPage to compile to new but it still won't compile the 5.1 php so still a nice red box...gee I love this job.
The previous post may have been right though since the dedicateds are running the latest 4x and have never shown a warning even though they are showing the available upgrade for FrontPage.
The previous post may have been right though since the dedicateds are running the latest 4x and have never shown a warning even though they are showing the available upgrade for FrontPage.
I have been trying to sort my system out all day. When I first got the error message, it took some time to figure out that I need to compile to the latest PHP4 version to fix the PHP part of the error message. Once I did, it locked the lock on the error display.
But it was still showing Frontpage needed updating. So I ended up recompiling with 4.4.2 selected but Frontpage UNchecked. That cleared the error message. So I recompiled again with Frontpage enabled, and although the error message is still gone, when you view phpinfo.php, it doesn't show Frontpage 5.0.2.2635 as being configured under "Apache Version" of the "apache" section.
How do I get it to compile the Frontpage module back into it?
But it was still showing Frontpage needed updating. So I ended up recompiling with 4.4.2 selected but Frontpage UNchecked. That cleared the error message. So I recompiled again with Frontpage enabled, and although the error message is still gone, when you view phpinfo.php, it doesn't show Frontpage 5.0.2.2635 as being configured under "Apache Version" of the "apache" section.
How do I get it to compile the Frontpage module back into it?
Got error:
make -j 4 apache_1.3.36..............Done
make[2]: *** [target_static] Error 1
make[1]: *** [build-std] Error 2
make: *** [build] Error 2
make apache_1.3.36...(install)....Done
make[3]: *** [target_static] Error 1
make[2]: *** [build-std] Error 2
make[1]: *** [build] Error 2
make: *** [install-all] Error 2
make -j 4 apache_1.3.36..............Done
make[2]: *** [target_static] Error 1
make[1]: *** [build-std] Error 2
make: *** [build] Error 2
make apache_1.3.36...(install)....Done
make[3]: *** [target_static] Error 1
make[2]: *** [build-std] Error 2
make[1]: *** [build] Error 2
make: *** [install-all] Error 2
Insecure Apache
I've also been running into this problem over the past few hours. I'm continuously updating apache but all in wain all I got is my apache all messed up. The version of PHP is 5.1.4 upgraded from Cpanel only. Apache on the server is not coming up and I'm also getting messages as "Unable to obtain apache version information. Your apache server at xx.xx.xx.xx may be down, or unreachable. Any help is appreciated.
I've also been running into this problem over the past few hours. I'm continuously updating apache but all in wain all I got is my apache all messed up. The version of PHP is 5.1.4 upgraded from Cpanel only. Apache on the server is not coming up and I'm also getting messages as "Unable to obtain apache version information. Your apache server at xx.xx.xx.xx may be down, or unreachable. Any help is appreciated.
all mine worked fine with 4.4.2
Also, I get no error warnings anymore. I would stay away from 5 as I read many folks are having trouble with it...
Also, I get no error warnings anymore. I would stay away from 5 as I read many folks are having trouble with it...
Gr8Support,
Try loading "http://yourserverdomainname:2086/scripts2/buildapache" and selecting PHP 4.4.2, enabling Frontpage Module (and GD/Freetype if you used them) and then "Start Build". You may find that that will restore your Apache to a running configuration.
Try loading "http://yourserverdomainname:2086/scripts2/buildapache" and selecting PHP 4.4.2, enabling Frontpage Module (and GD/Freetype if you used them) and then "Start Build". You may find that that will restore your Apache to a running configuration.
Can you check your server's phpinfo.php page and see if you still have Frontpage 5 listed in the "Apache Version" portion of the "apache" section?JimboJ40 said:Using WHM to do upgrade via link and loading previous settings worked fine on my servers with PHP 4.4.2 first time round... no more warning message. - -
