NickTheGreek

we decided to automate the whole process so we did this: CHECK ===== find /opt/cpanel/* -name zzzzzzz-pecl.ini -exec grep -Hn "imag" {} \; find /opt/cpanel/* -name imagick.ini -exec grep -Hn "imag" {} \; FIX ===== find /opt/cpanel/* -name imagick.ini -exec sed -i 's/extension=imagick.so/;extension=imagick.so/' {} \; /scripts/restartsrv_httpd /scripts/restartsrv_apache_php_fpm

I found a nice clean guide for imagick PHP through SSH here: https://help.bigscoots.com/en/articles/730428-cpanel-easyapache-4-installing-imagemagick-and-imagick-php-extension cPanel EasyApache 4 Installing Imagemagick and imagick PHP extension This is a quick guide on how to install both the imagick PHP extension as well as the application via SSH. Written by Justin Catello Updated over a week ago This is fairly simple, just copy and paste the following into SSH. 1. Installing imagemagick: yum -y install ImageMagick-devel ImageMagick-c++-devel ImageMagick-perl 2. Installing the imagemagick PHP extensions for all installed PHP versions. for phpver in $(whmapi1 php_get_installed_versions|grep -oE '\bea-php.*') ; do printf "\autodetect" | /opt/cpanel/$phpver/root/usr/bin/pecl install imagick echo 'extension=imagick.so' >> /opt/cpanel/$phpver/root/etc/php.d/imagick.ini done /scripts/restartsrv_httpd /scripts/restartsrv_apache_php_fpm 3. Test to make sure imagemagick is installed: /usr/bin/convert --version 4. Test to make sure the PHP extensions loaded: for phpver in $(whmapi1 php_get_installed_versions|grep -oE '\bea-php.*') ; do echo "PHP $phpver" ; /opt/cpanel/$phpver/root/usr/bin/php -m |grep imagick done PHP 54 imagick PHP 55 imagick PHP 56 imagick PHP 70 imagick PHP 71 imagick Problem with this guide is this command: echo 'extension=imagick.so' >> /opt/cpanel/$phpver/root/etc/php.d/imagick.ini done We noticed with our colleagues in angellight.com it causes duplicate SO entries in: php.d/zzzzzzz-pecl.ini:extension="imagick.so" php.d/imagick.ini:extension=imagick.so as it shows here: https://support.cpanel.net/hc/en-us/articles/360052373474-Severity-Core-Warning-Module-imagick-already-loaded-Unknown-0 Symptoms You see these errors appearing in PHP's log files: ERROR - 17/08/2020 18:48:48 --> Severity: Core Warning --> Module 'imagick' already loaded Unknown 0 ERROR - 17/08/2020 18:48:48 --> Severity: Core Warning --> Module 'imagick' already loaded Unknown 0 ERROR - 17/08/2020 18:48:49 --> Severity: Core Warning --> Module 'imagick' already loaded Unknown 0 ERROR - 17/08/2020 18:48:49 --> Severity: Core Warning --> Module 'imagick' already loaded Unknown 0 ERROR - 17/08/2020 18:48:49 --> Severity: Core Warning --> Module 'imagick' already loaded Unknown 0 Description This usually means that the module has been loaded more than one time i.e. there are at least two instances of the directive that loads the module in PHP's configuration files. This can occur when the module has been installed multiple times using different utilities (yum, pecl, etc). In our case the directive looks like this: extension="imagick.so" Workaround First, we need to identify what PHP version the domain (AKA VHost) is using. You can run this command to confirm the PHP version the domain is assigned to: uapi --user=$USER LangPHP php_get_vhost_versions | egrep -i domain -A 1 Here $USER must be replaced with the name of the user the domain belongs to. The output looks like this: uapi --user=cptest LangPHP php_get_vhost_versions | egrep -i domain -A 1 domain: foo.testing.com version: ea-php72 -- domain: sub.cptest.net version: ea-php72 -- domain: foo1.bar1.com version: ea-php72 You will see the PHP version each domain is using listed underneath the domain name. Now you need to go to this location: cd /opt/cpanel/ea-php##/root/etc Don't forget to change the PHP version (ea-php##) in the above path with the domain's PHP. And now if you recursively search for the module-loading directive from above, you should see more than one line showing up: grep -ir imagi * php.d/zzzzzzz-pecl.ini:extension="imagick.so" php.d/imagick.ini:extension=imagick.so You need to edit one of these files and comment out the line where the directive appears and then restart the PHP-FPM service from the WHM > Restart Services > PHP-FPM service for Apache interface. The error messages should now disappear.

so we were excited to start using Windows 11 and the issue when using VmWare workstation was only one - no network So i tried updating using tethered mobile connection, then used hardware ID to find another driver as Vmware tools did not solve this PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00\000C29FFFFF58EFB00 and nothing Worse is, i installed on KVM and all worked flawlessly ... so the problem was easy to solve in the end: edit VMX add the following: ethernet0.addressType = "generated" ethernet0.virtualDev = "vmxnet3" ethernet0.present = "TRUE" voila

this was not enough, had to exclude a few files and dirs more to make this work properly

wherever i visited it was made quite clear upgrading CentOS 6 to CentOS 7 is not a realistically viable option https://forums.centos.org/viewtopic.php?t=69363 and OVZ6 or otherwise OpenVZ aka Virtuozzo containers lack their kernel so migrating was between hard to not possible. https://www.lowendtalk.com/discussion/149162/migrate-from-virtuozzo-to-xen-or-kvm Well, we are happy to disagree since we managed to do the Virtualization equivalent of Magellan Circumnavigation after a week of hard work: we started with OVZ container running CentOS 6.10 and cPanel / WHM 11.86 with an upgrade blocker due to COS6 being EOL since November 2020. Managed by trial and error to migrate this container to a KVM clone running same CentOS 6.10 and all files cloned 1-1 with rsync. Then we run the magnificent yet underrrated Red Hat upgrade tool in the KVM virtual machine to upgrade to CentOS 7.0.1406 and had to recreate the missing grub2 entries since grub is no more on COS7. From that point onwards we managed to properly yum update to 7.9 and finally to fix cPanel RPM issues and run a full WHM upgrade to 11.94. In short : OVZ COS6 WHM 11.86 -> KVM COS6 WHM 11.86 -> KVM COS7 WHM 1186 -> KVM COS7 WHM 11.94 and are are running now at latest version with functionality surprisingly high if not almost full identical www.forumsandmore.com

certifications looking good now !!!

nano /etc/yum.repos.d/CentOS-Base.repo [base] name=CentOS-$releasever - Base #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra baseurl=http://vault.centos.org/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 #released updates [updates] name=CentOS-$releasever - Updates #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra baseurl=http://vault.centos.org/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 #additional packages that may be useful [extras] name=CentOS-$releasever - Extras #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra baseurl=http://vault.centos.org/centos/$releasever/extras/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 #additional packages that extend functionality of existing packages [centosplus] name=CentOS-$releasever - Plus #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra baseurl=http://vault.centos.org/centos/$releasever/centosplus/$basearch/ gpgcheck=1 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 #contrib - packages by Centos Users [contrib] name=CentOS-$releasever - Contrib #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=contrib&infra=$infra baseurl=http://vault.centos.org/centos/$releasever/contrib/$basearch/ gpgcheck=1 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6

When moving a KVM image to another server, it’s a pretty simple process. If you’re using SolusVM or Virtualizor, it makes it even easier. However, if you have a VM node which hosts openVZ containers and need to move them to a new node with different virtualization, QEMU/KVM in this case, it makes things a little more difficult. The main different between KVM and openVZ is the level of virtualization. OpenVZ is an OS level virtualization which means the hosts’ kernel is shared with guest containers inside it, you can’t use your own kernel. KVM is very different. It’s a full virtualization. The whole OS and its kernel is virtualized so you can even install an OS with its own kernel in it, like installing Windows VM inside a linux host. So let’s get on with this tutorial now that we have a little background. Please proceed at your own risk! – Converting OpenVZ to KVM box Let’s start the moving process. 1. The first step before start moving the box is installing a KVM box with the exact same OS as the openVZ container, preferably same point revision too (You will want to run yum update on both VM’s to make sure) 2. SSH into both VMs. 3. In the KVM box, or openVZ box, install mingetty. I’m using CentOS 6.2 so I use yum to install mingetty yum install mingetty 4. Edit /etc/inittab in the VM installed with mingetty vi /etc/inittab and add these lines # Run gettys in standard run levels 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 This will enable the machine to actually get a logon prompt. 5. Install rsync on both VMs yum install rsync 6. From the openVZ box, make a text file containing files to exclude. This will preserve settings in KVM box to make sure the VM is bootable. nano /root/exclude.txt add these lines to exclude.txt, you may customize it to your needs /boot /proc /sys /tmp /dev /var/lock /etc/fstab /etc/mtab /etc/resolv.conf /etc/conf.d/net /etc/network/interfaces /etc/networks /etc/sysconfig/network* /etc/sysconfig/hwconf /etc/sysconfig/ip6tables-config /etc/sysconfig/kernel /etc/hostname /etc/HOSTNAME /etc/hosts /etc/modprobe* /etc/modules /net /lib/modules /etc/rc.conf /usr/share/nova-agent* /usr/sbin/nova-agent* /etc/init.d/nova-agent* /etc/ips /etc/ipaddrpool /etc/ips.dnsmaster /etc/resolv.conf /etc/sysconfig/network-scripts/ifcfg-eth0 7. Now we can start to sync the OpenVZ box to the KVM box. In the openVZ box, type: rsync –exclude-from=”/root/exclude.txt” –delete –numeric-ids -avpogtStlHz -e “ssh -p ” / root@ That’s all, to make sure everything’s working, reboot the KVM box when the rsync process has completed. Once your new KVM box is up, you will have to go in there and make the IP changes to cPAnel/WHM, shoutcast, zPanel, or whichever other control panel you’re using. https://blog.webhostpython.com/2015/11/25/how-to-convertmigrate-openvz-vps-to-xenkvm/