/usr/local/cpanel/scripts/rpmup command (process 24810) reported error
Hello,
The upgrade was successful.
But yesterday the following message received:
The cPanel & WHM update process failed for the following reason:
Maintenance ended; however, it did not exit cleanly (256). The following events were logged: "scripts/rpmup". Review the update logs to determine why the update failed.
Update log preview:
...
...
[2019-07-08 15:21:22 -0700] E [/usr/local/cpanel/scripts/rpmup] The "/usr/local/cpanel/scripts/rpmup" command (process 24810) reported error number 1 when it ended.
Please, advice. Many thanks.
With the best
L
-
when you run /usr/local/cpanel/scripts/rpmup
manually, what is the output?0 -
when you run
/usr/local/cpanel/scripts/rpmup
manually, what is the output?
Hello Lauren, I received the follows: checkyum version 22.3 (excludes: bind-chroot kernel perl ruby) info [rpmup] Starting yum execution "--assumeyes --config /etc/yum.conf update --disablerepo=epel". Loaded plugins: fastestmirror, universal-hooks Setting up Update Process Loading mirror speeds from cached hostfile * EA4: 104.219.172.10 * cpanel-addons-production-feed: 104.219.172.10 * cpanel-plugins: 104.219.172.10 * base: centos-distro.cavecreek.net * extras: centos-distro.cavecreek.net * ius: dfw.mirror.rackspace.com * updates: centos-distro.cavecreek.net Resolving Dependencies --> Running transaction check ---> Package upstart.x86_64 0:0.6.5-13.el6_5.3 will be updated ---> Package upstart.x86_64 0:0.6.5-17.el6 will be an update --> Finished Dependency Resolution Total download size: 177 k Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Updating : upstart-0.6.5-17.el6.x86_64 1/2 Error unpacking rpm package upstart-0.6.5-17.el6.x86_64 upstart-0.6.5-13.el6_5.3.x86_64 was supposed to be removed but is not! Verifying : upstart-0.6.5-13.el6_5.3.x86_64 1/2 Verifying : upstart-0.6.5-17.el6.x86_64 2/2 Complete! info [rpmup] Completed yum execution "--assumeyes --config /etc/yum.conf update --disablerepo=epel": in 16.064 second(s). (XID 7zheh4) 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 5355) reported error number 1 when it ended. : Error unpacking rpm package upstart-0.6.5-17.el6.x86_64 upstart-0.6.5-13.el6_5.3.x86_64 was supposed to be removed but is not! checkyum version 22.3 (excludes: bind-chroot perl ruby) Please, advice. Thanks.0 -
Do you have two versions of upstart present? You can check this with the following: rpm -qa |grep upstart
If so, are you able to manually remove: upstart-0.6.5-13.el6_5.3.x86_64 (the older version of the package)0 -
Do you have two versions of upstart present? You can check this with the following:
rpm -qa |grep upstart
If so, are you able to manually remove: upstart-0.6.5-13.el6_5.3.x86_64 (the older version of the package)
Hello Lauren, Here rpm -qa |grep upstart upstart-0.6.5-13.el6_5.3.x86_64 and nothing else. Please, advice. Thanks.0 -
I have the same issue, when I type the command (/usr/local/cpanel/scripts/rpmup) I got a huge error message: --> Finished Dependency Resolution Total size: 144 M Downloading packages: Running transaction check Running transaction test info [rpmup] Completed yum execution "--assumeyes --config /etc/yum.conf update": in 22.224 second(s). (XID zdnxg3) The system failed to execute yum with the arguments "--assumeyes --config /etc/yum.conf update" because of an error: The "/usr/bin/yum --assumeyes -- config /etc/yum.conf update" command (process 7233) reported error number 1 when it ended. : Transaction check error: file /usr/include/asm-generic/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_ 64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-769503.x86_64 file /usr/include/asm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and k ernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-769503.x86_64 file /usr/include/drm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and k ernel-4.19-ovh-xxxx-std-ipv6-64-headers- - snipped -0 -
Hello Lauren, Here rpm -qa |grep upstart upstart-0.6.5-13.el6_5.3.x86_64 and nothing else. Please, advice. Thanks.
Let's try this - can you manually update upstart? You'd run the following:yum update upstart0 -
Let's try this - can you manually update upstart? You'd run the following:
yum update upstart
Do I need to do this me too ?0 -
@Jean-Sebastien Provost While you are getting an error doing the same action your issue is different. You have an RPM conflict between two RPM's on your system: file /usr/include/asm-generic/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-769503.x86_64 file /usr/include/asm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-769503.x86_64 file /usr/include/drm/..install.cmd conflicts between attempted installs of kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 and kernel-4.19-ovh-xxxx-std-ipv6-64-headers-
your system is attempting to install: kernel-4.19-ovh-mod-std-ipv6-64-headers-4.19_ovh_mod_std_ipv6_64-732421.x86_64 But you have the following installed: kernel-4.19-ovh-xxxx-std-ipv6-64-headers-4.19_ovh_xxxx_std_ipv6_64-769503.x86_64 technically the kernel-headers version you have installed is the newer version - what kernel version are you running?0 -
@Jean-Sebastien Provost technically the kernel-headers version you have installed is the newer version - what kernel version are you running?
[root@ns559924 ~]# uname -a Linux ns559924.ip-54-39-105.net 4.9.144-xxxx-std-ipv6-64 #494761 SMP Mon Dec 10 14:03:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@ns559924 ~]# uname -r 4.9.144-xxxx-std-ipv6-640 -
What I need to do to fix this issue ? 0 -
can you run the following instead: rpm -qa |grep kernel0 -
can you run the following instead:
rpm -qa |grep kernel
Got this :[root@ns559924 ~]# rpm -qa |grep kernel kernel-headers-3.10.0-957.12.2.el7.x86_64 kernel-devel-3.10.0-957.12.2.el7.x86_64 kernel-devel-3.10.0-957.12.1.el7.x86_64 kernel-3.10.0-862.14.4.el7.x86_64 kernel-devel-3.10.0-957.5.1.el7.x86_64 ovhkernel_4.9_xxxx_std_ipv6-4.9.178_xxxx_std_ipv6_64-730913.x86_64 kernel-devel-3.10.0-957.1.3.el7.x86_64 kernel-devel-3.10.0-957.10.1.el7.x86_64 [root@ns559924 ~]#0 -
This is a bit confusing - are you trying to use the OVH kernel or are you trying to use the standard CentOS kernel? It looks like based on the packages that are installed you at some point were utilizing the CentOS kernel I'd wager though that none of these have been used in some time they're not in use currently kernel-devel-3.10.0-957.12.2.el7.x86_64 kernel-devel-3.10.0-957.12.1.el7.x86_64 kernel-devel-3.10.0-957.5.1.el7.x86_64 kernel-devel-3.10.0-957.1.3.el7.x86_64 kernel-devel-3.10.0-957.10.1.el7.x86_64
kernel-headers-3.10.0-957.12.2.el7.x86_64
You also have an older standard kernel installedkernel-3.10.0-862.14.4.el7.x86_64
What you are currently using based on the output from:[root@ns559924 ~]# uname -r 4.9.144-xxxx-std-ipv6-64
But you have this package installed:ovhkernel_4.9_xxxx_std_ipv6-4.9.178_xxxx_std_ipv6_64-730913.x86_64
What you may want to do and what might be the safest bet is to contact OVH and have them assist you with removing the unused kernel packages and then assist you with updating the kernel in use on the system. While rpmup is experiencing an issue running it's occurring because of the conflicts and the cause of the conflicts aren't necessarily something that we have control over - we don't control what kernel version you're running and it can be risky to make modifications in this area without knowing fully what you're doing.0 -
This is a bit confusing - are you trying to use the OVH kernel or are you trying to use the standard CentOS kernel? It looks like based on the packages that are installed you at some point were utilizing the CentOS kernel I'd wager though that none of these have been used in some time they're not in use currently
kernel-devel-3.10.0-957.12.2.el7.x86_64 kernel-devel-3.10.0-957.12.1.el7.x86_64 kernel-devel-3.10.0-957.5.1.el7.x86_64 kernel-devel-3.10.0-957.1.3.el7.x86_64 kernel-devel-3.10.0-957.10.1.el7.x86_64
kernel-headers-3.10.0-957.12.2.el7.x86_64
You also have an older standard kernel installedkernel-3.10.0-862.14.4.el7.x86_64
What you are currently using based on the output from:[root@ns559924 ~]# uname -r 4.9.144-xxxx-std-ipv6-64
But you have this package installed:ovhkernel_4.9_xxxx_std_ipv6-4.9.178_xxxx_std_ipv6_64-730913.x86_64
What you may want to do and what might be the safest bet is to contact OVH and have them assist you with removing the unused kernel packages and then assist you with updating the kernel in use on the system. While rpmup is experiencing an issue running it's occurring because of the conflicts and the cause of the conflicts aren't necessarily something that we have control over - we don't control what kernel version you're running and it can be risky to make modifications in this area without knowing fully what you're doing.
I already talked to OVH and they do not manage/support what is installed on the dedicated server. Their job is to gives me a dedicated server who works and check the physical part. So I'm currently on my own on this one and I have a lot of clients on this machine and I don't want (very not) to have a down time and play with a rescue shell ... What's safe move I can do ?0 -
My assumption here is that you'll want to use the standard kernel but this is a system administration task and not something controlled or managed by cPanel. If your provider is unable to assist you with this I'd suggest enlisting the assistance of a qualified system administrator, if you don't have one you might find one here: System Administration Services | cPanel Forums. I definitely wouldn't be comfortable giving you advice on this without having access to the system and you're more than welcome to open ticket for which you can find instructions on how to do in the link in my signature, but I would be prepared for us being unable to make any changes of this nature as well as directing you to a system administrator. 0 -
Let's try this - can you manually update upstart? You'd run the following:
yum update upstart
Hello Lauren, The above command run then i can see the following: Total download size: 177 k Is this ok [y/N]: y Downloading Packages: upstart-0.6.5-17.el6.x86_64.rpm | 177 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Updating : upstart-0.6.5-17.el6.x86_64 1/2 Error unpacking rpm package upstart-0.6.5-17.el6.x86_64 error: unpacking of archive failed on file /etc/dbus-1/system.d/Upstart.conf;5d2df7d5: cpio: mkdir upstart-0.6.5-13.el6_5.3.x86_64 was supposed to be removed but is not! Verifying : upstart-0.6.5-13.el6_5.3.x86_64 1/2 Verifying : upstart-0.6.5-17.el6.x86_64 2/2 Failed: upstart.x86_64 0:0.6.5-13.el6_5.3 upstart.x86_64 0:0.6.5-17.el6 Complete! Please, advice. Thanks.0 -
Hi @Lillike The issue seems to be in the ability to make the directory: error: unpacking of archive failed on file /etc/dbus-1/system.d/Upstart.conf;5d2df7d5: cpio: mkdir
This could be indicative of several things including some serious issues. Because this isn't a package or an issue specific to cPanel/WHM and rather than speculate, I believe that the best way to troubleshoot this would be to contact your provider for assistance, if they're unable to provide assistance I'd suggest enlisting the assistance of a qualified system administrator, if you don't have one you might find one here: System Administration Services | cPanel Forums0
Please sign in to leave a comment.
Comments
17 comments