The system could not fetch the TIERS file error
Very strange, our new VPS KVM CentOS 7 templates seem to have an issue with cPanel. I got through the normal steps to disable network manager and the firewall.
But when I run cPanel I get this error and all networking stops:
2019-04-10 00:12:39 333 (DEBUG): Package kernel-headers-3.10.0-957.10.1.el7.x86_64 already installed and latest version
2019-04-10 00:12:39 333 (DEBUG): Nothing to do
2019-04-10 00:12:39 333 (DEBUG): - ssystem [END]
2019-04-10 00:12:39 184 (DEBUG): - ssystem [BEGIN]: ps -U nscd -h 2>/dev/null || /sbin/service nscd start
2019-04-10 00:12:39 184 (DEBUG): Redirecting to /bin/systemctl start nscd.service
2019-04-10 00:12:39 184 (DEBUG): - ssystem [END]
2019-04-10 00:12:39 1729 (DEBUG): - ssystem [BEGIN]: /usr/bin/rdate -s rdate.cpanel.net
2019-04-10 00:12:39 1729 (DEBUG): rdate: rdate.cpanel.net: Name or service not known
2019-04-10 00:12:39 1729 (ERROR): - ssystem [EXIT_CODE] '/usr/bin/rdate' exited with 1 (ignored)
2019-04-10 00:12:39 1729 (DEBUG): - ssystem [END]
2019-04-10 00:12:39 1731 ( INFO): The system set the clock to: Wed Apr 10 00:12:39 2019
2019-04-10 00:12:39 1741 ( INFO): The system changed the clock by 0 seconds.
2019-04-10 00:12:39 1511 ( INFO): The installation process will now set up the necessary empty cpanel directories.
2019-04-10 00:12:39 1542 ( INFO): The installation process will now ensure that GPG is set up properly before it imports keys.
2019-04-10 00:12:39 1545 ( INFO): The installation process will now import GPG keys for yum.
2019-04-10 00:12:39 1273 (DEBUG): Retrieving to the TIERS file...
2019-04-10 00:12:39 1282 (FATAL): The system could not fetch the TIERS file.
When i reboot the server networking starts again but when I run cPanel it stops at the same point and all networking is down.
I'm stumped, the resolve file is fine. Everything looks good that I can tell.
-
Hello, I'm monitoring the corresponding support ticket opened for this issue and will update this thread with the outcome once it's closed. Thank you. 0 -
I'm sorry, I was just so used to my previous template that I didn't think to disable SeLinux. I changed the /etc/selinux/config file to # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted rebooted and 0
Please sign in to leave a comment.
Comments
2 comments