Migrating cloudlinux EA3 to EA4
i need to EasyApache 3 and switch to EasyApache 4
what troubles can i expect after upgrade/migration?
i run a lot of different websites on my server with different php versions and modules selected in PHP Selector and users use old versions of php like 4.4
is the new apache compiled with the same modules as it was ?
server runs php versions:
4.4/ 5.1/ 5.2/ 5.3/ 5.4/ 5.5/ 5.6/ 7.0/ 7.1/ 7.2 - are they still ALL present and working after migration to ea4 ?
is the migration to ea4 affecting the php versions - are they compiled new? ( still working the same way as before) are the php modules of customers still the same when activated inside "php selector" and php variables of customers?
what are your experiences running the migration script on a production server with a couple of hundreds accounts on it?
running:
CLOUDLINUX 7.5 cpanel v76.0.10
Linux 3.10.0-714.10.2.lve1.5.12.el7.x86_64 #1 SMP Fri Feb 9 00:27:48 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Server version: Apache/2.4.18 (Unix)
Server built: Feb 1 2016 18:34:29
Cpanel::Easy::Apache v3.32.9 rev9999 +cloudlinux
Server's Module Magic Number: 20120211:52
Server loaded: APR 1.5.2, APR-UTIL 1.5.4
Compiled using: APR 1.5.2, APR-UTIL 1.5.4
Architecture: 64-bit
Server MPM: prefork
threaded: no
forked: yes (variable process count)
# cd ~; wget
-
Hi @zye The documentation here goes over what to expect during the process: The EasyApache 3 to EasyApache 4 Migration Process - EasyApache 4 - cPanel Documentation Let us know if you still have concerns after reading through that information. As always if you run into any issues during the migration process we're always more than happy to assist with this. 0 -
my current cpanel version is 76.0.22
Is there a reason the version of cPanel is so old on that machine? While I have used that tool many times with no issues, the cPanel version is more concerning to me than the EA4 conversion.0 -
yes - ea3 is the limiting factor on updates - thats why i am stuck with v 76.0.22 i feared troubles and non working websites of customers and after reverting to ea3 after update complete mess so you used the script on a production server with customer data on it and everything worked afterwards? 0 -
Yes - that script has been used many times, both by me, and by other support techs. Is this a CentOS 7 machine? If not, it might be better to migrate to a new system. That way you could move the data over to the new machine, and test things there before changing the DNS. If something is wrong, you could adjust it without ever causing the live sites to go offline. 0 -
cloudlinux 7.8 0 -
Even though the system itself isn't out of date, you could always perform a migration so you don't have to make any changes to the current machine. 0 -
yeah 0
Please sign in to leave a comment.
Comments
8 comments