Almalinux + cPanel + Cloudlinux
We have been using centos 7 to use cloudlinux and cPanel, but since learning EOL for centos 7 support I have been playing with Almalinux and Cloudlinux, problems with performance on low-end machines, and problems after installing. Never had this with CentOS 7 and Cloudlinux. Then the whole can't upgrade between 7 and 8 of on os. It's a joke cause more work and headaches.
Problematic is not the word.
Centos 7 + Cloudlinux + cPanel work perfectly.
Almalinux + Cloudllinux + cPanel not so much.
1) I found that once converting from Almalinux to Cloudlinux on a 2 CPU Shared VPS it is not stable, it's slow, and DAV and Python takes hours to install and set up.
2) On dedicated servers have found issues where some would not allow, SSH or Web Browser access after a reboot for kernel update. (this is down to the whole network and network manager i think)
I have tried the VMWARE image on Cloudlinux website to find it worked perfectly, but has mariadb and not MySQL as a default, then when trying to convert from mariadb to mysql cloudlinux was not having any of it. We hate maradb because of issues importing mysql databases, whereas mysql to mysql and maradb to my sql is seamless.
Then I also found this
Starting LSB: Bring up/down networking...
[18659]: WARN : [network] You are using 'network' service provided by 'network-scripts', which are now deprecated.
[18659]: WARN : [network] 'network-scripts' will be removed in one of the next major releases of RHEL.
[18659]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network management.
[18659]: Bringing up loopback interface: [ OK ]
[18659]: Bringing up interface eth0: [ OK ]
[1]: Started LSB: Bring up/down networking.
This is a problem is Cloudlinux and cPanel won't work with Network Manager, from what I have read.
So you install Almalinux to go to cPanel + Cloudlinux to have the move update services possible, to find that more work and workarounds need to be done as the network is being removed. Is this why the servers work one moment, then boom, not at all?
The problem is too many OS, and too many dependencies from multiple sources that tend to be unrelable and not always working.
Personally my self I am getting sick of trying to fix problems caused by updates and changes in OS and EOL, I mean come on Microsoft, and don't have all these issues. Personally, I wish cPanel would bring out a windows version I would move all our services to windows. Also if an os fails or closes down then your up a stream with out a paddle.
-
Hey there! AlmaLinux has been stable for some time with many cPanel users. CloudLinux 8 is also stable and I haven't heard of these types of issues. You are correct that NetworkManager is not supported by cPanel and does have to be removed, but everything else would be configured by CloudLinux. There is no reason you have to install AlmaLinux first - you could start straight with a CloudLinux 8 operating system and not have to convert CentOS or AlmaLinux, and that might help with some of the configuration you've run into. 0 -
We have been using centos 7 to use cloudlinux and cPanel, but since learning EOL for centos 7 support I have been playing with Almalinux and Cloudlinux, problems with performance on low-end machines, and problems after installing. Never had this with CentOS 7 and Cloudlinux. Then the whole can't upgrade between 7 and 8 of on os. It's a joke cause more work and headaches. Problematic is not the word. Centos 7 + Cloudlinux + cPanel work perfectly. Almalinux + Cloudllinux + cPanel not so much. 1) I found that once converting from Almalinux to Cloudlinux on a 2 CPU Shared VPS it is not stable, it's slow, and DAV and Python takes hours to install and set up. 2) On dedicated servers have found issues where some would not allow, SSH or Web Browser access after a reboot for kernel update. (this is down to the whole network and network manager i think) I have tried the VMWARE image on Cloudlinux website to find it worked perfectly, but has mariadb and not MySQL as a default, then when trying to convert from mariadb to mysql cloudlinux was not having any of it. We hate maradb because of issues importing mysql databases, whereas mysql to mysql and maradb to my sql is seamless. Then I also found this Starting LSB: Bring up/down networking... [18659]: WARN : [network] You are using 'network' service provided by 'network-scripts', which are now deprecated. [18659]: WARN : [network] 'network-scripts' will be removed in one of the next major releases of RHEL. [18659]: WARN : [network] It is advised to switch to 'NetworkManager' instead for network management. [18659]: Bringing up loopback interface: [ OK ] [18659]: Bringing up interface eth0: [ OK ] [1]: Started LSB: Bring up/down networking. This is a problem is Cloudlinux and cPanel won't work with Network Manager, from what I have read. So you install Almalinux to go to cPanel + Cloudlinux to have the move update services possible, to find that more work and workarounds need to be done as the network is being removed. Is this why the servers work one moment, then boom, not at all? The problem is too many OS, and too many dependencies from multiple sources that tend to be unrelable and not always working. Personally my self I am getting sick of trying to fix problems caused by updates and changes in OS and EOL, I mean come on Microsoft, and don't have all these issues. Personally, I wish cPanel would bring out a windows version I would move all our services to windows. Also if an os fails or closes down then your up a stream with out a paddle.
This issue mostly happen with hetzner and ovh server. After installing cpanel on almalinux 8. Everything work fine when we reboot the server it never goes up again. Read this article. I hope you will find out the solution0 -
Hi, Nope, even Cloudlinux says it should not be happening, they have restarted 4 times in the last hour. So even they are not sure why it is happening. But it does seem to be isolated to VMWare, Openstack images work fine.
I"ve already faced the same issue last month that"s why i provided the blog which was helpful for me.0 -
I"ve already faced the same issue last month that"s why i provided the blog which was helpful for me.
Tried that, but it did not work, I provided your fix to the tech team and they said it had not worked for them either.0 -
Hey there! AlmaLinux has been stable for some time with many cPanel users. CloudLinux 8 is also stable and I haven't heard of these types of issues. You are correct that NetworkManager is not supported by cPanel and does have to be removed, but everything else would be configured by CloudLinux. There is no reason you have to install AlmaLinux first - you could start straight with a CloudLinux 8 operating system and not have to convert CentOS or AlmaLinux, and that might help with some of the configuration you've run into.
I already tried the Cloudlinux all three images from Cloudlinux, Cloudlinux on its own and with cpanel.0 -
It's definitely time to submit a ticket to our team, then, so we can check this out. 0 -
Tried that, but it did not work, I provided your fix to the tech team and they said it had not worked for them either.
Could you contact the blog support team which i mentioned. May be it will help to sort out your issue. Or open a cpanel ticket they will check the issue.0 -
*Coff Coff* But Cloudlinux has got back to me and Cloudlinux is unstable with VMWare and they are now looking into it further. This was there last reply to me [QUOTE] When I talked about loading a different kernel, I literally meant a different kernel on the same system. When the CloudLinux OS is installed, it adds its own kernel and makes it the primary kernel to boot. The kernel of the original system is not removed and is normally available for selection in the grub boot menu. As I understand it, this menu is not available when booting the system now. Unfortunately, I have not been able to reconfigure the boot loader via rescue mode. Apparently due to the peculiarities of the creation of this virtual machine or the operation of DC, only the ovf and vmdk files of your virtual machine are available on the sda drive, which should be the file system of the server. 0 -
It's definitely time to submit a ticket to our team, then, so we can check this out.
I did 3 days ago, they don't know either, they said they would have to contact cloudlinux, so told them I already have and they are also trying to find the issue.0 -
I did 3 days ago, they don't know either, they said they would have to contact cloudlinux, so told them I already have and they are also trying to find the issue.
Already told try to contact the blog support which I mentioned. They will help to fix the issue.0 -
Finally, a fix is here. Run the commands below. yum install wget -y
wget https://repo.cloudlinux.com/cloudlinux/sources/cln/cldeploy
sh cldeploy -i
grub2-set-default 0
grub2-mkconfig -o /boot/grub/grub.cfg
reboot
Finally!! If you will install the control panel, natively supported by CloudLinux (cPanel, DirectAdmin, Plesk) later, then you MUST reinstall CloudLinux Manager packages with the following command:yum reinstall -y lvemanager lve-utils alt-python27-cllib cagefs
Please note this only works for this error. not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I hope this helps others, and I recommend that cPanel add it to their solutions.0 -
Already told try to contact the blog support which I mentioned. They will help to fix the issue.
Sorry, I rather get the organ grinder fixed, and it may have taken Cloudlinux and me a whole day but we did it. We pay money for licenses, which also includes support. Unlike most companies, Cloudlinux is willing to help without charging extra! But thank you for the information.0
Please sign in to leave a comment.
Comments
14 comments