WHM update not work. Problem "database is locked" if launch "yum update"

andinacom

• June 08, 2020 16:36

Hi, i have a problem updating WHM. It is currently blocked to v82.0.16 . After searching the forum I realized that it is a problem with the yum command. When I run "yum update" the answer is as follows: Loaded plugins: universal-hooks EA4 | 2.9 kB 00:00:00 cpanel-addons-production-feed | 2.9 kB 00:00:00 cpanel-plugins | 2.9 kB 00:00:00 MariaDB103 | 2.9 kB 00:00:00 base | 3.6 kB 00:00:00 extras | 2.9 kB 00:00:00 updates | 2.9 kB 00:00:00 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 database is locked
Can you help me solve the problem? Thank's a lot.

• 

  dalem

  • June 08, 2020 22:27

  Try yum clean all yum update

  0
• 

  Michael-Inet

  • June 09, 2020 19:19

  database is locked
  This is for the edge case where you've just built the server and the hosting firm has an auto 'yum update' launch in their ISOs. In this case then you'll get the database is locked until it finishes updating and then you're good. Pretty rare, but really frustrating... Best, Michael

  0
• 

  SamuelM

  • June 11, 2020 03:17

  Hello @andinacom Did you have any luck after executing the yum clean all
  command? The error is difficult to interpret because it does specify which repository failed. Does the command work if you enable only the base repo? yum --disablerepo=* --enablerepo=base update
  Best regards

  0

Please sign in to leave a comment.