delalibera

Member
Jan 6, 2014
20
0
1
cPanel Access Level
Reseller Owner
Hello,

I updated my cpanel to v80.0.11 and now the upcp returns the error

Code:
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] ---> Package python-six.noarch 0:1.9.0-2.el6 will be installed
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] --> Finished Dependency Resolution
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] Error: Package: 32:bind-chroot-9.8.2-0.47.rc1.el6_8.4.x86_64 (@updates)
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]  You could try using --skip-broken to work around the problem
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] ** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] 32:bind-9.8.2-0.47.rc1.el6_8.4.x86_64 has missing requires of portreserve
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] (XID 34k624) The system failed to execute yum with the arguments “--assumeyes --config /etc/yum.conf update --disablerepo=epel” because of an error: The “/usr/bin/yum --assumeyes --config /etc/yum.conf update --disablerepo=epel” command (process 27193) reported error number 1 when it ended. : Error: Package: 32:bind-chroot-9.8.2-0.47.rc1.el6_8.4.x86_64 (@updates)
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]            Requires: bind = 32:9.8.2-0.47.rc1.el6_8.4
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]            Removing: 32:bind-9.8.2-0.47.rc1.el6_8.4.x86_64 (@updates)
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]                bind = 32:9.8.2-0.47.rc1.el6_8.4
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]            Updated By: 32:bind-9.8.2-0.68.rc1.el6_10.1.x86_64 (updates)
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]                bind = 32:9.8.2-0.68.rc1.el6_10.1
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]            Available: 32:bind-9.8.2-0.68.rc1.el6.x86_64 (base)
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup]                bind = 32:9.8.2-0.68.rc1.el6
[2019-06-01 06:55:37 -0300]      [/usr/local/cpanel/scripts/rpmup] checkyum version 22.3  (excludes: bind-chroot perl ruby)
[2019-06-01 06:55:37 -0300] E    [/usr/local/cpanel/scripts/rpmup] The “/usr/local/cpanel/scripts/rpmup” command (process 27177) reported error number 1 when it ended.
[2019-06-01 06:55:37 -0300]   The Administrator will be notified to review this output when this script completes
[2019-06-01 06:55:37 -0300]    - Finished command `/usr/local/cpanel/scripts/rpmup` in 12.127 seconds
I executed the command yum check and update and returns the error

Code:
Error: Package: 32:bind-chroot-9.8.2-0.47.rc1.el6_8.4.x86_64 (@updates)
           Requires: bind = 32:9.8.2-0.47.rc1.el6_8.4
           Removing: 32:bind-9.8.2-0.47.rc1.el6_8.4.x86_64 (@updates)
               bind = 32:9.8.2-0.47.rc1.el6_8.4
           Updated By: 32:bind-9.8.2-0.68.rc1.el6_10.1.x86_64 (updates)
               bind = 32:9.8.2-0.68.rc1.el6_10.1
           Available: 32:bind-9.8.2-0.68.rc1.el6.x86_64 (base)
               bind = 32:9.8.2-0.68.rc1.el6
 You could try using --skip-broken to work around the problem
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
32:bind-9.8.2-0.47.rc1.el6_8.4.x86_64 has missing requires of portreserve
cpanel-analytics-1.3.3-1.1.noarch has missing requires of cpanel-version >= ('0', '73.0.0', None)
Can anyone help me to solve this?
 

GOT

Get Proactive!
PartnerNOC
Apr 8, 2003
1,753
311
363
Chesapeake, VA
cPanel Access Level
DataCenter Provider
I do not believe that the bind-chroot package is supposed to be installed at all even if you are using bind as your dns server.

If it were me, what I would do is go into whm and go to nameserver selection and change your nameserver over to PowerDNS. Once that is switched and verified running, I would check to see if bind-chroot is still installed and if so, I would probably remove it and then updates can run.

If you really prefer to run bind, at this point you could go back into whm and turn bind back on.