Fresh install on CloudLinux 7.3 and latest cPanel

Paul Adair

Registered
Mar 14, 2017
2
1
3
london, ontario, canada
cPanel Access Level
DataCenter Provider
First off, I have a lot of experience with Ubuntu/Lunix and have managed systems manually for many years. Generally, I know my way around linux and configuration etc.

I'm looking at setting up a new virtual server and deploying CloudLinux with cPanel so clients can manage their websites themselves or use alternate developers looking for cPanel interface.

Host is licensed VMware 6.0. I've created a vm with 4cpu, 8GB and 500GB disk. I've downloaded the latest CloudLinux 7.3 and did a very basic install (tried as a CentOS 7 and RHEL 7) selecting only the web host option and setup root/user accounts. After install was complete only modifications I made were to set a static IP, set the hostname and DNS servers in resolv.conf. After that I followed this step in the cPanel install guide.
Code:
"cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest"
Error received 6 times then fails is this.
Code:
2017-03-14 15:49:17  249 (DEBUG):   - ssystem [END]
2017-03-14 15:49:17  249 (DEBUG):   - ssystem [BEGIN]: /usr/bin/yum -y install kernel-headers
2017-03-14 15:49:18  249 (DEBUG):     Loaded plugins: fastestmirror, langpacks
2017-03-14 15:49:18  249 (DEBUG):     Loading mirror speeds from cached hostfile
2017-03-14 15:49:18  249 (DEBUG):     There are no enabled repos.
2017-03-14 15:49:18  249 (DEBUG):      Run "yum repolist all" to see the repos you have.
2017-03-14 15:49:18  249 (DEBUG):      To enable Red Hat Subscription Management repositories:
2017-03-14 15:49:18  249 (DEBUG):          subscription-manager repos --enable <repo>
2017-03-14 15:49:18  249 (DEBUG):      To enable custom repositories:
2017-03-14 15:49:18  249 (DEBUG):          yum-config-manager --enable <repo>
2017-03-14 15:49:18  249 (ERROR):   - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored)
2017-03-14 15:49:18  249 (DEBUG):   - ssystem [END]
2017-03-14 15:49:18  253 (FATAL): yum failed 6 times. The installation process cannot continue.
Removing /root/installer.lock.
[[email protected] home]#
I know much more about 'apt-get' than yum but I did some poking around and found /etc/yum.repos.d and the cloudlinux.repo file. All of the repos had "enabled=0" in them. I set them to "enabled=1" again and re-ran the "sh latest" in the /home directory.

All of updates and downloads occurred and it looked like it was going well but then eventually failed.

