EasyApache 4

[pierre]

Thank you.

I opened a ticket ( #HWU-271-99583).

[info]

Hello, is that normal that php version are not updated (7.0.8 for example).
Thanks

[bogdan.sh]

It should be updated together with other system packages when cPanels upcp is run. But you may want to update manually https://www.cloudlinux.com/cloudlinu...hp-updated-1-5 .

[dave]

With EA4 being stable with cpanel 11.58, is the Cloudlinux integration with EA4 stable yet?

[info]

Im sorry, I don undestand. Im using easyapache 4, so I think I need to use easy-apache repository from cloundlinux:

http://repo.cloudlinux.com/cloudlinux/EA4/6/updates/x86_64/

But here I see only 7.0.8

Thanks

[mail]

Hi,

As Dave said.
With EA4 being fully released now, is CloudLinux classed as stable with EA4?

Thanks

[karl]

OK Lets go over what we know and where we appear to be at;

- EA3 that fully supports CL PHP Selector will expire September 2017 after which there will be no new updates from cPanel sources.
- The last cPanel version to support EA3 will be v60 anticipated for September 2016.
- Users running EA3 and CL PHP Selector will be blocked from upgrading to cPanel v62 which will release probably in December 2016 / January 2017.
- The current EA4/MultiPHP that cPanel supplies in 58.0.20 is rubbish compared to the CL EA3/PHP Selector and looks like it has little chance of ever getting anywhere close to feature parity by the time that EA3 goes EOL.
- We have had no news from CL about their spin of EA4 and if it will ever leave the beta development stage, or about anything else to do with this topic (that I started well over a year ago) !!
- The disconnect between cPanel staff and their endorsement of CL seems to be widening by the day.

Come on guys, this is our livelihood you are playing with here – at least have the ethics and courtesy to let us know what is happening – even if that is not much

[mtindor]

I agree with Karl. A few things concern me.

1. cPanel has a "hardened" kernel available now, meant to deal with the symlinks issue
2. cPanel has EA4 + MultiPHP (to deal with the longtime outcries for support for multiple versions of PHP)

CloudLinux had all of this taken care of a couple years ago. Sure, in order for people to benefit they had to pay for a CL license and install CL. And I do understand that cPanel likely has many many customers who do not use CL. So naturally cPanel had to come up with something to appease their customers who do not use CL.

But now there is a huge base of CL users, including a likely huge base running CageFS+PHP Selector. All of us who have adopted PHP Selector are used to it. Whether we love it or hate it, when compared to what is currently offered [and being marketed as production quality] by cPanel cannot compare to the ease of configurability of accounts with PHP Selector. I dont want to have to move away from PHP Selector. In the past [Igor, I believe] mentioned that at some point down the road, when CL felt that EA4+MultiPHP was refined enough, that CL may drop their PHP Selector. I would certainly like to know if this is still something that CL is planning to do in the future. And, if so, how far into the future can be expect continued full-blown PHP Selector support to continue?

Early on cPanel seemed to encourage/nudge its customers toward adopting CloudLinux (likely because of security). But now, I just get this feeling that there is a disconnect between cPanel / CloudLinux as far as their future together.

I understand that EA4 is inevitable. I just have to wonder if hosts who hosts hundreds or more accounts per server will ever be able to have confidence in the EA3/EA4 conversion, or we all simply need to plan for/expect a lot of breakage and then feel relieved and lucky if we do not experience issues. And when (not if, but when -- we will have no choice) we do migrate to EA4, if things start breaking are we going to need to contact cPanel or are we going to need to contact CloudLinux?

Before I even attempt to do an EA4 conversion,I need to know up front whose door I will need to bang on for assistance, and Ill need to know that they are ready to support the hell out of us during that process so that our customers sites arent down for 15 hours.

Nothing in the documentation for EA4, either through cPanel or CloudLinux, gives me any confidence of a smooth migration. And if I shouldnt expect a smooth migration, then one / both companies should be documenting things that could / likely will go wrong and how to fix them so that we, as admins, can act quickly to fix any issues that arise.

After all, we arent privy to information regarding how badly a migration has went, what kinds of things needed to be done to fix it, etc. If an EA3 to EA4 migration isnt bulletproof, then we need to have some documentation to guide us through fixing things while we await help from cPanel or CloudLinux. After all, you never know if somebody is going to pick up your ticket in 5 minutes or 5 hours.

Listen, I love CL. I can sleep at night with CL. I havent had a server crash in ages, I havent had resources run away in ages. Machines consistently perform at a certain load level and never really fluctuate. Its a beautiful thing. I have nothing but good things to say about CloudLinux. And I absolutely realize that everytime something is changed in EA4 (or the EA3-->EA4 conversion process) by cPanel, CloudLInux is stuck having to catch up with those fixes/changes after the fact. I cant fault CloudLinux for that.

I would, however, like to hear CloudLinux respond with their thoughts on the EA3-->EA4 conversion, common issues that arise during such a conversion, and also give us some sort of guarantee on how long PHP Selector will be supported into the future.

Mike

[iseletsk]

The EA4 support should become production ready within weeks. As you know - we tend to keep things in beta for a long time -- until they are mature.
We have A LOT of people running EA4 already. It works, it works very well. We still encounter some minor things like:
* We have reported that apache configured to run on 8080 was reconfigured to run on port 80 after the upgrade. So far we cannot replicate it, not sure what caused it
* mod_lsapi treats php.ini files in subdirectories differently from suPHP, which creates issues with MultiPHP (but not with PHPSelector/EA4) - fixed, in testing

Within last two weeks, we solved about ten other small issues like that. Some of them (most of them?) are not even related to CL, but to EA4 itself, and would be there on CentOS as well. It is just that we are very particular about naming things production.
Yet, we are pretty much at the end of the beta cycle. The rate of new errors dropped dramatically, while the number of people upgrading is speeding up with every day.

[mtindor]

Thanks for the update on EA4, Igor. Personally, I figured it would be quite a while for EA4 to be out of beta. Ive been using optimumcache for a long time now, and its still in beta even though its been working wonderfully for me in production.

Can you elaborate on my question about long-term support of PHP Selector? At this point in time, are you able to say how long CL will continue to provide PHP Selector? In the past you had suggested that, in the future if you felt MultiPHP worked as well as / provided equivalent features as PHP Selector, then CL might consider dropping development of PHP Selector.

So Im just wondering if we can expect to have PHP Selector available to us for years, or if we will be stuck in a year having to migrate people from PHP Selector to MultiPHP.

Mike

[iseletsk]

We will continue to provide PHP Selector until:
- MultiPHP has the same functionality (that might never happen)
AND
- we have easy/transparent migration from PHPSelector to MultiPHP

We are not going to abandon it in any way or form.

At this stage we made PHP Selector to work with MultiPHP (like you can select one way or the other, etc...)

[mtindor]

You guys are rock stars!

Tnx

Mike

[karl]

They ARE rock stars and their ideas and code are fantastic.

I just wish they would remember to let us mere mortals know what was going on from time to time, instead of us having to make provocative posts to elicit some scraps of information. I think they need some extra Public Relations staff to cope with us Grumpy Old Men !

Having said that, I shall now crawl back under my rock for a few weeks - my very best wishes to all the CL team
Kindest regards
Karl Fleming

[mtindor]

Karl,

Youre probably right about public relations. Im glad that Igor responded though, and I have confidence that they wont leave us hanging. Now I need to go find somebody else to complain to

Mike

[karl]

So there I was, contemplating CloudLinux and Existentialism, and I have to wonder if there isn an easier way of going about an RPM based web server.

Why not just ignore "EasyApache 3/4/dream-on" and produce an RPM based, optimized, CloudLinux httpd (Apache, nginx - whatever works best) that can be installed as an alternative to EA and fully supports (enhances?) CageFS, LVE and PHP Selector, and is updated by Yum once a day as necessary as part of upcp ?

Am I missing something here ? It seems such a simple solution, but maybe I haven grasped the intricacies of the EA httpd integration into cPanel.