Houston, we've had a problem

Unable to check update due to a system error: Error running a command. cmd = [’/usr/bin/yum’, ‘changelog’, ‘2016-Nov-04’, ‘rockstor’]. rc = 1. stdout = [‘Loaded plugins: changelog, fastestmirror’, ‘’]. 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. Disable the repository, 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 ‘, ‘’, ’ 4. 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 retrieve metalink for repository: epel/x86_64. Please verify its path and try again’, ‘’]

        Traceback (most recent call last):

File “/opt/rockstor/src/rockstor/storageadmin/views/command.py”, line 177, in post
return Response(update_check(subscription=subo))
File “/opt/rockstor/src/rockstor/system/pkg_mgmt.py”, line 155, in update_check
o, e, rc = run_command([YUM, ‘changelog’, date, pkg])
File “/opt/rockstor/src/rockstor/system/osi.py”, line 104, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = [’/usr/bin/yum’, ‘changelog’, ‘2016-Nov-04’, ‘rockstor’]. rc = 1. stdout = [‘Loaded plugins: changelog, fastestmirror’, ‘’]. 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. Disable the repository, 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 ‘, ‘’, ’ 4. 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 retrieve metalink for repository: epel/x86_64. Please verify its path and try again’, ‘’]

@TheEgyptianDeveloper Welcome to Rockstor and apologies for the delay in your post appearing.

From the error it looks like the epel repository was not available / accessible. At the time this error occurred Rockstor expected a working internet connection to the epel repository and didn’t find it.

When did this error occur?