Now this is what I get.
Code:
017-03-14 16:24:18  249 (DEBUG):   - ssystem [BEGIN]: /usr/bin/yum -y update
2017-03-14 16:24:19  249 (DEBUG):     Loaded plugins: fastestmirror, langpacks
2017-03-14 16:24:19  249 (DEBUG):     Loading mirror speeds from cached hostfile
2017-03-14 16:24:19  249 (DEBUG):      * cloudlinux-base: download.cloudlinux.com
2017-03-14 16:24:19  249 (DEBUG):      * cloudlinux-updates: download.cloudlinux.com
2017-03-14 16:24:21  249 (DEBUG):     Resolving Dependencies
2017-03-14 16:24:21  249 (DEBUG):     --> Running transaction check
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kernel.x86_64 1:3.10.0-427.36.1.lve1.4.35.el7 will be installed
2017-03-14 16:24:21  249 (DEBUG):     --> Processing Dependency: kmod-lve-3.10.0-427.36.1.lve1.4.35.el7.x86_64 for package: 1:kernel-3.10.0-427.36.1.lve1.4.35.el7.x86_64
2017-03-14 16:24:21  249 (DEBUG):     --> Processing Dependency: kmod-e1000e-3.10.0-427.36.1.lve1.4.35.el7.x86_64 for package: 1:kernel-3.10.0-427.36.1.lve1.4.35.el7.x86_64
2017-03-14 16:24:21  249 (DEBUG):     --> Processing Dependency: kmod-ixgbe-3.10.0-427.36.1.lve1.4.35.el7.x86_64 for package: 1:kernel-3.10.0-427.36.1.lve1.4.35.el7.x86_64
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kernel-tools.x86_64 1:3.10.0-427.18.2.lve1.4.27.el7 will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kernel-tools.x86_64 1:3.10.0-427.36.1.lve1.4.35.el7 will be an update
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kernel-tools-libs.x86_64 1:3.10.0-427.18.2.lve1.4.27.el7 will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kernel-tools-libs.x86_64 1:3.10.0-427.36.1.lve1.4.35.el7 will be an update
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kmod-lve.x86_64 1:1.4-27.1.el7 will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kmod-lve.x86_64 1:1.4-35.el7 will be an update
2017-03-14 16:24:21  249 (DEBUG):     ---> Package python-perf.x86_64 1:3.10.0-427.18.2.lve1.4.27.el7 will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package python-perf.x86_64 1:3.10.0-427.36.1.lve1.4.35.el7 will be an update
2017-03-14 16:24:21  249 (DEBUG):     ---> Package rhn-check.noarch 0:2.0.2-8.el7.cloudlinux will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package rhn-check.noarch 0:2.0.2-10.el7.cloudlinux will be an update
2017-03-14 16:24:21  249 (DEBUG):     ---> Package rhn-client-tools.noarch 0:2.0.2-8.el7.cloudlinux will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package rhn-client-tools.noarch 0:2.0.2-10.el7.cloudlinux will be an update
2017-03-14 16:24:21  249 (DEBUG):     --> Processing Dependency: python-cllib >= 1.2-2.16 for package: rhn-client-tools-2.0.2-10.el7.cloudlinux.noarch
2017-03-14 16:24:21  249 (DEBUG):     ---> Package rhn-setup.noarch 0:2.0.2-8.el7.cloudlinux will be updated
2017-03-14 16:24:21  249 (DEBUG):     ---> Package rhn-setup.noarch 0:2.0.2-10.el7.cloudlinux will be an update
2017-03-14 16:24:21  249 (DEBUG):     --> Running transaction check
2017-03-14 16:24:21  249 (DEBUG):     ---> Package kmod-e1000e-3.10.0-427.36.1.lve1.4.35.el7.x86_64.x86_64 1:3.3.5.3-6.el7 will be installed
2017-03-14 16:24:22  249 (DEBUG):     ---> Package kmod-ixgbe-3.10.0-427.36.1.lve1.4.35.el7.x86_64.x86_64 1:4.5.4-7.el7 will be installed
2017-03-14 16:24:22  249 (DEBUG):     ---> Package kmod-lve-3.10.0-427.36.1.lve1.4.35.el7.x86_64.x86_64 1:1.4-35.el7 will be installed
2017-03-14 16:24:22  249 (DEBUG):     ---> Package python-cllib.noarch 0:1.2-2.16.el7.cloudlinux will be installed
2017-03-14 16:24:22  249 (DEBUG):     --> Processing Dependency: python-simplejson for package: python-cllib-1.2-2.16.el7.cloudlinux.noarch
2017-03-14 16:24:22  249 (DEBUG):     --> Processing Dependency: python-jinja2 for package: python-cllib-1.2-2.16.el7.cloudlinux.noarch
2017-03-14 16:24:22  249 (DEBUG):     --> Processing Dependency: python-simplejson for package: python-cllib-1.2-2.16.el7.cloudlinux.noarch
2017-03-14 16:24:22  249 (DEBUG):     --> Processing Dependency: python-jinja2 for package: python-cllib-1.2-2.16.el7.cloudlinux.noarch
2017-03-14 16:24:22  249 (DEBUG):     --> Processing Dependency: PyYAML for package: python-cllib-1.2-2.16.el7.cloudlinux.noarch
2017-03-14 16:24:22  249 (DEBUG):     --> Processing Dependency: PyYAML for package: python-cllib-1.2-2.16.el7.cloudlinux.noarch
2017-03-14 16:24:22  249 (DEBUG):     --> Finished Dependency Resolution
2017-03-14 16:24:22  249 (DEBUG):     Error: Package: python-cllib-1.2-2.16.el7.cloudlinux.noarch (cloudlinux-updates-testing)
2017-03-14 16:24:22  249 (DEBUG):                Requires: python-jinja2
2017-03-14 16:24:22  249 (DEBUG):     Error: Package: python-cllib-1.2-2.16.el7.cloudlinux.noarch (cloudlinux-updates-testing)
2017-03-14 16:24:22  249 (DEBUG):                Requires: python-simplejson
2017-03-14 16:24:22  249 (DEBUG):     Error: Package: python-cllib-1.2-2.16.el7.cloudlinux.noarch (cloudlinux-updates-testing)
2017-03-14 16:24:22  249 (DEBUG):                Requires: PyYAML
2017-03-14 16:24:22  249 (DEBUG):      You could try using --skip-broken to work around the problem
2017-03-14 16:24:23  249 (DEBUG):      You could try running: rpm -Va --nofiles --nodigest
2017-03-14 16:24:23  249 (ERROR):   - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored)
2017-03-14 16:24:23  249 (DEBUG):   - ssystem [END]
2017-03-14 16:24:23  253 (FATAL): yum failed 6 times. The installation process cannot continue.
Removing /root/installer.lock.
I'm not sure what to try next. I could keep digging around but there must be something obvious I'm missing, there is NO WAY it should be this hard to get a brand new basic system with cpanel up and running. If it is this difficult there should be a manual or forum post or something documenting what the problems are here on a fresh vanilla install.

thanks, Paul.
 
Last edited by a moderator:

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,202
363
Hello,

I would like to note that with the initial RHEL installation, some additional steps are required before starting the cPanel installation:

Installation Guide - System Requirements - Documentation - cPanel Documentation

However, if that doesn't help, feel free to open a support ticket using the link in my signature so we can take a closer look and determine why the installation failed. You can post the ticket number here and we will update this thread with the outcome.

Thank you.
 

Paul Adair

Registered
Mar 14, 2017
2
1
3
london, ontario, canada
cPanel Access Level
DataCenter Provider
Michael, thanks for the reply. I may not of been clear, when I installed CloudLinux in VMware it asks what type of system it is. I tried it a few times, picking RHEL and CentOS. Both times though I installed CloudLinux from the ISO.

On that note, I see some specific instructions regarding a fresh CloudLinux setup. I hadn't see that before. Not sure how my 'googling' didn't find that link but anyway... I will start fresh again, will disable SELinux and run those 2 lines of commands in that link for CL.

I'll post back shortly how it goes.

thx, Paul.
 
  • Like
Reactions: cPanelMichael