Upgrading to the latest edge (whm11) is giving error 500 on apache

[a66fm]

i'm using centos 4.3 and when i upgrade to the latest edge (whm11) i get error 500 on all sites and no error is getting logged.
Is anyone having the same issue?

 

[cinusik]

I had almost the same as this update messed up a http.conf file a little.
For me it was line AddModule mod_php5.c commented out so php stops working right after upcp. Probably the same happened to you, or maybe you have commented other line or you have it messed up in other way.

 

[appleboy]

wierd i updated to edge:

WHM 10.8.0 cPanel 11.0-E484
FreeBSD 5.5-STABLE i386 - WHM X v3.1.0

and get this:

Unsupported Version You are running an old version of cPanel that is no longer supported. You can upgrade to the latest version at no cost by clicking the link below:
Please Click Here to Upgrade


Updated to Edge: 4:20pm PDT

 

[carluk]

edge is using the new easyapache with apache 2 being default and is nice a buggy with php not working (from my last try).

 

[a66fm]

i tried for almost an hour to rebuild apache (from ssh) using the "new" default (ver2), went back to apache 1.36 tried all the default rebuild options, i even tried the "failsafe" one, i also thought of disabling suexec but the only thing that did work was falling back to the current build and rebuilding apache again

 

[cix]

I got some different problem:

I´ve updated my CPANEL RELEASE to EDGE and ran easyapache.

So this is what I got after compiling the new apache 2.0.x:

You are currently running Apache 2.0.59

Step 1) Set the Apache version you want to build and run
1.3.37
Current Selection 2.0.59
2.2.3

but on Apache Server Status, shows:

Server Version: Apache/1.3.37 (Unix) mod_auth_passthrough/1.8 mod_bwlimited/1.4 mod_log_bytes/1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a PHP-CGI/0.1b
Server Built: Aug 15 2006 14:33:50


So I´ve needed to recompile, after that, apache 2.0.x works.

 

[Spiral]

Just a side note ....

I strongly recommend that anyone running mod_security or other extra modules
that you disable and / or remove those modules prior to trying to make the
upgrade jump up to Apache2. Will make your life a lot easier.

 

[MN-Robert]

11 edge is sh*t, it's not worthy of edge.

 

[chirpy]

If you don't want the hassles then you should not be running EDGE or CURRENT. IF you do run them, then you should let cPanel know of any problems by using bugzilla. Otherwise, you should be using STABLE or RELEASE if you don't want the hassles of the newer trees.

 

[BPrintz]

What's the command to downgrade your current version of CPanel - I just want to get rid of this problem.

 

[Curious Too]

What's the command to downgrade your current version of CPanel - I just want to get rid of this problem.

Downgrading won't work, I already tried that. If you just need to get Apache going again, uncomment the add_module line for php4 in the httpd.conf file. For some reason the latest edge comments out that line.

 

[BPrintz]

Thanks I'll give it a go... but just for reference how do I downgrade CPanel to stable?

 

[MN-Robert]

If you don't want the hassles then you should not be running EDGE or CURRENT. IF you do run them, then you should let cPanel know of any problems by using bugzilla. Otherwise, you should be using STABLE or RELEASE if you don't want the hassles of the newer trees.

We use it on a few test servers, I honestly can't believe they have released cpanel 11 in edge. So bug riddled. It's bullsh*t

 

[a66fm]

it has worked for me 3-4 times in a row so it must work for you.
just select from whm>Update Config select "current" or "RELEASE" and do a

/scripts/upcp --force

from ssh.

i managed to have apache 2.0.59 working but i culd not enable exif and mod security

 

[Curious Too]

it has worked for me 3-4 times in a row so it must work for you.
just select from whm>Update Config select "current" or "RELEASE" and do a
from ssh.

i managed to have apache 2.0.59 working but i culd not enable exif and mod security

I force downloaded to current and still received the error message in whm and php still did not work. I am ignoring the error message for now and had to uncomment the add_module statement in httpd.conf in order to get php working again.

 

[chirpy]

CURRENT is effectively at the same level as EDGE so you won't see much difference. As I said, you'll have to go to STABLE or RELEASE.

 

[carluk]

We use it on a few test servers, I honestly can't believe they have released cpanel 11 in edge. So bug riddled. It's bullsh*t

Seriously get a clue. If you have any problems submit the bug report to cpanel rather than whine on these forums saying rubbish like the above. If it was either stable or release I might understand but it's edge.


To to go to stable/release just edit the update type via WHM or edit the /etc/cpupdate.conf file and replace the edge text with release, or remove it completely so it's just manual for stable. Then

 /scripts/upcp

 

[jamesbond]

I thought the BETA version was supposed to be used for bug reporting

 

[MN-Robert]

Seriously get a clue. If you have any problems submit the bug report to cpanel rather than whine on these forums saying rubbish like the above. If it was either stable or release I might understand but it's edge.

Not sure why your attacking me Carl. We've raised many bug reports, etc over the years and some still remain unresolved after a year. Edge is to be tested, it's how they get to stable. Hey look, you even agree with me:

http://forums.cpanel.net/showpost.php?p=240543&postcount=17

Going through the bug list and fixing all the bugs! Especially from 04/05.

I've given up submitting tickets/bug reports to cpanel because they don't get resolved in a timely manner. You should know that's why we are looking at other panels. Can someone tell me what cpanel have done in the last 12 months. I mean seriously, apache2 is still crippled (even after the farce of 15 different eta's) they are re-writing the api etc etc for cpanel but apart from that what has been done? 1700 odd bugs still in bugzilla. Why are they working on adding game servers, 3rd party application installers and other new features when the existing features don't work correctly.

It's a shame, but cpanel and it's related issues cause 90% of the tickets we get in our system. If a reseller/you delete a dns zone but not the account it disappears from the list and it needs system admin intervention to fix it. I could probably document 50 problems off the top of my head.

--

If Chripy or another mod wishes to spilt this I would appreciate it. I was looking for honest answers three months ago when I posted this: http://forums.cpanel.net/showthread.php?t=53143 but it seems nothing is being done. Most software has a timeline/roadmap on where it will be in x months or x years. So my question to Nick/Dan is where do you see cpanel at the end of 2007?

 

[carluk]

Not sure why your attacking me Carl. We've raised many bug reports, etc over the years and some still remain unresolved after a year. Edge is to be tested, it's how they get to stable. Hey look, you even agree with me:

Sorry if you cannot handle a different opinion from yours but I do not agree with your statements with regards to not believing they released edge and it happens to be bug riddled. The only major bug I have come across so far which wasn't in a previous build is the easyapache problems. I do not agree with your assessment of my agreeing with your statement either, you should infact compare that statement you quoted with yours and you shall see the differences between moaning about a buggy edge release (which is just above beta in the cpanel tree), and posting in a thread asking what new features etc we'd like and simply requesting some of the bugs in the tracker be fixed. "Edge is to be tested" and "I cant believe they released 11 in edge, as it's riddled with bugs" - nice slight contradiction there.

</Unsubscribed>