upgrading from Apache 1.37 to 2.2

I have apache 1.37 installed and i'm thinking if there is any need to update to apache 2.2

any new "Good" features with new version ?

any current things might be affected in the process ?

i'm running cpanel 10 and i think i'll have to upgrade to cpanel 11 to use apache 2.2 but this shouldn't be an issue

need advice

 

The best features in updated versions is the patches to security vulnerabilities

 

This is already a standard feature in every software update

I mean what else ?

example. any resource usage change ?

any thing i can gain after the update ?

any thing i will lose ?

 

Security for the 1.x and the 2.x branch are about the same...

2.2. is faster, at least in our experience it can handle more requests. config is slightly different, st least for the default apache 2.2 setup.

I think 2.2. does not work with cpanel (at least not on our servers with cpanel 11), correct me if I am wrong

 

Well, 2.2.x branch is a lot better...I've been using it on my DA server.
The main difference is management of child processes. 1.3.x is prefork while 2.2.x isnt and hence more faster and stabler.

 

I was told that cPanel 11 supports apache 2.2 but it's not stable with it yet and might crash the server so i'm sticking with apache 1.3 for the time being...

 

Sorry for bumping an old thread but I came searching today with the same question as the OP.

Has the cPanel & Apache 2.2.x relationship been ironed out? Is it time to upgrade or if everything seems to be working fine as-is with 1.3.x then should I just stick with it?

I saw references to 2.2.x being 'faster and stabler' so of course that has my attention.

 

Hello

I have to say something, because I had tried
Apache 1.3
Apache 2.0
Apache 2.2 on my server.

Let me say it

You need to update cPanel to version 11 CURRENT build.
Upto cPanel 11 STABLE build,the Apache installer is called , BuildApache (I think so, correct me if not)

But CURRENT version has got a new installer,called EasyApache 3

From my experience, I will not tell you to update to Apache 2.2.
But I will tell you to update Apache to version 2.0

I am using 2 on my server right now. I upgraded to 2.2 first and got about 40-50 problems , most of them are 500 Internal Server Error,
Coz the file permissions are changed in a random manner, I then chmod all to 755 and 644 for folders and php files. 2 days of hard work for getting every thing normal. Then I downgraded to 2.0 .
I am now using 2.0
Its very fast and there are lot of improvements
Here is the Server Singnature

Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.7a mod_auth_passthrough/2.1 mod_jk/1.2.25 FrontPage/5.0.2.2635 mod_bwlimited/1.4 PHP/5.2.3 Server at www.suntexhosting.com Port 80

2.2 is buggy, Config is differnet and hard to understand on first time.
Apache 2.2 will work with cpanel 11.

Yes, 2.2 is not such stable, but 2.0 is stable, and better than 1.3. Use that.

Update to Apache 2.0 if possible,
Also If you don't want to face the problem which may occur after the wrong configuration then please dont do it. Apache 1.3 is fine

 

Also, If you are trying to upgrade to Apache 2 then use PHP 5

 

I know this isn't related to cPanel, but one nice new feature of Apache 2 is worker mode compared to pre-fork mode.

Unfortunately, some PHP extensions are not thread-safe and there is no official list of which ones are and which ones aren't. Hence Apache2 in worker mode is not safe to use with PHP. Apache2 in prefork mode is fine.

 

If you are running cPanel I would recommend you do not switch to Apache 2.2 or Apache 2 for that matter until easyApache 3.0 reaches Stable (October 30th estimated at this time).

It has gone well for most but there have been several people doing the conversion that lost things like the www aliases on domains, SSL configuration gone ect.

I just think for something as big as this Apache change is let it reach Stable which should mean it is working 100% for most. The same deal with cPanel 11 basically. A lot of people switched earlier and it worked fine but others it destroyed thens and lots of parts were broken. Once it hit Stable it was pretty good for Release and Current as well.


That's what I think anyways and that is what we're doing with our servers. We've ran some test builds and it went fine but frankly still not trusting it at this point. The big thing for us is we've always compiled PHP5 ourselves but the new easyapache can do it for you. Well it hasn't gone smooth for everyone and we can't risk it not working and trying to figure out why or trying to revert which has broken things for people as well. Better safe than sorry

 

Yes, he is telling true. I got some problems with EA3 ,SeverAlias
I had corrected it manually by editing httpd.conf and it took about 3 hours for checking all.

If you are not sure, then stay with Apache 1.3.
Anyway, I have Apache 2.0 installed and now working fine with PHP5

 

I got an error when my server reached 400 domains

Then I contacted cPanel. The problem was with Apache version 2 and OpenSSL. Here is the email I received from the cPanel tech.

Solution : Downgrade to 1.3

 

You could have just as easily installed a newer version of openSSL (not hard to do). Which would solve the problem and allow you to continue to run Apache 2

 

You should consider upgrading your server first to apache 2. Then advice me lol

 

You've already ran the scary part running the easyapache3 rebuild script.

As for us running Apache2, well next week we will be starting to test it and see how well we can migrate things. We've already got a machine setup with accounts that we created doing a copy of an older machine so we have old content and essentially real live sites without them actually being on the machine. Assuming it can do the conversion without issue we may be running Apache 2.2. with cPanel controlling PHP4 and PHP5 before easyapache 3 even hits stable.

It'll be nice to finally not be doing custom compiles of PHP5