I’m currently running version 3.8.16-16 I think. It’s not showing in the web UI. I just replaced the mother board and figured while I was doing serious MX, I’d update to the latest development release as well. I hit the software update to see how far behind I was and got the following error.
##### Houston, we’ve had a problem.
Unable to check update due to a system error: Error running a command. cmd = /usr/bin/yum changelog 2017-Mar-08 rockstor. rc = 1. stdout = [‘Loaded plugins: changelog, fastestmirror’, ‘Loading mirror speeds from cached hostfile’, ’ * base: ftp.usf.edu’, ’ * epel: mirror.clarkson.edu’, ’ * extras: centos.servint.com’, ’ * updates: ewr.edge.kernel.org’, ‘’]. stderr = [’’, ‘’, ’ 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=<repoid> …’, ‘’, " 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 <repoid>’, ’ or’, ’ subscription-manager repos --disable=<repoid>’, ‘’, ’ 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=<repoid>.skip_if_unavailable=true’, ‘’, ‘disk I/O error’, ‘’]
The traceback window contains:
Traceback (most recent call last):
File “/opt/rockstor/src/rockstor/storageadmin/views/command.py”, line 188, in post
return Response(update_check(subscription=subo))
File “/opt/rockstor/src/rockstor/system/pkg_mgmt.py”, line 163, in update_check
o, e, rc = run_command([YUM, ‘changelog’, date, pkg])
File “/opt/rockstor/src/rockstor/system/osi.py”, line 110, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = /usr/bin/yum changelog 2017-Mar-08 rockstor. rc = 1. stdout = [‘Loaded plugins: changelog, fastestmirror’, ‘Loading mirror speeds from cached hostfile’, ’ * base: repos.dfw.quadranet.com’, ’ * epel: mirror.clarkson.edu’, ’ * extras: mirrors.centos.webair.com’, ’ * updates: centos.servint.com’, ‘’]. stderr = [’’, ‘’, ’ 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’, ‘’, ‘disk I/O error’, ‘’]
I’m guessing this is probably a quick CLI action to update the correct repo, but don’t want to guess and break things. Any help greatly appreciated.