cPanel & WHM Version
98.0.9

tommyxv

Member
Jun 15, 2006
22
5
153
I keep getting this update error. Any ideas how to fix?

[2021-10-12 06:28:43 -0400] Processing: Running rpmup (yum -y update)
[2021-10-12 06:28:43 -0400] - Processing command `/usr/local/cpanel/scripts/rpmup`
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] checkyum version 22.3 (excludes: bind-chroot kernel)
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] Running package manager clean up before update due to force option …
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] Loaded plugins: fastestmirror, universal-hooks
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] Determining fastest mirrors
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * EA4: 63.247.64.58
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * cpanel-addons-production-feed: 63.247.64.58
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * cpanel-plugins: 63.247.64.58
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * base: repos.dfw.quadranet.com
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * epel: mirror.atl.genesisadaptive.com
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * extras: mirrors.unifiedlayer.com
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] * updates: mirror.atl.genesisadaptive.com
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] https://repo.saltstack.com/yum/redhat/7/x86_64/latest/repodata/repomd.xml:[Errno 14] HTTPS Error 404 - Not Found
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] Trying other mirror.
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] To address this issue please refer to the below wiki article
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] yum-errors - CentOS Wiki
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] If above article doesn't help to resolve this issue please use My View - CentOS Bug Tracker.
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] One of the configured repositories failed (SaltStack Latest Release Channel for RHEL/Centos 7),
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] and yum doesn't have enough cached data to continue. At this point the only
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] safe thing yum can do is fail. There are a few ways to work "fix" this:
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] 1. Contact the upstream for the repository and get them to fix the problem.
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] 2. Reconfigure the baseurl/etc. for the repository, to point to a working
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] upstream. This is most often useful if you are using a newer
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] distribution release than is supported by the repository (and the
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] packages for the previous distribution release still work).
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] 3. Run the command with the repository temporarily disabled
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] yum --disablerepo=salt-latest ...
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] 4. Disable the repository permanently, so yum won't use it by default. Yum
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] will then just ignore the repository until you permanently enable it
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] again or use --enablerepo for temporary usage:
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] yum-config-manager --disable salt-latest
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] or
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] subscription-manager repos --disable=salt-latest
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] 5. Configure the failing repository to be skipped, if it is unavailable.
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] Note that yum will try to contact the repo. when it runs most commands,
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] so will have to try and fail each time (and thus. yum will be be much
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] slower). If it is a very temporary problem though, this is often anice
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] compromise:
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] yum-config-manager --save --setopt=salt-latest.skip_if_unavailable=true
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup]
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] failure: repodata/repomd.xml from salt-latest: [Errno 256] No more mirrorsto try.
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] https://repo.saltstack.com/yum/redhat/7/x86_64/latest/repodata/repomd.xml:[Errno 14] HTTPS Error 404 - Not Found
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] (XID 2k9hbd) “/usr/bin/yum” reported error code “1” when it ended:
[2021-10-12 06:28:53 -0400] [/usr/local/cpanel/scripts/rpmup] checkyum version 22.3 (excludes: bind-chroot)
[2021-10-12 06:28:53 -0400] E [/usr/local/cpanel/scripts/rpmup] The “/usr/local/cpanel/scripts/rpmup” command (process 27552) reported error number 1 when it ended.
[2021-10-12 06:28:53 -0400] The Administrator will be notified to review this output when this script completes
[2021-10-12 06:28:53 -0400] - Finished command `/usr/local/cpanel/scripts/rpmup` in 9.151 seconds
[2021-10-12 06:28:53 -0400] 30% complete
[2021-10-12 06:28:53 -0400] - Finished in 9.151 seconds
[2021-10-12 06:28:53 -0400] - Finished in 0.061 seconds
[2021-10-12 06:28:53 -0400] Processing:
[2021-10-12 06:28:53 -0400] Maintenance complete. [state=pre]
=> Log closed Tue Oct 12 06:28:53 2021
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (27387) at Tue Oct 12 06:28:53 2021
[2021-10-12 06:28:53 -0400] E Pre Maintenance ended, however it did not exit cleanly (256). The following events were logged: "scripts/rpmup". Please check the logs for an indication of what happened
=> Log closed Tue Oct 12 06:28:53 2021
 
Last edited by a moderator:

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
7,519
1,028
313
cPanel Access Level
Root Administrator
Hey there! This error isn't related to cPanel itself, but to the additional "saltstack" repository that is configured on the machine. You would likely get a similar error running "yum update" directly on the operating system itself.

I checked this on my end and also am not able to connect to that resource:

Code:
# wget https://repo.saltstack.com/yum/redhat/7/x86_64/latest/repodata/repomd.xml
--2021-10-12 08:53:27--  https://repo.saltstack.com/yum/redhat/7/x86_64/latest/repodata/repomd.xml
Resolving repo.saltstack.com (repo.saltstack.com)... 2600:9000:2162:9c00:d:e451:e500:93a1, 2600:9000:2162:d800:d:e451:e500:93a1, 2600:9000:2162:2600:d:e451:e500:93a1, ...
Connecting to repo.saltstack.com (repo.saltstack.com)|2600:9000:2162:9c00:d:e451:e500:93a1|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-10-12 08:53:28 ERROR 404: Not Found.
so it would likely be best to just remove that repository so your system doesn't try and use it during the update process.