Skip to main content

upcp - /scripts/rpmup command reported error number 29 when it ended.

Comments

6 comments

  • cPanelMichael
    Hello @jimlongo, Can you manually run the /usr/local/cpanel/scripts/rpmup command and let us know the output? Thank you.
    0
  • jimlongo
    SERVER1 root@vps [~]# /usr/local/cpanel/scripts/rpmup info [rpmup] Resolving potential yum cache issue " "yum" reported error code "1" when it ended: w/ yum Often errors like this can be resolved by running `yum makecache` root@vps [~]# yum makecache Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://vzdownload.swsoft.com/download/mirrors/centos-7 error was 12: Timeout on http://vzdownload.swsoft.com/download/mirrors/centos-7: (28, 'Connection timed out after 30001 milliseconds') One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Cannot find a valid baseurl for repo: vz-base
    SERVER2 [root@li1265-51 ~]# /usr/local/cpanel/scripts/rpmup Checking that the RPM DB is OK... glibc-2.17-222.el7.x86_64 OK: RPM DB is responding to queries Testing if rpm_is_working RPM is installed package rpm_is_working is not installed Testing if it's possible to install a simple RPM Preparing... ######################################## Updating / installing... rpm_is_working-1.0-0 ######################################## checkyum version 22.3 Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile * EA4: 66.23.237.210 * cpanel-addons-production-feed: 66.23.237.210 * base: ewr.edge.kernel.org * extras: ewr.edge.kernel.org * updates: ewr.edge.kernel.org No packages marked for update checkyum version 22.3
    0
  • cPanelMichael
    Could not retrieve mirrorlist : (28, 'Connection timed out after 30001 milliseconds')

    Hello @jimlongo, For the first server, this error suggests your system is configured with a custom /etc/yum.repos.d/vz.repo YUM repository, and connections to it are timing out. You can add an "enabled=0" line to both the [vz-base] and [vz-updates] sections of this REPO to disable it. For example: [vz-base] name=vz-base mirrorlist=http://vzdownload.swsoft.com/download/mirrors/centos-7 enabled=0 gpgcheck=0 [vz-updates] name=vz-updates mirrorlist=http://vzdownload.swsoft.com/download/mirrors/updates-released-ce7 enabled=0 gpgcheck=0
    Then, run the yum makecache command again. This should allow updates to proceed. Once you've confirmed updates are working, you may want to check with your VPS hosting provider to verify why the custom YUM repo configured on your system is not working properly. For the second server, it looks like the RPM update completed well. Are cPanel updates still failing on this server, and if so, is the error message still the same? Thank you.
    0
  • jimlongo
    Thank you. Server2 seems okay now, and I'm dealing with Server1 through the provider.
    0
  • jimlongo
    My provider found that the IP of the mirror serving the update files was blocked by the firewall.
    0
  • cPanelMichael
    Hello @jimlongo, I'm glad to see the issue was solved. Thank you for sharing the outcome.
    0

Please sign in to leave a comment.