PATH:
var
/
log
/
bitninja-reliable-auto-update
E0207 19:25:40.349272 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0207 19:25:40.349272 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0207 19:25:40.349272 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0208 01:25:29.224731 11302 app.go:105] Auto update running every 6 hours I0208 01:25:29.225094 11302 app.go:106] Checking for updates I0208 01:25:34.834461 11302 updatemanager.go:29] Checking bitninja package E0208 01:25:41.873279 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 01:25:41.873279 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 01:25:41.873279 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0208 07:25:29.223602 11302 app.go:105] Auto update running every 6 hours I0208 07:25:29.224133 11302 app.go:106] Checking for updates I0208 07:25:34.640777 11302 updatemanager.go:29] Checking bitninja package E0208 07:25:40.832311 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 07:25:40.832311 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 07:25:40.832311 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0208 13:25:29.224174 11302 app.go:105] Auto update running every 6 hours I0208 13:25:29.224542 11302 app.go:106] Checking for updates I0208 13:25:34.817903 11302 updatemanager.go:29] Checking bitninja package E0208 13:25:41.695109 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 13:25:41.695109 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 13:25:41.695109 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0208 19:25:29.224274 11302 app.go:105] Auto update running every 6 hours I0208 19:25:29.224742 11302 app.go:106] Checking for updates I0208 19:25:34.767968 11302 updatemanager.go:29] Checking bitninja package E0208 19:25:41.282276 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 19:25:41.282276 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0208 19:25:41.282276 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0209 01:25:29.470223 11302 app.go:105] Auto update running every 6 hours I0209 01:25:29.470811 11302 app.go:106] Checking for updates I0209 01:25:35.077002 11302 updatemanager.go:29] Checking bitninja package E0209 01:25:41.764241 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 01:25:41.764241 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 01:25:41.764241 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0209 07:25:29.469821 11302 app.go:105] Auto update running every 6 hours I0209 07:25:29.470345 11302 app.go:106] Checking for updates I0209 07:25:35.054093 11302 updatemanager.go:29] Checking bitninja package E0209 07:25:41.785216 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 07:25:41.785216 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 07:25:41.785216 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 09:58:09.867920 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 09:58:09.867920 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 09:58:09.867920 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0209 09:58:09.869481 11302 socket.go:120] Connection closed. Reconnecting... I0209 09:58:09.995652 11302 socket.go:46] Login successful! I0209 09:58:09.995684 11302 socket.go:59] Trying to connect to API Server I0209 09:58:10.103169 11302 socket.go:73] Successfully connected to API Server E0209 10:00:37.569885 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:00:37.569885 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:00:37.569885 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0209 10:00:37.569948 11302 socket.go:120] Connection closed. Reconnecting... I0209 10:00:37.616639 11302 socket.go:46] Login successful! I0209 10:00:37.616667 11302 socket.go:59] Trying to connect to API Server I0209 10:00:37.723972 11302 socket.go:73] Successfully connected to API Server E0209 10:33:23.179253 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:33:23.179253 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:33:23.179253 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0209 10:33:23.179380 11302 socket.go:120] Connection closed. Reconnecting... I0209 10:33:23.424121 11302 socket.go:46] Login successful! I0209 10:33:23.424150 11302 socket.go:59] Trying to connect to API Server I0209 10:33:23.507905 11302 socket.go:73] Successfully connected to API Server E0209 10:34:32.649177 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:34:32.649177 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:34:32.649177 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0209 10:34:32.649244 11302 socket.go:120] Connection closed. Reconnecting... I0209 10:34:32.695719 11302 socket.go:46] Login successful! I0209 10:34:32.695747 11302 socket.go:59] Trying to connect to API Server I0209 10:34:32.777225 11302 socket.go:73] Successfully connected to API Server E0209 10:36:08.872945 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:36:08.872945 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 10:36:08.872945 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0209 10:36:08.873002 11302 socket.go:120] Connection closed. Reconnecting... I0209 10:36:08.946446 11302 socket.go:46] Login successful! I0209 10:36:08.946474 11302 socket.go:59] Trying to connect to API Server I0209 10:36:09.027769 11302 socket.go:73] Successfully connected to API Server E0209 11:00:38.547195 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 11:00:38.547195 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0209 11:00:38.547195 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0209 11:00:38.547288 11302 socket.go:120] Connection closed. Reconnecting... I0209 11:00:38.626855 11302 socket.go:46] Login successful! I0209 11:00:38.626884 11302 socket.go:59] Trying to connect to API Server I0209 11:00:38.702345 11302 socket.go:73] Successfully connected to API Server I0209 13:25:29.471006 11302 app.go:105] Auto update running every 6 hours I0209 13:25:29.471048 11302 app.go:106] Checking for updates I0209 13:25:35.073552 11302 updatemanager.go:29] Checking bitninja package E0209 13:25:42.069197 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 13:25:42.069197 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 13:25:42.069197 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0209 19:25:29.470198 11302 app.go:105] Auto update running every 6 hours I0209 19:25:29.470714 11302 app.go:106] Checking for updates I0209 19:25:35.054521 11302 updatemanager.go:29] Checking bitninja package E0209 19:25:42.153592 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 19:25:42.153592 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0209 19:25:42.153592 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0210 01:25:29.787906 11302 app.go:105] Auto update running every 6 hours I0210 01:25:29.788507 11302 app.go:106] Checking for updates I0210 01:25:35.342706 11302 updatemanager.go:29] Checking bitninja package E0210 01:25:42.064188 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 01:25:42.064188 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 01:25:42.064188 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0210 07:25:29.788313 11302 app.go:105] Auto update running every 6 hours I0210 07:25:29.788811 11302 app.go:106] Checking for updates I0210 07:25:35.310922 11302 updatemanager.go:29] Checking bitninja package E0210 07:25:41.969620 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 07:25:41.969620 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 07:25:41.969620 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0210 13:25:29.787916 11302 app.go:105] Auto update running every 6 hours I0210 13:25:29.787957 11302 app.go:106] Checking for updates I0210 13:25:35.432713 11302 updatemanager.go:29] Checking bitninja package E0210 13:25:42.178608 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 13:25:42.178608 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 13:25:42.178608 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0210 19:25:29.788295 11302 app.go:105] Auto update running every 6 hours I0210 19:25:29.788853 11302 app.go:106] Checking for updates I0210 19:25:35.252699 11302 updatemanager.go:29] Checking bitninja package E0210 19:25:41.592662 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 19:25:41.592662 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0210 19:25:41.592662 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0211 01:25:30.073138 11302 app.go:105] Auto update running every 6 hours I0211 01:25:30.073535 11302 app.go:106] Checking for updates I0211 01:25:35.487730 11302 updatemanager.go:29] Checking bitninja package E0211 01:25:41.622748 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 01:25:41.622748 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 01:25:41.622748 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0211 07:25:30.076654 11302 app.go:105] Auto update running every 6 hours I0211 07:25:30.078203 11302 app.go:106] Checking for updates I0211 07:25:35.646464 11302 updatemanager.go:29] Checking bitninja package E0211 07:25:42.650020 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 07:25:42.650020 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 07:25:42.650020 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 09:39:09.512824 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 09:39:09.512824 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 09:39:09.512824 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0211 09:39:09.514500 11302 socket.go:120] Connection closed. Reconnecting... I0211 09:39:09.873779 11302 socket.go:46] Login successful! I0211 09:39:09.873811 11302 socket.go:59] Trying to connect to API Server I0211 09:39:09.971148 11302 socket.go:73] Successfully connected to API Server E0211 10:29:18.158567 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 10:29:18.158567 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 10:29:18.158567 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0211 10:29:18.158852 11302 socket.go:120] Connection closed. Reconnecting... I0211 10:29:18.628130 11302 socket.go:46] Login successful! I0211 10:29:18.628160 11302 socket.go:59] Trying to connect to API Server I0211 10:29:20.414212 11302 socket.go:73] Successfully connected to API Server E0211 10:29:59.121296 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 10:29:59.121296 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 10:29:59.121296 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0211 10:29:59.121364 11302 socket.go:120] Connection closed. Reconnecting... I0211 10:29:59.251675 11302 socket.go:46] Login successful! I0211 10:29:59.251702 11302 socket.go:59] Trying to connect to API Server I0211 10:29:59.328947 11302 socket.go:73] Successfully connected to API Server I0211 13:25:30.073295 11302 app.go:105] Auto update running every 6 hours I0211 13:25:30.074084 11302 app.go:106] Checking for updates I0211 13:25:35.763070 11302 updatemanager.go:29] Checking bitninja package E0211 13:25:43.634949 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 13:25:43.634949 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 13:25:43.634949 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 14:00:31.793095 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 14:00:31.793095 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0211 14:00:31.793095 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0211 14:00:31.793173 11302 socket.go:120] Connection closed. Reconnecting... I0211 14:00:31.861195 11302 socket.go:46] Login successful! I0211 14:00:31.861224 11302 socket.go:59] Trying to connect to API Server I0211 14:00:31.940329 11302 socket.go:73] Successfully connected to API Server I0211 19:25:30.073073 11302 app.go:105] Auto update running every 6 hours I0211 19:25:30.073889 11302 app.go:106] Checking for updates I0211 19:25:35.956602 11302 updatemanager.go:29] Checking bitninja package E0211 19:25:43.363670 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 19:25:43.363670 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0211 19:25:43.363670 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0212 01:25:30.216260 11302 app.go:105] Auto update running every 6 hours I0212 01:25:30.216827 11302 app.go:106] Checking for updates I0212 01:25:35.789308 11302 updatemanager.go:29] Checking bitninja package E0212 01:25:42.622066 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 01:25:42.622066 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 01:25:42.622066 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0212 07:25:30.217414 11302 app.go:105] Auto update running every 6 hours I0212 07:25:30.218823 11302 app.go:106] Checking for updates I0212 07:25:36.015535 11302 updatemanager.go:29] Checking bitninja package E0212 07:25:43.403535 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 07:25:43.403535 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 07:25:43.403535 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 13:10:33.997927 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 13:10:33.997927 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 13:10:33.997927 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0212 13:10:34.005248 11302 socket.go:120] Connection closed. Reconnecting... I0212 13:10:34.386167 11302 socket.go:46] Login successful! I0212 13:10:34.386198 11302 socket.go:59] Trying to connect to API Server I0212 13:10:34.481715 11302 socket.go:73] Successfully connected to API Server E0212 13:23:25.697018 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 13:23:25.697018 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 13:23:25.697018 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0212 13:23:25.697787 11302 socket.go:120] Connection closed. Reconnecting... I0212 13:23:27.030809 11302 socket.go:46] Login successful! I0212 13:23:27.030850 11302 socket.go:59] Trying to connect to API Server E0212 13:24:12.032957 11302 socket.go:62] dial: read tcp 139.162.194.112:44374->136.243.56.38:443: i/o timeout E0212 13:24:12.032957 11302 socket.go:62] dial: read tcp 139.162.194.112:44374->136.243.56.38:443: i/o timeout E0212 13:24:12.032957 11302 socket.go:62] dial: read tcp 139.162.194.112:44374->136.243.56.38:443: i/o timeout I0212 13:24:12.033005 11302 socket.go:64] Retrying connection after 5s... I0212 13:24:17.099385 11302 socket.go:46] Login successful! I0212 13:24:17.099418 11302 socket.go:59] Trying to connect to API Server E0212 13:25:02.099907 11302 socket.go:62] dial: read tcp 139.162.194.112:56788->136.243.56.38:443: i/o timeout E0212 13:25:02.099907 11302 socket.go:62] dial: read tcp 139.162.194.112:56788->136.243.56.38:443: i/o timeout E0212 13:25:02.099907 11302 socket.go:62] dial: read tcp 139.162.194.112:56788->136.243.56.38:443: i/o timeout I0212 13:25:02.099961 11302 socket.go:64] Retrying connection after 5s... I0212 13:25:07.241579 11302 socket.go:46] Login successful! I0212 13:25:07.241621 11302 socket.go:59] Trying to connect to API Server I0212 13:25:30.217545 11302 app.go:105] Auto update running every 6 hours I0212 13:25:30.217579 11302 app.go:106] Checking for updates I0212 13:25:36.305808 11302 updatemanager.go:29] Checking bitninja package E0212 13:25:43.255508 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 13:25:43.255508 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 13:25:43.255508 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 13:25:52.241954 11302 socket.go:62] dial: read tcp 139.162.194.112:35578->136.243.80.118:443: i/o timeout E0212 13:25:52.241954 11302 socket.go:62] dial: read tcp 139.162.194.112:35578->136.243.80.118:443: i/o timeout E0212 13:25:52.241954 11302 socket.go:62] dial: read tcp 139.162.194.112:35578->136.243.80.118:443: i/o timeout I0212 13:25:52.242012 11302 socket.go:64] Retrying connection after 5s... I0212 13:25:57.320411 11302 socket.go:46] Login successful! I0212 13:25:57.320684 11302 socket.go:59] Trying to connect to API Server E0212 13:26:42.322047 11302 socket.go:62] dial: read tcp 139.162.194.112:34966->136.243.80.118:443: i/o timeout E0212 13:26:42.322047 11302 socket.go:62] dial: read tcp 139.162.194.112:34966->136.243.80.118:443: i/o timeout E0212 13:26:42.322047 11302 socket.go:62] dial: read tcp 139.162.194.112:34966->136.243.80.118:443: i/o timeout I0212 13:26:42.322101 11302 socket.go:64] Retrying connection after 5s... I0212 13:26:47.375523 11302 socket.go:46] Login successful! I0212 13:26:47.375556 11302 socket.go:59] Trying to connect to API Server E0212 13:27:32.376482 11302 socket.go:62] dial: read tcp 139.162.194.112:37848->136.243.72.177:443: i/o timeout E0212 13:27:32.376482 11302 socket.go:62] dial: read tcp 139.162.194.112:37848->136.243.72.177:443: i/o timeout E0212 13:27:32.376482 11302 socket.go:62] dial: read tcp 139.162.194.112:37848->136.243.72.177:443: i/o timeout I0212 13:27:32.376529 11302 socket.go:64] Retrying connection after 5s... I0212 13:27:37.420332 11302 socket.go:46] Login successful! I0212 13:27:37.420361 11302 socket.go:59] Trying to connect to API Server E0212 13:28:22.420711 11302 socket.go:62] dial: read tcp 139.162.194.112:35518->136.243.56.38:443: i/o timeout E0212 13:28:22.420711 11302 socket.go:62] dial: read tcp 139.162.194.112:35518->136.243.56.38:443: i/o timeout E0212 13:28:22.420711 11302 socket.go:62] dial: read tcp 139.162.194.112:35518->136.243.56.38:443: i/o timeout I0212 13:28:22.420788 11302 socket.go:64] Retrying connection after 5s... I0212 13:28:27.745326 11302 socket.go:46] Login successful! I0212 13:28:27.745361 11302 socket.go:59] Trying to connect to API Server E0212 13:29:12.746198 11302 socket.go:62] dial: read tcp 139.162.194.112:48884->136.243.80.118:443: i/o timeout E0212 13:29:12.746198 11302 socket.go:62] dial: read tcp 139.162.194.112:48884->136.243.80.118:443: i/o timeout E0212 13:29:12.746198 11302 socket.go:62] dial: read tcp 139.162.194.112:48884->136.243.80.118:443: i/o timeout I0212 13:29:12.746247 11302 socket.go:64] Retrying connection after 5s... I0212 13:29:17.792229 11302 socket.go:46] Login successful! I0212 13:29:17.792260 11302 socket.go:59] Trying to connect to API Server E0212 13:30:02.792493 11302 socket.go:62] dial: read tcp 139.162.194.112:36598->136.243.56.38:443: i/o timeout E0212 13:30:02.792493 11302 socket.go:62] dial: read tcp 139.162.194.112:36598->136.243.56.38:443: i/o timeout E0212 13:30:02.792493 11302 socket.go:62] dial: read tcp 139.162.194.112:36598->136.243.56.38:443: i/o timeout I0212 13:30:02.792544 11302 socket.go:64] Retrying connection after 5s... I0212 13:30:07.880075 11302 socket.go:46] Login successful! I0212 13:30:07.880111 11302 socket.go:59] Trying to connect to API Server E0212 13:30:52.881119 11302 socket.go:62] dial: read tcp 139.162.194.112:34414->136.243.80.118:443: i/o timeout E0212 13:30:52.881119 11302 socket.go:62] dial: read tcp 139.162.194.112:34414->136.243.80.118:443: i/o timeout E0212 13:30:52.881119 11302 socket.go:62] dial: read tcp 139.162.194.112:34414->136.243.80.118:443: i/o timeout I0212 13:30:52.881170 11302 socket.go:64] Retrying connection after 5s... I0212 13:30:57.964819 11302 socket.go:46] Login successful! I0212 13:30:57.964853 11302 socket.go:59] Trying to connect to API Server E0212 13:31:42.965129 11302 socket.go:62] dial: read tcp 139.162.194.112:50676->136.243.80.118:443: i/o timeout E0212 13:31:42.965129 11302 socket.go:62] dial: read tcp 139.162.194.112:50676->136.243.80.118:443: i/o timeout E0212 13:31:42.965129 11302 socket.go:62] dial: read tcp 139.162.194.112:50676->136.243.80.118:443: i/o timeout I0212 13:31:42.965176 11302 socket.go:64] Retrying connection after 5s... I0212 13:31:48.021184 11302 socket.go:46] Login successful! I0212 13:31:48.021213 11302 socket.go:59] Trying to connect to API Server I0212 13:32:03.507372 11302 socket.go:73] Successfully connected to API Server E0212 18:49:47.943701 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 18:49:47.943701 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 18:49:47.943701 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0212 18:49:47.944353 11302 socket.go:120] Connection closed. Reconnecting... I0212 18:49:48.138105 11302 socket.go:46] Login successful! I0212 18:49:48.138141 11302 socket.go:59] Trying to connect to API Server I0212 18:49:48.347372 11302 socket.go:73] Successfully connected to API Server E0212 19:00:35.982760 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 19:00:35.982760 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0212 19:00:35.982760 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0212 19:00:35.982863 11302 socket.go:120] Connection closed. Reconnecting... I0212 19:00:36.025197 11302 socket.go:46] Login successful! I0212 19:00:36.025231 11302 socket.go:59] Trying to connect to API Server I0212 19:00:36.093104 11302 socket.go:73] Successfully connected to API Server I0212 19:25:30.216572 11302 app.go:105] Auto update running every 6 hours I0212 19:25:30.216616 11302 app.go:106] Checking for updates I0212 19:25:35.841287 11302 updatemanager.go:29] Checking bitninja package E0212 19:25:42.574623 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 19:25:42.574623 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0212 19:25:42.574623 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0213 01:25:30.695516 11302 app.go:105] Auto update running every 6 hours I0213 01:25:30.696447 11302 app.go:106] Checking for updates I0213 01:25:36.529698 11302 updatemanager.go:29] Checking bitninja package E0213 01:25:43.798142 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 01:25:43.798142 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 01:25:43.798142 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 02:00:38.310455 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 02:00:38.310455 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 02:00:38.310455 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 02:00:38.310543 11302 socket.go:120] Connection closed. Reconnecting... I0213 02:00:38.415729 11302 socket.go:46] Login successful! I0213 02:00:38.415756 11302 socket.go:59] Trying to connect to API Server I0213 02:00:38.491032 11302 socket.go:73] Successfully connected to API Server I0213 07:25:30.702117 11302 app.go:105] Auto update running every 6 hours I0213 07:25:30.703716 11302 app.go:106] Checking for updates I0213 07:25:36.303981 11302 updatemanager.go:29] Checking bitninja package E0213 07:25:43.437177 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 07:25:43.437177 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 07:25:43.437177 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 09:19:33.535921 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 09:19:33.535921 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 09:19:33.535921 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 09:19:33.538156 11302 socket.go:120] Connection closed. Reconnecting... I0213 09:19:33.700319 11302 socket.go:46] Login successful! I0213 09:19:33.700353 11302 socket.go:59] Trying to connect to API Server I0213 09:19:33.786527 11302 socket.go:73] Successfully connected to API Server E0213 11:17:01.386665 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 11:17:01.386665 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 11:17:01.386665 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 11:17:01.387237 11302 socket.go:120] Connection closed. Reconnecting... I0213 11:17:02.590645 11302 socket.go:46] Login successful! I0213 11:17:02.590679 11302 socket.go:59] Trying to connect to API Server E0213 11:17:47.591522 11302 socket.go:62] dial: read tcp 139.162.194.112:48930->5.9.124.26:443: i/o timeout E0213 11:17:47.591522 11302 socket.go:62] dial: read tcp 139.162.194.112:48930->5.9.124.26:443: i/o timeout E0213 11:17:47.591522 11302 socket.go:62] dial: read tcp 139.162.194.112:48930->5.9.124.26:443: i/o timeout I0213 11:17:47.591574 11302 socket.go:64] Retrying connection after 5s... I0213 11:17:52.653255 11302 socket.go:46] Login successful! I0213 11:17:52.653285 11302 socket.go:59] Trying to connect to API Server E0213 11:18:37.653927 11302 socket.go:62] dial: read tcp 139.162.194.112:48356->136.243.56.38:443: i/o timeout E0213 11:18:37.653927 11302 socket.go:62] dial: read tcp 139.162.194.112:48356->136.243.56.38:443: i/o timeout E0213 11:18:37.653927 11302 socket.go:62] dial: read tcp 139.162.194.112:48356->136.243.56.38:443: i/o timeout I0213 11:18:37.653979 11302 socket.go:64] Retrying connection after 5s... I0213 11:18:42.710471 11302 socket.go:46] Login successful! I0213 11:18:42.710502 11302 socket.go:59] Trying to connect to API Server E0213 11:19:27.711672 11302 socket.go:62] dial: read tcp 139.162.194.112:36412->136.243.72.177:443: i/o timeout E0213 11:19:27.711672 11302 socket.go:62] dial: read tcp 139.162.194.112:36412->136.243.72.177:443: i/o timeout E0213 11:19:27.711672 11302 socket.go:62] dial: read tcp 139.162.194.112:36412->136.243.72.177:443: i/o timeout I0213 11:19:27.711737 11302 socket.go:64] Retrying connection after 5s... I0213 11:19:32.747159 11302 socket.go:46] Login successful! I0213 11:19:32.747189 11302 socket.go:59] Trying to connect to API Server E0213 11:20:17.748328 11302 socket.go:62] dial: read tcp 139.162.194.112:45966->136.243.72.177:443: i/o timeout E0213 11:20:17.748328 11302 socket.go:62] dial: read tcp 139.162.194.112:45966->136.243.72.177:443: i/o timeout E0213 11:20:17.748328 11302 socket.go:62] dial: read tcp 139.162.194.112:45966->136.243.72.177:443: i/o timeout I0213 11:20:17.748388 11302 socket.go:64] Retrying connection after 5s... I0213 11:20:22.878225 11302 socket.go:46] Login successful! I0213 11:20:22.878263 11302 socket.go:59] Trying to connect to API Server I0213 11:20:23.105167 11302 socket.go:73] Successfully connected to API Server E0213 11:31:44.402065 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 11:31:44.402065 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 11:31:44.402065 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 11:31:44.402153 11302 socket.go:120] Connection closed. Reconnecting... I0213 11:31:44.451901 11302 socket.go:46] Login successful! I0213 11:31:44.451932 11302 socket.go:59] Trying to connect to API Server I0213 11:31:44.577220 11302 socket.go:73] Successfully connected to API Server E0213 12:22:52.704926 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:22:52.704926 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:22:52.704926 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 12:22:52.705419 11302 socket.go:120] Connection closed. Reconnecting... I0213 12:22:54.879233 11302 socket.go:46] Login successful! I0213 12:22:54.879484 11302 socket.go:59] Trying to connect to API Server I0213 12:22:54.951993 11302 socket.go:73] Successfully connected to API Server E0213 12:28:28.445890 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:28:28.445890 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:28:28.445890 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 12:28:28.445991 11302 socket.go:120] Connection closed. Reconnecting... I0213 12:28:29.695855 11302 socket.go:46] Login successful! I0213 12:28:29.695887 11302 socket.go:59] Trying to connect to API Server I0213 12:28:29.799978 11302 socket.go:73] Successfully connected to API Server E0213 12:38:18.465636 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:38:18.465636 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:38:18.465636 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 12:38:18.465704 11302 socket.go:120] Connection closed. Reconnecting... I0213 12:38:19.521908 11302 socket.go:46] Login successful! I0213 12:38:19.521951 11302 socket.go:59] Trying to connect to API Server I0213 12:38:19.613248 11302 socket.go:73] Successfully connected to API Server E0213 12:43:00.645224 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:43:00.645224 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 12:43:00.645224 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 12:43:00.645302 11302 socket.go:120] Connection closed. Reconnecting... I0213 12:43:02.822959 11302 socket.go:46] Login successful! I0213 12:43:02.822995 11302 socket.go:59] Trying to connect to API Server I0213 12:43:02.906450 11302 socket.go:73] Successfully connected to API Server E0213 13:07:21.938386 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 13:07:21.938386 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 13:07:21.938386 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 13:07:21.938482 11302 socket.go:120] Connection closed. Reconnecting... I0213 13:07:23.216852 11302 socket.go:46] Login successful! I0213 13:07:23.216882 11302 socket.go:59] Trying to connect to API Server I0213 13:07:23.316357 11302 socket.go:73] Successfully connected to API Server I0213 13:25:30.695261 11302 app.go:105] Auto update running every 6 hours I0213 13:25:30.695306 11302 app.go:106] Checking for updates I0213 13:25:36.412885 11302 updatemanager.go:29] Checking bitninja package E0213 13:25:43.054266 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 13:25:43.054266 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 13:25:43.054266 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 14:14:12.407329 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 14:14:12.407329 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 14:14:12.407329 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 14:14:12.407401 11302 socket.go:120] Connection closed. Reconnecting... I0213 14:14:13.550987 11302 socket.go:46] Login successful! I0213 14:14:13.551020 11302 socket.go:59] Trying to connect to API Server E0213 14:14:58.551767 11302 socket.go:62] dial: read tcp 139.162.194.112:38990->136.243.56.38:443: i/o timeout E0213 14:14:58.551767 11302 socket.go:62] dial: read tcp 139.162.194.112:38990->136.243.56.38:443: i/o timeout E0213 14:14:58.551767 11302 socket.go:62] dial: read tcp 139.162.194.112:38990->136.243.56.38:443: i/o timeout I0213 14:14:58.551818 11302 socket.go:64] Retrying connection after 5s... I0213 14:15:09.989085 11302 socket.go:46] Login successful! I0213 14:15:09.989118 11302 socket.go:59] Trying to connect to API Server I0213 14:15:10.070622 11302 socket.go:73] Successfully connected to API Server E0213 17:00:32.606221 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 17:00:32.606221 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 17:00:32.606221 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 17:00:32.606725 11302 socket.go:120] Connection closed. Reconnecting... I0213 17:00:32.935457 11302 socket.go:46] Login successful! I0213 17:00:32.935489 11302 socket.go:59] Trying to connect to API Server I0213 17:00:33.023916 11302 socket.go:73] Successfully connected to API Server E0213 19:00:31.721187 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 19:00:31.721187 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 19:00:31.721187 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 19:00:31.721839 11302 socket.go:120] Connection closed. Reconnecting... I0213 19:00:31.814133 11302 socket.go:46] Login successful! I0213 19:00:31.814173 11302 socket.go:59] Trying to connect to API Server I0213 19:00:31.906446 11302 socket.go:73] Successfully connected to API Server I0213 19:25:30.695285 11302 app.go:105] Auto update running every 6 hours I0213 19:25:30.695323 11302 app.go:106] Checking for updates I0213 19:25:36.581699 11302 updatemanager.go:29] Checking bitninja package E0213 19:25:43.870181 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 19:25:43.870181 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 19:25:43.870181 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0213 20:03:09.079298 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 20:03:09.079298 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 20:03:09.079298 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 20:03:09.079376 11302 socket.go:120] Connection closed. Reconnecting... I0213 20:03:09.231890 11302 socket.go:46] Login successful! I0213 20:03:09.231920 11302 socket.go:59] Trying to connect to API Server I0213 20:03:09.421806 11302 socket.go:73] Successfully connected to API Server E0213 20:13:09.445537 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 20:13:09.445537 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 20:13:09.445537 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 20:13:09.445619 11302 socket.go:120] Connection closed. Reconnecting... I0213 20:13:09.592359 11302 socket.go:46] Login successful! I0213 20:13:09.592413 11302 socket.go:59] Trying to connect to API Server I0213 20:13:10.002209 11302 socket.go:73] Successfully connected to API Server E0213 20:17:45.647856 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 20:17:45.647856 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 20:17:45.647856 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 20:17:45.647933 11302 socket.go:120] Connection closed. Reconnecting... I0213 20:17:45.795493 11302 socket.go:46] Login successful! I0213 20:17:45.795520 11302 socket.go:59] Trying to connect to API Server I0213 20:17:47.995254 11302 socket.go:73] Successfully connected to API Server E0213 22:00:35.965165 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 22:00:35.965165 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0213 22:00:35.965165 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0213 22:00:35.965844 11302 socket.go:120] Connection closed. Reconnecting... I0213 22:00:36.064255 11302 socket.go:46] Login successful! I0213 22:00:36.064289 11302 socket.go:59] Trying to connect to API Server I0213 22:00:36.391943 11302 socket.go:73] Successfully connected to API Server E0214 00:43:05.568147 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0214 00:43:05.568147 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0214 00:43:05.568147 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0214 00:43:05.568692 11302 socket.go:120] Connection closed. Reconnecting... I0214 00:43:05.820948 11302 socket.go:46] Login successful! I0214 00:43:05.820982 11302 socket.go:59] Trying to connect to API Server I0214 00:43:05.899667 11302 socket.go:73] Successfully connected to API Server I0214 01:25:31.176667 11302 app.go:105] Auto update running every 6 hours I0214 01:25:31.176701 11302 app.go:106] Checking for updates I0214 01:25:36.954445 11302 updatemanager.go:29] Checking bitninja package E0214 01:25:43.905671 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 01:25:43.905671 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 01:25:43.905671 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0214 07:25:31.179948 11302 app.go:105] Auto update running every 6 hours I0214 07:25:31.181516 11302 app.go:106] Checking for updates I0214 07:25:36.828719 11302 updatemanager.go:29] Checking bitninja package E0214 07:25:43.820172 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 07:25:43.820172 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 07:25:43.820172 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0214 13:25:31.176289 11302 app.go:105] Auto update running every 6 hours I0214 13:25:31.178182 11302 app.go:106] Checking for updates I0214 13:25:37.001697 11302 updatemanager.go:29] Checking bitninja package E0214 13:25:44.151065 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 13:25:44.151065 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 13:25:44.151065 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 15:07:44.351036 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0214 15:07:44.351036 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0214 15:07:44.351036 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0214 15:07:44.352349 11302 socket.go:120] Connection closed. Reconnecting... I0214 15:07:44.636649 11302 socket.go:46] Login successful! I0214 15:07:44.636680 11302 socket.go:59] Trying to connect to API Server I0214 15:07:44.958862 11302 socket.go:73] Successfully connected to API Server I0214 19:25:31.176809 11302 app.go:105] Auto update running every 6 hours I0214 19:25:31.177486 11302 app.go:106] Checking for updates I0214 19:25:36.918716 11302 updatemanager.go:29] Checking bitninja package E0214 19:25:43.651986 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 19:25:43.651986 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0214 19:25:43.651986 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0215 01:25:31.598605 11302 app.go:105] Auto update running every 6 hours I0215 01:25:31.599562 11302 app.go:106] Checking for updates I0215 01:25:37.192770 11302 updatemanager.go:29] Checking bitninja package E0215 01:25:43.817896 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 01:25:43.817896 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 01:25:43.817896 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 07:12:36.899780 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0215 07:12:36.899780 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0215 07:12:36.899780 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0215 07:12:36.911881 11302 socket.go:120] Connection closed. Reconnecting... I0215 07:12:37.026474 11302 socket.go:46] Login successful! I0215 07:12:37.026503 11302 socket.go:59] Trying to connect to API Server I0215 07:12:37.113859 11302 socket.go:73] Successfully connected to API Server I0215 07:25:31.599117 11302 app.go:105] Auto update running every 6 hours I0215 07:25:31.599155 11302 app.go:106] Checking for updates I0215 07:25:37.236173 11302 updatemanager.go:29] Checking bitninja package E0215 07:25:44.316872 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 07:25:44.316872 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 07:25:44.316872 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0215 13:25:31.598122 11302 app.go:105] Auto update running every 6 hours I0215 13:25:31.598493 11302 app.go:106] Checking for updates I0215 13:25:37.179827 11302 updatemanager.go:29] Checking bitninja package E0215 13:25:43.775202 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 13:25:43.775202 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 13:25:43.775202 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0215 19:25:31.598194 11302 app.go:105] Auto update running every 6 hours I0215 19:25:31.598469 11302 app.go:106] Checking for updates I0215 19:25:37.172160 11302 updatemanager.go:29] Checking bitninja package E0215 19:25:43.818104 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 19:25:43.818104 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 19:25:43.818104 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0215 22:40:05.627967 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0215 22:40:05.627967 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0215 22:40:05.627967 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0215 22:40:05.629414 11302 socket.go:120] Connection closed. Reconnecting... I0215 22:40:06.854765 11302 socket.go:46] Login successful! I0215 22:40:06.854799 11302 socket.go:59] Trying to connect to API Server I0215 22:40:07.005141 11302 socket.go:73] Successfully connected to API Server I0216 01:25:31.651065 11302 app.go:105] Auto update running every 6 hours I0216 01:25:31.651417 11302 app.go:106] Checking for updates I0216 01:25:37.464975 11302 updatemanager.go:29] Checking bitninja package E0216 01:25:44.896605 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 01:25:44.896605 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 01:25:44.896605 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 05:00:32.262810 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 05:00:32.262810 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 05:00:32.262810 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 05:00:32.263627 11302 socket.go:120] Connection closed. Reconnecting... I0216 05:00:32.368796 11302 socket.go:46] Login successful! I0216 05:00:32.368829 11302 socket.go:59] Trying to connect to API Server I0216 05:00:32.454906 11302 socket.go:73] Successfully connected to API Server I0216 07:25:31.649007 11302 app.go:105] Auto update running every 6 hours I0216 07:25:31.649583 11302 app.go:106] Checking for updates I0216 07:25:37.068723 11302 updatemanager.go:29] Checking bitninja package E0216 07:25:43.377150 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 07:25:43.377150 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 07:25:43.377150 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 11:00:31.943144 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 11:00:31.943144 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 11:00:31.943144 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 11:00:31.943798 11302 socket.go:120] Connection closed. Reconnecting... I0216 11:00:32.059083 11302 socket.go:46] Login successful! I0216 11:00:32.059124 11302 socket.go:59] Trying to connect to API Server I0216 11:00:32.147423 11302 socket.go:73] Successfully connected to API Server E0216 12:00:33.076158 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 12:00:33.076158 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 12:00:33.076158 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 12:00:33.076240 11302 socket.go:120] Connection closed. Reconnecting... I0216 12:00:33.136044 11302 socket.go:46] Login successful! I0216 12:00:33.136078 11302 socket.go:59] Trying to connect to API Server I0216 12:00:33.228988 11302 socket.go:73] Successfully connected to API Server E0216 12:55:34.535047 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 500 E0216 12:55:34.535047 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 500 E0216 12:55:34.535047 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 500 E0216 13:01:55.250593 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 13:01:55.250593 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 13:01:55.250593 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 13:01:55.250685 11302 socket.go:120] Connection closed. Reconnecting... E0216 13:02:08.352825 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0216 13:02:08.352825 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0216 13:02:08.352825 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0216 13:03:58.385738 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [500]. Response was: [{"statusCode":500,"message":"Internal server error"}]. Retrying in 60 seconds... E0216 13:03:58.385738 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [500]. Response was: [{"statusCode":500,"message":"Internal server error"}]. Retrying in 60 seconds... E0216 13:03:58.385738 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [500]. Response was: [{"statusCode":500,"message":"Internal server error"}]. Retrying in 60 seconds... I0216 13:04:58.425225 11302 socket.go:46] Login successful! I0216 13:04:58.425260 11302 socket.go:59] Trying to connect to API Server I0216 13:04:58.520113 11302 socket.go:73] Successfully connected to API Server E0216 13:11:31.014142 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 13:11:31.014142 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 13:11:31.014142 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 13:11:31.014212 11302 socket.go:120] Connection closed. Reconnecting... I0216 13:11:31.047645 11302 socket.go:46] Login successful! I0216 13:11:31.047673 11302 socket.go:59] Trying to connect to API Server I0216 13:11:31.337176 11302 socket.go:73] Successfully connected to API Server E0216 13:16:31.734490 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:16:31.734490 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:16:31.734490 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:21:31.972447 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:21:31.972447 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:21:31.972447 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 I0216 13:25:31.649708 11302 app.go:105] Auto update running every 6 hours I0216 13:25:31.649747 11302 app.go:106] Checking for updates I0216 13:25:37.400567 11302 updatemanager.go:29] Checking bitninja package E0216 13:25:44.349431 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 13:25:44.349431 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 13:25:44.349431 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 13:26:31.732890 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:26:31.732890 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:26:31.732890 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:31:31.735116 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:31:31.735116 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:31:31.735116 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:36:31.743639 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:36:31.743639 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:36:31.743639 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:41:31.724893 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:41:31.724893 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:41:31.724893 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:43:32.457820 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 13:43:32.457820 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 13:43:32.457820 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 13:43:32.457886 11302 socket.go:120] Connection closed. Reconnecting... I0216 13:43:35.666260 11302 socket.go:46] Login successful! I0216 13:43:35.666293 11302 socket.go:59] Trying to connect to API Server I0216 13:43:35.743428 11302 socket.go:73] Successfully connected to API Server E0216 13:46:31.734054 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:46:31.734054 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:46:31.734054 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:51:31.724989 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:51:31.724989 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:51:31.724989 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:56:31.731264 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:56:31.731264 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 13:56:31.731264 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:00:32.369395 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 14:00:32.369395 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 14:00:32.369395 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 14:00:32.369484 11302 socket.go:120] Connection closed. Reconnecting... I0216 14:00:32.436051 11302 socket.go:46] Login successful! I0216 14:00:32.436078 11302 socket.go:59] Trying to connect to API Server I0216 14:00:32.520672 11302 socket.go:73] Successfully connected to API Server E0216 14:01:31.853196 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:01:31.853196 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:01:31.853196 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:06:31.728008 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:06:31.728008 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:06:31.728008 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:11:31.746759 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:11:31.746759 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:11:31.746759 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:16:31.741013 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:16:31.741013 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:16:31.741013 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:21:31.727023 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:21:31.727023 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:21:31.727023 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:26:31.737740 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:26:31.737740 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:26:31.737740 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:31:31.773394 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:31:31.773394 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:31:31.773394 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:36:31.726463 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:36:31.726463 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:36:31.726463 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:41:31.728884 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:41:31.728884 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:41:31.728884 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:46:31.733518 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:46:31.733518 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:46:31.733518 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:51:31.722858 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:51:31.722858 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:51:31.722858 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:56:31.732699 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:56:31.732699 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 14:56:31.732699 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:01:31.738854 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:01:31.738854 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:01:31.738854 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:06:31.723921 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:06:31.723921 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:06:31.723921 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:11:31.730788 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:11:31.730788 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:11:31.730788 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:16:31.730426 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:16:31.730426 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:16:31.730426 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:21:31.723100 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:21:31.723100 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:21:31.723100 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:26:31.987955 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:26:31.987955 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:26:31.987955 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:31:31.738788 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:31:31.738788 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:31:31.738788 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:36:31.722857 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:36:31.722857 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:36:31.722857 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:41:31.926134 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:41:31.926134 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:41:31.926134 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:46:31.741536 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:46:31.741536 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:46:31.741536 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:51:31.726372 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:51:31.726372 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:51:31.726372 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:56:31.936988 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:56:31.936988 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 15:56:31.936988 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:01:31.881845 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:01:31.881845 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:01:31.881845 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:06:31.722635 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:06:31.722635 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:06:31.722635 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:11:31.734823 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:11:31.734823 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:11:31.734823 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:16:31.764399 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:16:31.764399 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:16:31.764399 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:21:31.729628 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:21:31.729628 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:21:31.729628 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:26:31.739017 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:26:31.739017 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:26:31.739017 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0216 16:59:37.639302 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 16:59:37.639302 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 16:59:37.639302 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 16:59:37.639375 11302 socket.go:120] Connection closed. Reconnecting... I0216 16:59:37.762446 11302 socket.go:46] Login successful! I0216 16:59:37.762508 11302 socket.go:59] Trying to connect to API Server I0216 16:59:37.828676 11302 socket.go:73] Successfully connected to API Server I0216 19:25:31.649596 11302 app.go:105] Auto update running every 6 hours I0216 19:25:31.649887 11302 app.go:106] Checking for updates I0216 19:25:37.479025 11302 updatemanager.go:29] Checking bitninja package E0216 19:25:44.512965 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 19:25:44.512965 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 19:25:44.512965 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0216 21:39:23.181379 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 21:39:23.181379 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0216 21:39:23.181379 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0216 21:39:23.181702 11302 socket.go:120] Connection closed. Reconnecting... I0216 21:39:23.375238 11302 socket.go:46] Login successful! I0216 21:39:23.375267 11302 socket.go:59] Trying to connect to API Server I0216 21:39:23.498761 11302 socket.go:73] Successfully connected to API Server I0217 01:25:32.673727 11302 app.go:105] Auto update running every 6 hours I0217 01:25:32.674280 11302 app.go:106] Checking for updates I0217 01:25:38.193122 11302 updatemanager.go:29] Checking bitninja package E0217 01:25:44.889385 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 01:25:44.889385 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 01:25:44.889385 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 05:17:07.709995 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 05:17:07.709995 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 05:17:07.709995 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 05:17:07.713726 11302 socket.go:120] Connection closed. Reconnecting... I0217 05:17:07.925757 11302 socket.go:46] Login successful! I0217 05:17:07.925787 11302 socket.go:59] Trying to connect to API Server I0217 05:17:08.054385 11302 socket.go:73] Successfully connected to API Server E0217 06:22:21.192392 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 06:22:21.192392 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 06:22:21.192392 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 06:22:21.192468 11302 socket.go:120] Connection closed. Reconnecting... I0217 06:22:21.366646 11302 socket.go:46] Login successful! I0217 06:22:21.366676 11302 socket.go:59] Trying to connect to API Server I0217 06:22:21.691826 11302 socket.go:73] Successfully connected to API Server I0217 07:25:32.674169 11302 app.go:105] Auto update running every 6 hours I0217 07:25:32.675015 11302 app.go:106] Checking for updates I0217 07:25:38.225327 11302 updatemanager.go:29] Checking bitninja package E0217 07:25:44.596520 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 07:25:44.596520 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 07:25:44.596520 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 09:00:32.183962 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 09:00:32.183962 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 09:00:32.183962 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 09:00:32.184507 11302 socket.go:120] Connection closed. Reconnecting... I0217 09:00:32.371910 11302 socket.go:46] Login successful! I0217 09:00:32.371958 11302 socket.go:59] Trying to connect to API Server I0217 09:00:32.451793 11302 socket.go:73] Successfully connected to API Server I0217 13:25:32.675195 11302 app.go:105] Auto update running every 6 hours I0217 13:25:32.676239 11302 app.go:106] Checking for updates I0217 13:25:38.294987 11302 updatemanager.go:29] Checking bitninja package E0217 13:25:44.930161 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 13:25:44.930161 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 13:25:44.930161 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 15:59:11.700489 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 15:59:11.700489 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 15:59:11.700489 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 15:59:11.701304 11302 socket.go:120] Connection closed. Reconnecting... I0217 15:59:11.852991 11302 socket.go:46] Login successful! I0217 15:59:11.853026 11302 socket.go:59] Trying to connect to API Server I0217 15:59:12.478028 11302 socket.go:73] Successfully connected to API Server E0217 16:00:32.118294 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 16:00:32.118294 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 16:00:32.118294 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 16:00:32.118391 11302 socket.go:120] Connection closed. Reconnecting... I0217 16:00:32.282763 11302 socket.go:46] Login successful! I0217 16:00:32.282801 11302 socket.go:59] Trying to connect to API Server I0217 16:00:32.961230 11302 socket.go:73] Successfully connected to API Server E0217 16:42:27.120369 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 16:42:27.120369 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 16:42:27.120369 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 16:42:27.120595 11302 socket.go:120] Connection closed. Reconnecting... I0217 16:42:27.249364 11302 socket.go:46] Login successful! I0217 16:42:27.249397 11302 socket.go:59] Trying to connect to API Server I0217 16:42:27.330050 11302 socket.go:73] Successfully connected to API Server E0217 19:00:32.118367 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 19:00:32.118367 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0217 19:00:32.118367 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0217 19:00:32.118444 11302 socket.go:120] Connection closed. Reconnecting... I0217 19:00:32.386204 11302 socket.go:46] Login successful! I0217 19:00:32.386234 11302 socket.go:59] Trying to connect to API Server I0217 19:00:32.474582 11302 socket.go:73] Successfully connected to API Server I0217 19:25:32.673523 11302 app.go:105] Auto update running every 6 hours I0217 19:25:32.674106 11302 app.go:106] Checking for updates I0217 19:25:38.553812 11302 updatemanager.go:29] Checking bitninja package E0217 19:25:45.804915 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 19:25:45.804915 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0217 19:25:45.804915 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 00:19:00.286514 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 00:19:00.286514 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 00:19:00.286514 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 00:19:00.286910 11302 socket.go:120] Connection closed. Reconnecting... I0218 00:19:00.439487 11302 socket.go:46] Login successful! I0218 00:19:00.439515 11302 socket.go:59] Trying to connect to API Server I0218 00:19:00.526604 11302 socket.go:73] Successfully connected to API Server I0218 01:25:32.634078 11302 app.go:105] Auto update running every 6 hours I0218 01:25:32.634131 11302 app.go:106] Checking for updates I0218 01:25:38.131081 11302 updatemanager.go:29] Checking bitninja package E0218 01:25:44.733657 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 01:25:44.733657 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 01:25:44.733657 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 03:26:47.502662 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 03:26:47.502662 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 03:26:47.502662 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 03:26:47.502995 11302 socket.go:120] Connection closed. Reconnecting... I0218 03:26:47.644238 11302 socket.go:46] Login successful! I0218 03:26:47.644271 11302 socket.go:59] Trying to connect to API Server I0218 03:26:47.728866 11302 socket.go:73] Successfully connected to API Server I0218 07:25:32.633933 11302 app.go:105] Auto update running every 6 hours I0218 07:25:32.634976 11302 app.go:106] Checking for updates I0218 07:25:38.253306 11302 updatemanager.go:29] Checking bitninja package E0218 07:25:44.770798 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 07:25:44.770798 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 07:25:44.770798 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 08:40:16.500170 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 08:40:16.500170 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 08:40:16.500170 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 08:40:16.500253 11302 socket.go:120] Connection closed. Reconnecting... I0218 08:40:20.105992 11302 socket.go:46] Login successful! I0218 08:40:20.106026 11302 socket.go:59] Trying to connect to API Server I0218 08:40:20.340379 11302 socket.go:73] Successfully connected to API Server E0218 08:41:23.280247 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 08:41:23.280247 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 08:41:23.280247 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 08:41:23.280315 11302 socket.go:120] Connection closed. Reconnecting... I0218 08:41:23.326695 11302 socket.go:46] Login successful! I0218 08:41:23.326756 11302 socket.go:59] Trying to connect to API Server I0218 08:41:23.411929 11302 socket.go:73] Successfully connected to API Server E0218 09:00:31.536708 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 09:00:31.536708 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 09:00:31.536708 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 09:00:31.536801 11302 socket.go:120] Connection closed. Reconnecting... I0218 09:00:32.145251 11302 socket.go:46] Login successful! I0218 09:00:32.145286 11302 socket.go:59] Trying to connect to API Server I0218 09:00:32.255668 11302 socket.go:73] Successfully connected to API Server E0218 10:09:09.841619 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 10:09:09.841619 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 10:09:09.841619 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 10:09:09.842175 11302 socket.go:120] Connection closed. Reconnecting... I0218 10:09:10.414982 11302 socket.go:46] Login successful! I0218 10:09:10.415015 11302 socket.go:59] Trying to connect to API Server I0218 10:09:10.498251 11302 socket.go:73] Successfully connected to API Server E0218 12:25:55.595515 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 12:25:55.595515 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 12:25:55.595515 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 12:25:55.595987 11302 socket.go:120] Connection closed. Reconnecting... I0218 12:25:55.723955 11302 socket.go:46] Login successful! I0218 12:25:55.723985 11302 socket.go:59] Trying to connect to API Server I0218 12:25:55.826168 11302 socket.go:73] Successfully connected to API Server E0218 12:28:55.479853 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 12:28:55.479853 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 12:28:55.479853 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 12:28:55.479925 11302 socket.go:120] Connection closed. Reconnecting... I0218 12:28:55.662055 11302 socket.go:46] Login successful! I0218 12:28:55.662106 11302 socket.go:59] Trying to connect to API Server I0218 12:28:55.742173 11302 socket.go:73] Successfully connected to API Server E0218 13:12:15.926796 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 13:12:15.926796 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 13:12:15.926796 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 13:12:15.926900 11302 socket.go:120] Connection closed. Reconnecting... I0218 13:12:17.932207 11302 socket.go:46] Login successful! I0218 13:12:17.932240 11302 socket.go:59] Trying to connect to API Server I0218 13:12:18.017001 11302 socket.go:73] Successfully connected to API Server E0218 13:22:51.089731 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 13:22:51.089731 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 13:22:51.089731 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 13:22:51.089806 11302 socket.go:120] Connection closed. Reconnecting... I0218 13:22:54.954971 11302 socket.go:46] Login successful! I0218 13:22:54.955000 11302 socket.go:59] Trying to connect to API Server I0218 13:22:55.031928 11302 socket.go:73] Successfully connected to API Server I0218 13:25:32.634394 11302 app.go:105] Auto update running every 6 hours I0218 13:25:32.634430 11302 app.go:106] Checking for updates I0218 13:25:38.327246 11302 updatemanager.go:29] Checking bitninja package E0218 13:25:45.236896 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 13:25:45.236896 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 13:25:45.236896 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 16:00:45.363363 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 16:00:45.363363 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 16:00:45.363363 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 16:00:45.363753 11302 socket.go:120] Connection closed. Reconnecting... I0218 16:00:45.438823 11302 socket.go:46] Login successful! I0218 16:00:45.438847 11302 socket.go:59] Trying to connect to API Server I0218 16:00:45.521649 11302 socket.go:73] Successfully connected to API Server E0218 17:00:44.437459 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 17:00:44.437459 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0218 17:00:44.437459 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0218 17:00:44.438074 11302 socket.go:120] Connection closed. Reconnecting... I0218 17:00:44.502426 11302 socket.go:46] Login successful! I0218 17:00:44.502460 11302 socket.go:59] Trying to connect to API Server I0218 17:00:44.586885 11302 socket.go:73] Successfully connected to API Server I0218 19:25:32.633460 11302 app.go:105] Auto update running every 6 hours I0218 19:25:32.633979 11302 app.go:106] Checking for updates I0218 19:25:38.165769 11302 updatemanager.go:29] Checking bitninja package E0218 19:25:44.659279 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 19:25:44.659279 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0218 19:25:44.659279 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 00:45:06.409728 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 00:45:06.409728 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 00:45:06.409728 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 00:45:06.410085 11302 socket.go:120] Connection closed. Reconnecting... I0219 00:45:08.610581 11302 socket.go:46] Login successful! I0219 00:45:08.610610 11302 socket.go:59] Trying to connect to API Server I0219 00:45:08.725480 11302 socket.go:73] Successfully connected to API Server I0219 01:25:33.467110 11302 app.go:105] Auto update running every 6 hours I0219 01:25:33.467158 11302 app.go:106] Checking for updates I0219 01:25:38.901225 11302 updatemanager.go:29] Checking bitninja package E0219 01:25:45.367542 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 01:25:45.367542 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 01:25:45.367542 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 02:28:14.622291 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 02:28:14.622291 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 02:28:14.622291 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 02:28:14.622398 11302 socket.go:120] Connection closed. Reconnecting... I0219 02:28:14.814841 11302 socket.go:46] Login successful! I0219 02:28:14.814874 11302 socket.go:59] Trying to connect to API Server I0219 02:28:15.488691 11302 socket.go:73] Successfully connected to API Server E0219 03:00:40.799795 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 03:00:40.799795 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 03:00:40.799795 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 03:00:40.799858 11302 socket.go:120] Connection closed. Reconnecting... I0219 03:00:40.919090 11302 socket.go:46] Login successful! I0219 03:00:40.919124 11302 socket.go:59] Trying to connect to API Server I0219 03:00:41.011993 11302 socket.go:73] Successfully connected to API Server I0219 07:25:33.467048 11302 app.go:105] Auto update running every 6 hours I0219 07:25:33.468320 11302 app.go:106] Checking for updates I0219 07:25:39.094158 11302 updatemanager.go:29] Checking bitninja package E0219 07:25:45.899307 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 07:25:45.899307 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 07:25:45.899307 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 07:53:56.042557 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 07:53:56.042557 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 07:53:56.042557 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 07:53:56.042631 11302 socket.go:120] Connection closed. Reconnecting... I0219 07:53:56.226880 11302 socket.go:46] Login successful! I0219 07:53:56.226906 11302 socket.go:59] Trying to connect to API Server I0219 07:53:56.310252 11302 socket.go:73] Successfully connected to API Server E0219 08:00:39.869698 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 08:00:39.869698 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 08:00:39.869698 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 08:00:39.869768 11302 socket.go:120] Connection closed. Reconnecting... I0219 08:00:39.924542 11302 socket.go:46] Login successful! I0219 08:00:39.924580 11302 socket.go:59] Trying to connect to API Server I0219 08:00:40.011127 11302 socket.go:73] Successfully connected to API Server E0219 11:50:13.415770 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 11:50:13.415770 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 11:50:13.415770 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 11:50:13.416442 11302 socket.go:120] Connection closed. Reconnecting... I0219 11:50:21.953201 11302 socket.go:46] Login successful! I0219 11:50:21.953354 11302 socket.go:59] Trying to connect to API Server I0219 11:50:22.220181 11302 socket.go:73] Successfully connected to API Server E0219 11:51:00.605868 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 11:51:00.605868 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 11:51:00.605868 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 11:51:00.605933 11302 socket.go:120] Connection closed. Reconnecting... I0219 11:51:00.683277 11302 socket.go:46] Login successful! I0219 11:51:00.683304 11302 socket.go:59] Trying to connect to API Server I0219 11:51:00.761258 11302 socket.go:73] Successfully connected to API Server E0219 12:07:25.452330 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 12:07:25.452330 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 12:07:25.452330 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 12:07:25.452400 11302 socket.go:120] Connection closed. Reconnecting... I0219 12:07:25.581821 11302 socket.go:46] Login successful! I0219 12:07:25.581878 11302 socket.go:59] Trying to connect to API Server I0219 12:07:25.657751 11302 socket.go:73] Successfully connected to API Server E0219 12:15:30.207866 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 12:15:30.207866 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 12:15:30.207866 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 12:15:30.207944 11302 socket.go:120] Connection closed. Reconnecting... I0219 12:15:30.324292 11302 socket.go:46] Login successful! I0219 12:15:30.324322 11302 socket.go:59] Trying to connect to API Server I0219 12:15:30.410118 11302 socket.go:73] Successfully connected to API Server E0219 12:31:08.705319 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 12:31:08.705319 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 12:31:08.705319 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 12:31:08.705395 11302 socket.go:120] Connection closed. Reconnecting... I0219 12:31:08.755866 11302 socket.go:46] Login successful! I0219 12:31:08.755900 11302 socket.go:59] Trying to connect to API Server I0219 12:31:08.840908 11302 socket.go:73] Successfully connected to API Server I0219 13:25:33.467048 11302 app.go:105] Auto update running every 6 hours I0219 13:25:33.467620 11302 app.go:106] Checking for updates I0219 13:25:39.184824 11302 updatemanager.go:29] Checking bitninja package E0219 13:25:46.022622 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 13:25:46.022622 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 13:25:46.022622 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0219 19:25:33.467102 11302 app.go:105] Auto update running every 6 hours I0219 19:25:33.467919 11302 app.go:106] Checking for updates I0219 19:25:39.387277 11302 updatemanager.go:29] Checking bitninja package E0219 19:25:46.302274 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 19:25:46.302274 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 19:25:46.302274 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0219 20:31:22.334236 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 20:31:22.334236 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 20:31:22.334236 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 20:31:22.334703 11302 socket.go:120] Connection closed. Reconnecting... I0219 20:31:22.418698 11302 socket.go:46] Login successful! I0219 20:31:22.418727 11302 socket.go:59] Trying to connect to API Server I0219 20:31:22.518234 11302 socket.go:73] Successfully connected to API Server E0219 21:53:06.616092 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 21:53:06.616092 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 21:53:06.616092 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 21:53:06.616708 11302 socket.go:120] Connection closed. Reconnecting... I0219 21:53:07.128380 11302 socket.go:46] Login successful! I0219 21:53:07.128412 11302 socket.go:59] Trying to connect to API Server I0219 21:53:07.207201 11302 socket.go:73] Successfully connected to API Server E0219 23:22:12.042051 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 23:22:12.042051 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0219 23:22:12.042051 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0219 23:22:12.042125 11302 socket.go:120] Connection closed. Reconnecting... I0219 23:22:12.282566 11302 socket.go:46] Login successful! I0219 23:22:12.282596 11302 socket.go:59] Trying to connect to API Server I0219 23:22:12.361639 11302 socket.go:73] Successfully connected to API Server I0220 01:25:34.087264 11302 app.go:105] Auto update running every 6 hours I0220 01:25:34.088357 11302 app.go:106] Checking for updates I0220 01:25:39.669780 11302 updatemanager.go:29] Checking bitninja package E0220 01:25:46.485275 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 01:25:46.485275 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 01:25:46.485275 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 03:23:24.608151 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 03:23:24.608151 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 03:23:24.608151 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0220 03:23:24.608795 11302 socket.go:120] Connection closed. Reconnecting... I0220 03:23:24.747941 11302 socket.go:46] Login successful! I0220 03:23:24.747969 11302 socket.go:59] Trying to connect to API Server I0220 03:23:24.823001 11302 socket.go:73] Successfully connected to API Server E0220 06:39:45.709375 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 06:39:45.709375 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 06:39:45.709375 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0220 06:39:45.709705 11302 socket.go:120] Connection closed. Reconnecting... I0220 06:39:45.883935 11302 socket.go:46] Login successful! I0220 06:39:45.883962 11302 socket.go:59] Trying to connect to API Server I0220 06:39:45.965765 11302 socket.go:73] Successfully connected to API Server I0220 07:25:34.086992 11302 app.go:105] Auto update running every 6 hours I0220 07:25:34.087032 11302 app.go:106] Checking for updates I0220 07:25:39.869255 11302 updatemanager.go:29] Checking bitninja package E0220 07:25:46.853113 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 07:25:46.853113 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 07:25:46.853113 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 11:06:15.039698 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 11:06:15.039698 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 11:06:15.039698 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0220 11:06:15.040160 11302 socket.go:120] Connection closed. Reconnecting... I0220 11:06:15.098826 11302 socket.go:46] Login successful! I0220 11:06:15.098856 11302 socket.go:59] Trying to connect to API Server I0220 11:06:15.182640 11302 socket.go:73] Successfully connected to API Server I0220 13:25:34.087314 11302 app.go:105] Auto update running every 6 hours I0220 13:25:34.088154 11302 app.go:106] Checking for updates I0220 13:25:39.642924 11302 updatemanager.go:29] Checking bitninja package E0220 13:25:46.271136 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 13:25:46.271136 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 13:25:46.271136 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 14:13:05.086169 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 14:13:05.086169 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 14:13:05.086169 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0220 14:13:05.086246 11302 socket.go:120] Connection closed. Reconnecting... I0220 14:13:05.230383 11302 socket.go:46] Login successful! I0220 14:13:05.230411 11302 socket.go:59] Trying to connect to API Server I0220 14:13:05.383187 11302 socket.go:73] Successfully connected to API Server E0220 15:00:36.511901 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 15:00:36.511901 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 15:00:36.511901 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0220 15:00:36.511981 11302 socket.go:120] Connection closed. Reconnecting... I0220 15:00:36.577433 11302 socket.go:46] Login successful! I0220 15:00:36.577467 11302 socket.go:59] Trying to connect to API Server I0220 15:00:36.657788 11302 socket.go:73] Successfully connected to API Server I0220 19:25:34.087271 11302 app.go:105] Auto update running every 6 hours I0220 19:25:34.088399 11302 app.go:106] Checking for updates I0220 19:25:39.889697 11302 updatemanager.go:29] Checking bitninja package E0220 19:25:46.615418 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 19:25:46.615418 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 19:25:46.615418 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0220 22:17:52.254668 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 22:17:52.254668 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0220 22:17:52.254668 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0220 22:17:52.256449 11302 socket.go:120] Connection closed. Reconnecting... I0220 22:17:52.538929 11302 socket.go:46] Login successful! I0220 22:17:52.538969 11302 socket.go:59] Trying to connect to API Server I0220 22:17:52.627000 11302 socket.go:73] Successfully connected to API Server I0221 01:25:34.433876 11302 app.go:105] Auto update running every 6 hours I0221 01:25:34.434593 11302 app.go:106] Checking for updates I0221 01:25:40.087869 11302 updatemanager.go:29] Checking bitninja package E0221 01:25:47.054219 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 01:25:47.054219 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 01:25:47.054219 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0221 07:25:34.437199 11302 app.go:105] Auto update running every 6 hours I0221 07:25:34.438750 11302 app.go:106] Checking for updates I0221 07:25:40.039377 11302 updatemanager.go:29] Checking bitninja package E0221 07:25:46.807303 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 07:25:46.807303 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 07:25:46.807303 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 07:29:10.567467 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 07:29:10.567467 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 07:29:10.567467 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0221 07:29:10.569418 11302 socket.go:120] Connection closed. Reconnecting... I0221 07:29:10.760139 11302 socket.go:46] Login successful! I0221 07:29:10.760165 11302 socket.go:59] Trying to connect to API Server I0221 07:29:10.880391 11302 socket.go:73] Successfully connected to API Server I0221 13:25:34.433784 11302 app.go:105] Auto update running every 6 hours I0221 13:25:34.437637 11302 app.go:106] Checking for updates I0221 13:25:40.063054 11302 updatemanager.go:29] Checking bitninja package E0221 13:25:46.621140 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 13:25:46.621140 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 13:25:46.621140 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 14:55:13.263363 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 14:55:13.263363 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 14:55:13.263363 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0221 14:55:13.263931 11302 socket.go:120] Connection closed. Reconnecting... I0221 14:55:13.439707 11302 socket.go:46] Login successful! I0221 14:55:13.439738 11302 socket.go:59] Trying to connect to API Server I0221 14:55:13.865200 11302 socket.go:73] Successfully connected to API Server E0221 15:31:33.039570 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 15:31:33.039570 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 15:31:33.039570 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0221 15:31:33.039645 11302 socket.go:120] Connection closed. Reconnecting... I0221 15:31:33.092480 11302 socket.go:46] Login successful! I0221 15:31:33.092507 11302 socket.go:59] Trying to connect to API Server I0221 15:31:33.179409 11302 socket.go:73] Successfully connected to API Server I0221 19:25:34.433268 11302 app.go:105] Auto update running every 6 hours I0221 19:25:34.434179 11302 app.go:106] Checking for updates I0221 19:25:40.016021 11302 updatemanager.go:29] Checking bitninja package E0221 19:25:46.695541 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 19:25:46.695541 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 19:25:46.695541 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0221 21:26:18.098369 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 21:26:18.098369 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0221 21:26:18.098369 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0221 21:26:18.098832 11302 socket.go:120] Connection closed. Reconnecting... I0221 21:26:18.205616 11302 socket.go:46] Login successful! I0221 21:26:18.205654 11302 socket.go:59] Trying to connect to API Server I0221 21:26:18.287625 11302 socket.go:73] Successfully connected to API Server E0222 00:00:32.892109 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 00:00:32.892109 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 00:00:32.892109 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 00:00:32.893061 11302 socket.go:120] Connection closed. Reconnecting... I0222 00:00:33.035301 11302 socket.go:46] Login successful! I0222 00:00:33.035347 11302 socket.go:59] Trying to connect to API Server I0222 00:00:33.111317 11302 socket.go:73] Successfully connected to API Server I0222 01:25:34.356817 11302 app.go:105] Auto update running every 6 hours I0222 01:25:34.357572 11302 app.go:106] Checking for updates I0222 01:25:39.938964 11302 updatemanager.go:29] Checking bitninja package E0222 01:25:46.563368 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 01:25:46.563368 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 01:25:46.563368 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 06:39:09.398088 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 06:39:09.398088 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 06:39:09.398088 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 06:39:09.399965 11302 socket.go:120] Connection closed. Reconnecting... I0222 06:39:09.551151 11302 socket.go:46] Login successful! I0222 06:39:09.551188 11302 socket.go:59] Trying to connect to API Server I0222 06:39:09.639012 11302 socket.go:73] Successfully connected to API Server E0222 07:00:36.439839 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 07:00:36.439839 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 07:00:36.439839 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 07:00:36.439938 11302 socket.go:120] Connection closed. Reconnecting... I0222 07:00:36.495193 11302 socket.go:46] Login successful! I0222 07:00:36.495226 11302 socket.go:59] Trying to connect to API Server I0222 07:00:36.577678 11302 socket.go:73] Successfully connected to API Server E0222 07:15:36.034265 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 500 E0222 07:15:36.034265 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 500 E0222 07:15:36.034265 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 500 I0222 07:25:34.356350 11302 app.go:105] Auto update running every 6 hours I0222 07:25:34.356735 11302 app.go:106] Checking for updates I0222 07:25:39.931481 11302 updatemanager.go:29] Checking bitninja package E0222 07:25:46.354826 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 07:25:46.354826 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 07:25:46.354826 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 09:00:32.406533 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 09:00:32.406533 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 09:00:32.406533 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 09:00:32.406608 11302 socket.go:120] Connection closed. Reconnecting... I0222 09:00:32.743336 11302 socket.go:46] Login successful! I0222 09:00:32.743369 11302 socket.go:59] Trying to connect to API Server I0222 09:00:32.833317 11302 socket.go:73] Successfully connected to API Server E0222 10:53:09.699033 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 10:53:09.699033 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 10:53:09.699033 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 10:53:09.699140 11302 socket.go:120] Connection closed. Reconnecting... I0222 10:53:09.965259 11302 socket.go:46] Login successful! I0222 10:53:09.965306 11302 socket.go:59] Trying to connect to API Server I0222 10:53:10.050595 11302 socket.go:73] Successfully connected to API Server I0222 13:25:34.356302 11302 app.go:105] Auto update running every 6 hours I0222 13:25:34.357120 11302 app.go:106] Checking for updates I0222 13:25:39.948629 11302 updatemanager.go:29] Checking bitninja package E0222 13:25:46.599041 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 13:25:46.599041 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 13:25:46.599041 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 13:40:15.662674 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 13:40:15.662674 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 13:40:15.662674 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 13:40:15.662785 11302 socket.go:120] Connection closed. Reconnecting... I0222 13:40:15.981755 11302 socket.go:46] Login successful! I0222 13:40:15.981789 11302 socket.go:59] Trying to connect to API Server I0222 13:40:16.283061 11302 socket.go:73] Successfully connected to API Server E0222 16:22:59.527906 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 16:22:59.527906 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 16:22:59.527906 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 16:22:59.528777 11302 socket.go:120] Connection closed. Reconnecting... I0222 16:23:00.225310 11302 socket.go:46] Login successful! I0222 16:23:00.225346 11302 socket.go:59] Trying to connect to API Server I0222 16:23:00.501136 11302 socket.go:73] Successfully connected to API Server E0222 17:31:38.188724 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 17:31:38.188724 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 17:31:38.188724 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 17:31:38.188800 11302 socket.go:120] Connection closed. Reconnecting... I0222 17:31:38.268337 11302 socket.go:46] Login successful! I0222 17:31:38.268364 11302 socket.go:59] Trying to connect to API Server I0222 17:31:38.579519 11302 socket.go:73] Successfully connected to API Server E0222 18:25:51.716548 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 18:25:51.716548 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 18:25:51.716548 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 18:25:51.717099 11302 socket.go:120] Connection closed. Reconnecting... I0222 18:25:51.828031 11302 socket.go:46] Login successful! I0222 18:25:51.828058 11302 socket.go:59] Trying to connect to API Server I0222 18:25:51.915768 11302 socket.go:73] Successfully connected to API Server I0222 19:25:34.355713 11302 app.go:105] Auto update running every 6 hours I0222 19:25:34.355752 11302 app.go:106] Checking for updates I0222 19:25:39.900234 11302 updatemanager.go:29] Checking bitninja package E0222 19:25:46.545682 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 19:25:46.545682 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 19:25:46.545682 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0222 22:45:19.906734 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 22:45:19.906734 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 22:45:19.906734 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 22:45:19.907250 11302 socket.go:120] Connection closed. Reconnecting... I0222 22:45:20.212085 11302 socket.go:46] Login successful! I0222 22:45:20.212115 11302 socket.go:59] Trying to connect to API Server I0222 22:45:20.302245 11302 socket.go:73] Successfully connected to API Server E0222 23:05:02.660801 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 23:05:02.660801 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0222 23:05:02.660801 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0222 23:05:02.660897 11302 socket.go:120] Connection closed. Reconnecting... I0222 23:05:07.771106 11302 socket.go:46] Login successful! I0222 23:05:07.771152 11302 socket.go:59] Trying to connect to API Server I0222 23:05:07.861723 11302 socket.go:73] Successfully connected to API Server I0223 01:25:35.048454 11302 app.go:105] Auto update running every 6 hours I0223 01:25:35.049154 11302 app.go:106] Checking for updates I0223 01:25:41.089703 11302 updatemanager.go:29] Checking bitninja package E0223 01:25:48.741313 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 01:25:48.741313 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 01:25:48.741313 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 04:03:12.379137 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 04:03:12.379137 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 04:03:12.379137 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 04:03:12.379534 11302 socket.go:120] Connection closed. Reconnecting... I0223 04:03:12.672431 11302 socket.go:46] Login successful! I0223 04:03:12.672465 11302 socket.go:59] Trying to connect to API Server I0223 04:03:12.752117 11302 socket.go:73] Successfully connected to API Server E0223 04:18:23.900215 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 04:18:23.900215 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 04:18:23.900215 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 04:18:23.900299 11302 socket.go:120] Connection closed. Reconnecting... I0223 04:18:24.017993 11302 socket.go:46] Login successful! I0223 04:18:24.018029 11302 socket.go:59] Trying to connect to API Server I0223 04:18:25.607564 11302 socket.go:73] Successfully connected to API Server I0223 07:25:35.050128 11302 app.go:105] Auto update running every 6 hours I0223 07:25:35.050699 11302 app.go:106] Checking for updates I0223 07:25:41.216523 11302 updatemanager.go:29] Checking bitninja package E0223 07:25:48.137036 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 07:25:48.137036 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 07:25:48.137036 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 07:35:18.022406 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 07:35:18.022406 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 07:35:18.022406 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 07:35:18.022483 11302 socket.go:120] Connection closed. Reconnecting... I0223 07:35:18.218238 11302 socket.go:46] Login successful! I0223 07:35:18.218264 11302 socket.go:59] Trying to connect to API Server I0223 07:35:18.311964 11302 socket.go:73] Successfully connected to API Server E0223 13:06:26.969977 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 13:06:26.969977 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 13:06:26.969977 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 13:06:26.981759 11302 socket.go:120] Connection closed. Reconnecting... I0223 13:06:27.074744 11302 socket.go:46] Login successful! I0223 13:06:27.074797 11302 socket.go:59] Trying to connect to API Server I0223 13:06:28.860288 11302 socket.go:73] Successfully connected to API Server E0223 13:06:46.343980 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 13:06:46.343980 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 13:06:46.343980 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 13:06:46.344044 11302 socket.go:120] Connection closed. Reconnecting... I0223 13:06:46.451363 11302 socket.go:46] Login successful! I0223 13:06:46.451390 11302 socket.go:59] Trying to connect to API Server I0223 13:06:46.537718 11302 socket.go:73] Successfully connected to API Server I0223 13:25:35.048396 11302 app.go:105] Auto update running every 6 hours I0223 13:25:35.048803 11302 app.go:106] Checking for updates I0223 13:25:40.597367 11302 updatemanager.go:29] Checking bitninja package E0223 13:25:47.332787 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 13:25:47.332787 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 13:25:47.332787 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 17:00:32.399633 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 17:00:32.399633 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 17:00:32.399633 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 17:00:32.400489 11302 socket.go:120] Connection closed. Reconnecting... I0223 17:00:32.660693 11302 socket.go:46] Login successful! I0223 17:00:32.660733 11302 socket.go:59] Trying to connect to API Server I0223 17:00:33.668392 11302 socket.go:73] Successfully connected to API Server E0223 17:42:25.277629 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 17:42:25.277629 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 17:42:25.277629 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 17:42:25.278449 11302 socket.go:120] Connection closed. Reconnecting... I0223 17:42:25.564481 11302 socket.go:46] Login successful! I0223 17:42:25.564521 11302 socket.go:59] Trying to connect to API Server I0223 17:42:25.640771 11302 socket.go:73] Successfully connected to API Server I0223 19:25:35.052935 11302 app.go:105] Auto update running every 6 hours I0223 19:25:35.053549 11302 app.go:106] Checking for updates I0223 19:25:40.661445 11302 updatemanager.go:29] Checking bitninja package E0223 19:25:47.322428 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 19:25:47.322428 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 19:25:47.322428 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0223 23:39:57.160223 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 23:39:57.160223 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0223 23:39:57.160223 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0223 23:39:57.162956 11302 socket.go:120] Connection closed. Reconnecting... I0223 23:39:57.311303 11302 socket.go:46] Login successful! I0223 23:39:57.311334 11302 socket.go:59] Trying to connect to API Server I0223 23:39:57.399551 11302 socket.go:73] Successfully connected to API Server E0224 01:00:35.160339 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 01:00:35.160339 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 01:00:35.160339 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0224 01:00:35.160432 11302 socket.go:120] Connection closed. Reconnecting... I0224 01:00:35.270710 11302 socket.go:46] Login successful! I0224 01:00:35.270743 11302 socket.go:59] Trying to connect to API Server I0224 01:00:35.348729 11302 socket.go:73] Successfully connected to API Server I0224 01:25:34.914334 11302 app.go:105] Auto update running every 6 hours I0224 01:25:34.914846 11302 app.go:106] Checking for updates I0224 01:25:40.495550 11302 updatemanager.go:29] Checking bitninja package E0224 01:25:47.139765 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 01:25:47.139765 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 01:25:47.139765 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 04:58:34.460463 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 04:58:34.460463 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 04:58:34.460463 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0224 04:58:34.460965 11302 socket.go:120] Connection closed. Reconnecting... I0224 04:58:34.832238 11302 socket.go:46] Login successful! I0224 04:58:34.832271 11302 socket.go:59] Trying to connect to API Server E0224 04:59:19.833552 11302 socket.go:62] dial: read tcp 139.162.194.112:39444->5.9.108.156:443: i/o timeout E0224 04:59:19.833552 11302 socket.go:62] dial: read tcp 139.162.194.112:39444->5.9.108.156:443: i/o timeout E0224 04:59:19.833552 11302 socket.go:62] dial: read tcp 139.162.194.112:39444->5.9.108.156:443: i/o timeout I0224 04:59:19.833593 11302 socket.go:64] Retrying connection after 5s... I0224 04:59:24.879742 11302 socket.go:46] Login successful! I0224 04:59:24.879808 11302 socket.go:59] Trying to connect to API Server I0224 04:59:24.956236 11302 socket.go:73] Successfully connected to API Server I0224 07:25:34.917654 11302 app.go:105] Auto update running every 6 hours I0224 07:25:34.919355 11302 app.go:106] Checking for updates I0224 07:25:40.513921 11302 updatemanager.go:29] Checking bitninja package E0224 07:25:47.207942 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 07:25:47.207942 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 07:25:47.207942 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 10:24:19.476576 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 10:24:19.476576 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 10:24:19.476576 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0224 10:24:19.482637 11302 socket.go:120] Connection closed. Reconnecting... I0224 10:24:19.630800 11302 socket.go:46] Login successful! I0224 10:24:19.630831 11302 socket.go:59] Trying to connect to API Server I0224 10:24:19.715874 11302 socket.go:73] Successfully connected to API Server E0224 11:00:33.290174 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 11:00:33.290174 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 11:00:33.290174 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0224 11:00:33.290257 11302 socket.go:120] Connection closed. Reconnecting... I0224 11:00:33.461688 11302 socket.go:46] Login successful! I0224 11:00:33.461726 11302 socket.go:59] Trying to connect to API Server I0224 11:00:33.536513 11302 socket.go:73] Successfully connected to API Server I0224 13:25:34.913068 11302 app.go:105] Auto update running every 6 hours I0224 13:25:34.913849 11302 app.go:106] Checking for updates I0224 13:25:40.767804 11302 updatemanager.go:29] Checking bitninja package E0224 13:25:47.723959 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 13:25:47.723959 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 13:25:47.723959 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 18:41:51.479298 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 18:41:51.479298 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0224 18:41:51.479298 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0224 18:41:51.480832 11302 socket.go:120] Connection closed. Reconnecting... I0224 18:41:51.613888 11302 socket.go:46] Login successful! I0224 18:41:51.613926 11302 socket.go:59] Trying to connect to API Server I0224 18:41:51.697222 11302 socket.go:73] Successfully connected to API Server I0224 19:25:34.913995 11302 app.go:105] Auto update running every 6 hours I0224 19:25:34.914028 11302 app.go:106] Checking for updates I0224 19:25:40.703230 11302 updatemanager.go:29] Checking bitninja package E0224 19:25:47.295690 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 19:25:47.295690 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0224 19:25:47.295690 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 00:29:10.835687 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 00:29:10.835687 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 00:29:10.835687 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 00:29:10.836278 11302 socket.go:120] Connection closed. Reconnecting... I0225 00:29:11.210123 11302 socket.go:46] Login successful! I0225 00:29:11.210155 11302 socket.go:59] Trying to connect to API Server I0225 00:29:11.308571 11302 socket.go:73] Successfully connected to API Server I0225 01:25:35.643223 11302 app.go:105] Auto update running every 6 hours I0225 01:25:35.643872 11302 app.go:106] Checking for updates I0225 01:25:41.162208 11302 updatemanager.go:29] Checking bitninja package E0225 01:25:48.072471 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 01:25:48.072471 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 01:25:48.072471 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 04:37:18.915859 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 04:37:18.915859 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 04:37:18.915859 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 04:37:18.916257 11302 socket.go:120] Connection closed. Reconnecting... I0225 04:37:19.080562 11302 socket.go:46] Login successful! I0225 04:37:19.080592 11302 socket.go:59] Trying to connect to API Server I0225 04:37:19.165289 11302 socket.go:73] Successfully connected to API Server E0225 05:00:35.618382 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 05:00:35.618382 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 05:00:35.618382 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 05:00:35.618468 11302 socket.go:120] Connection closed. Reconnecting... I0225 05:00:35.773473 11302 socket.go:46] Login successful! I0225 05:00:35.773506 11302 socket.go:59] Trying to connect to API Server I0225 05:00:35.855609 11302 socket.go:73] Successfully connected to API Server E0225 07:00:41.716514 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 07:00:41.716514 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 07:00:41.716514 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 07:00:41.716886 11302 socket.go:120] Connection closed. Reconnecting... I0225 07:00:41.818627 11302 socket.go:46] Login successful! I0225 07:00:41.818657 11302 socket.go:59] Trying to connect to API Server I0225 07:00:41.916475 11302 socket.go:73] Successfully connected to API Server I0225 07:25:35.643951 11302 app.go:105] Auto update running every 6 hours I0225 07:25:35.643997 11302 app.go:106] Checking for updates I0225 07:25:41.256666 11302 updatemanager.go:29] Checking bitninja package E0225 07:25:48.103736 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 07:25:48.103736 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 07:25:48.103736 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k I0225 13:25:35.641535 11302 app.go:105] Auto update running every 6 hours I0225 13:25:35.642122 11302 app.go:106] Checking for updates I0225 13:25:41.159601 11302 updatemanager.go:29] Checking bitninja package E0225 13:25:47.756556 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 13:25:47.756556 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 13:25:47.756556 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 14:44:05.840290 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 14:44:05.840290 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 14:44:05.840290 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 14:44:05.842235 11302 socket.go:120] Connection closed. Reconnecting... I0225 14:44:05.984006 11302 socket.go:46] Login successful! I0225 14:44:05.984035 11302 socket.go:59] Trying to connect to API Server I0225 14:44:06.078494 11302 socket.go:73] Successfully connected to API Server E0225 18:15:33.456986 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 18:15:33.456986 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 18:15:33.456986 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 18:15:33.457923 11302 socket.go:120] Connection closed. Reconnecting... I0225 18:15:33.573615 11302 socket.go:46] Login successful! I0225 18:15:33.573647 11302 socket.go:59] Trying to connect to API Server I0225 18:15:33.662250 11302 socket.go:73] Successfully connected to API Server I0225 19:25:35.643291 11302 app.go:105] Auto update running every 6 hours I0225 19:25:35.643639 11302 app.go:106] Checking for updates I0225 19:25:41.334388 11302 updatemanager.go:29] Checking bitninja package E0225 19:25:48.048809 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 19:25:48.048809 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 19:25:48.048809 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0225 21:00:50.843997 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0225 21:00:50.843997 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0225 21:00:50.843997 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0225 21:01:03.685526 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 21:01:03.685526 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0225 21:01:03.685526 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0225 21:01:03.685594 11302 socket.go:120] Connection closed. Reconnecting... E0225 21:01:18.708961 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:01:18.708961 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:01:18.708961 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:02:33.732532 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:02:33.732532 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:02:33.732532 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:04:39.782226 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:04:39.782226 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:04:39.782226 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:06:40.822029 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:06:40.822029 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:06:40.822029 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:06:45.665801 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0225 21:06:45.665801 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0225 21:06:45.665801 11302 app.go:123] Failed to send update channel to the API: received unexpected status code: 504 E0225 21:07:55.846123 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:07:55.846123 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:07:55.846123 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:09:55.869645 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:09:55.869645 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:09:55.869645 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [504]. Response was: [<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html> ]. Retrying in 60 seconds... E0225 21:11:45.896843 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [500]. Response was: [{"statusCode":500,"message":"Internal server error"}]. Retrying in 60 seconds... E0225 21:11:45.896843 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [500]. Response was: [{"statusCode":500,"message":"Internal server error"}]. Retrying in 60 seconds... E0225 21:11:45.896843 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [500]. Response was: [{"statusCode":500,"message":"Internal server error"}]. Retrying in 60 seconds... E0225 21:12:55.938816 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0225 21:12:55.938816 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0225 21:12:55.938816 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... I0225 21:13:56.000323 11302 socket.go:46] Login successful! I0225 21:13:56.000365 11302 socket.go:59] Trying to connect to API Server I0225 21:13:56.134948 11302 socket.go:73] Successfully connected to API Server I0226 01:25:35.970745 11302 app.go:105] Auto update running every 6 hours I0226 01:25:35.971093 11302 app.go:106] Checking for updates I0226 01:25:41.578939 11302 updatemanager.go:29] Checking bitninja package E0226 01:25:48.278735 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 01:25:48.278735 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 01:25:48.278735 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 04:50:18.143536 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 04:50:18.143536 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 04:50:18.143536 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 04:50:18.146394 11302 socket.go:120] Connection closed. Reconnecting... I0226 04:50:18.342642 11302 socket.go:46] Login successful! I0226 04:50:18.342673 11302 socket.go:59] Trying to connect to API Server I0226 04:50:18.588595 11302 socket.go:73] Successfully connected to API Server E0226 05:42:45.724523 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 05:42:45.724523 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 05:42:45.724523 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 05:42:45.724876 11302 socket.go:120] Connection closed. Reconnecting... I0226 05:42:45.877318 11302 socket.go:46] Login successful! I0226 05:42:45.877354 11302 socket.go:59] Trying to connect to API Server I0226 05:42:45.970759 11302 socket.go:73] Successfully connected to API Server E0226 06:00:38.887004 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 06:00:38.887004 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 06:00:38.887004 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 06:00:38.887093 11302 socket.go:120] Connection closed. Reconnecting... I0226 06:00:38.919402 11302 socket.go:46] Login successful! I0226 06:00:38.919429 11302 socket.go:59] Trying to connect to API Server I0226 06:00:38.997229 11302 socket.go:73] Successfully connected to API Server I0226 07:25:35.971538 11302 app.go:105] Auto update running every 6 hours I0226 07:25:35.971580 11302 app.go:106] Checking for updates I0226 07:25:41.584597 11302 updatemanager.go:29] Checking bitninja package E0226 07:25:48.277451 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 07:25:48.277451 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 07:25:48.277451 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 12:56:23.191390 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 12:56:23.191390 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 12:56:23.191390 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 12:56:23.192248 11302 socket.go:120] Connection closed. Reconnecting... I0226 12:56:23.308344 11302 socket.go:46] Login successful! I0226 12:56:23.308381 11302 socket.go:59] Trying to connect to API Server I0226 12:56:23.381112 11302 socket.go:73] Successfully connected to API Server I0226 13:25:35.969279 11302 app.go:105] Auto update running every 6 hours I0226 13:25:35.969319 11302 app.go:106] Checking for updates I0226 13:25:41.917821 11302 updatemanager.go:29] Checking bitninja package E0226 13:25:49.164848 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 13:25:49.164848 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 13:25:49.164848 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 15:15:52.476748 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 15:15:52.476748 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 15:15:52.476748 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 15:15:52.476843 11302 socket.go:120] Connection closed. Reconnecting... I0226 15:15:52.549059 11302 socket.go:46] Login successful! I0226 15:15:52.549106 11302 socket.go:59] Trying to connect to API Server I0226 15:15:52.625237 11302 socket.go:73] Successfully connected to API Server E0226 17:45:03.227488 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 17:45:03.227488 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 17:45:03.227488 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 17:45:03.227790 11302 socket.go:120] Connection closed. Reconnecting... E0226 17:45:13.401482 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0226 17:45:13.401482 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... E0226 17:45:13.401482 11302 socket.go:144] Login failed: Request to [https://api.bitninja.io/v2/authentication/login/license] failed with status code [401]. Response was: [{"statusCode":401,"message":"Couldn't log in"}]. Retrying in 60 seconds... I0226 17:46:13.479680 11302 socket.go:46] Login successful! I0226 17:46:13.479745 11302 socket.go:59] Trying to connect to API Server I0226 17:46:13.575917 11302 socket.go:73] Successfully connected to API Server I0226 19:25:35.969294 11302 app.go:105] Auto update running every 6 hours I0226 19:25:35.969732 11302 app.go:106] Checking for updates I0226 19:25:41.489140 11302 updatemanager.go:29] Checking bitninja package E0226 19:25:47.936618 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 19:25:47.936618 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 19:25:47.936618 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0226 23:11:18.400231 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 23:11:18.400231 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0226 23:11:18.400231 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0226 23:11:18.400553 11302 socket.go:120] Connection closed. Reconnecting... I0226 23:11:18.551397 11302 socket.go:46] Login successful! I0226 23:11:18.551431 11302 socket.go:59] Trying to connect to API Server I0226 23:11:18.715410 11302 socket.go:73] Successfully connected to API Server E0227 00:11:57.023422 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 00:11:57.023422 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 00:11:57.023422 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 00:11:57.023493 11302 socket.go:120] Connection closed. Reconnecting... I0227 00:11:57.213901 11302 socket.go:46] Login successful! I0227 00:11:57.213942 11302 socket.go:59] Trying to connect to API Server I0227 00:11:57.289678 11302 socket.go:73] Successfully connected to API Server I0227 01:25:36.277720 11302 app.go:105] Auto update running every 6 hours I0227 01:25:36.278106 11302 app.go:106] Checking for updates I0227 01:25:41.808613 11302 updatemanager.go:29] Checking bitninja package E0227 01:25:48.386804 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 01:25:48.386804 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 01:25:48.386804 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 06:30:20.517457 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 06:30:20.517457 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 06:30:20.517457 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 06:30:20.522432 11302 socket.go:120] Connection closed. Reconnecting... I0227 06:30:20.876470 11302 socket.go:46] Login successful! I0227 06:30:20.876500 11302 socket.go:59] Trying to connect to API Server I0227 06:30:21.436825 11302 socket.go:73] Successfully connected to API Server I0227 07:25:36.278928 11302 app.go:105] Auto update running every 6 hours I0227 07:25:36.278971 11302 app.go:106] Checking for updates I0227 07:25:41.832175 11302 updatemanager.go:29] Checking bitninja package E0227 07:25:48.376196 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 07:25:48.376196 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 07:25:48.376196 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 08:02:50.594733 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 08:02:50.594733 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 08:02:50.594733 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 08:02:50.594812 11302 socket.go:120] Connection closed. Reconnecting... I0227 08:02:50.991476 11302 socket.go:46] Login successful! I0227 08:02:50.991509 11302 socket.go:59] Trying to connect to API Server I0227 08:02:51.076854 11302 socket.go:73] Successfully connected to API Server E0227 10:58:12.655706 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 10:58:12.655706 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 10:58:12.655706 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 10:58:12.656094 11302 socket.go:120] Connection closed. Reconnecting... I0227 10:58:12.810255 11302 socket.go:46] Login successful! I0227 10:58:12.810287 11302 socket.go:59] Trying to connect to API Server I0227 10:58:12.920335 11302 socket.go:73] Successfully connected to API Server I0227 13:25:36.277920 11302 app.go:105] Auto update running every 6 hours I0227 13:25:36.278421 11302 app.go:106] Checking for updates I0227 13:25:42.107690 11302 updatemanager.go:29] Checking bitninja package E0227 13:25:49.041486 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 13:25:49.041486 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 13:25:49.041486 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 14:52:28.892810 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 14:52:28.892810 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 14:52:28.892810 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 14:52:28.893233 11302 socket.go:120] Connection closed. Reconnecting... I0227 14:52:29.035815 11302 socket.go:46] Login successful! I0227 14:52:29.035848 11302 socket.go:59] Trying to connect to API Server I0227 14:52:29.119923 11302 socket.go:73] Successfully connected to API Server E0227 18:32:57.028593 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 18:32:57.028593 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 18:32:57.028593 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 18:32:57.029387 11302 socket.go:120] Connection closed. Reconnecting... I0227 18:32:57.267652 11302 socket.go:46] Login successful! I0227 18:32:57.267682 11302 socket.go:59] Trying to connect to API Server I0227 18:32:57.339946 11302 socket.go:73] Successfully connected to API Server E0227 19:00:32.872154 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 19:00:32.872154 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 19:00:32.872154 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 19:00:32.872232 11302 socket.go:120] Connection closed. Reconnecting... I0227 19:00:32.990104 11302 socket.go:46] Login successful! I0227 19:00:32.990137 11302 socket.go:59] Trying to connect to API Server I0227 19:00:33.068106 11302 socket.go:73] Successfully connected to API Server I0227 19:25:36.278429 11302 app.go:105] Auto update running every 6 hours I0227 19:25:36.281104 11302 app.go:106] Checking for updates I0227 19:25:42.103811 11302 updatemanager.go:29] Checking bitninja package E0227 19:25:49.007822 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 19:25:49.007822 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 19:25:49.007822 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0227 20:01:08.337611 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 20:01:08.337611 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 20:01:08.337611 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 20:01:08.337684 11302 socket.go:120] Connection closed. Reconnecting... I0227 20:01:08.414138 11302 socket.go:46] Login successful! I0227 20:01:08.414172 11302 socket.go:59] Trying to connect to API Server I0227 20:01:08.509428 11302 socket.go:73] Successfully connected to API Server E0227 23:12:26.891347 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 23:12:26.891347 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0227 23:12:26.891347 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0227 23:12:26.891919 11302 socket.go:120] Connection closed. Reconnecting... I0227 23:12:27.111132 11302 socket.go:46] Login successful! I0227 23:12:27.111163 11302 socket.go:59] Trying to connect to API Server I0227 23:12:27.196536 11302 socket.go:73] Successfully connected to API Server E0228 01:22:21.912610 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 01:22:21.912610 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 01:22:21.912610 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0228 01:22:21.912995 11302 socket.go:120] Connection closed. Reconnecting... I0228 01:22:22.066468 11302 socket.go:46] Login successful! I0228 01:22:22.066499 11302 socket.go:59] Trying to connect to API Server I0228 01:22:22.148087 11302 socket.go:73] Successfully connected to API Server I0228 01:25:37.179392 11302 app.go:105] Auto update running every 6 hours I0228 01:25:37.179427 11302 app.go:106] Checking for updates I0228 01:25:42.822978 11302 updatemanager.go:29] Checking bitninja package E0228 01:25:50.283920 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 01:25:50.283920 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 01:25:50.283920 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 06:00:37.219134 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 06:00:37.219134 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 06:00:37.219134 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0228 06:00:37.219986 11302 socket.go:120] Connection closed. Reconnecting... I0228 06:00:37.348094 11302 socket.go:46] Login successful! I0228 06:00:37.348130 11302 socket.go:59] Trying to connect to API Server I0228 06:00:37.430667 11302 socket.go:73] Successfully connected to API Server I0228 07:25:37.179939 11302 app.go:105] Auto update running every 6 hours I0228 07:25:37.179977 11302 app.go:106] Checking for updates I0228 07:25:42.678175 11302 updatemanager.go:29] Checking bitninja package E0228 07:25:49.002689 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 07:25:49.002689 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 07:25:49.002689 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 13:19:13.192694 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 13:19:13.192694 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 13:19:13.192694 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0228 13:19:13.193206 11302 socket.go:120] Connection closed. Reconnecting... I0228 13:19:13.700633 11302 socket.go:46] Login successful! I0228 13:19:13.700662 11302 socket.go:59] Trying to connect to API Server I0228 13:19:14.105967 11302 socket.go:73] Successfully connected to API Server I0228 13:25:37.179072 11302 app.go:105] Auto update running every 6 hours I0228 13:25:37.179114 11302 app.go:106] Checking for updates I0228 13:25:42.780137 11302 updatemanager.go:29] Checking bitninja package E0228 13:25:49.632233 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 13:25:49.632233 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 13:25:49.632233 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 17:22:41.466712 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 17:22:41.466712 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0228 17:22:41.466712 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0228 17:22:41.467264 11302 socket.go:120] Connection closed. Reconnecting... I0228 17:22:41.589085 11302 socket.go:46] Login successful! I0228 17:22:41.589116 11302 socket.go:59] Trying to connect to API Server I0228 17:22:41.676110 11302 socket.go:73] Successfully connected to API Server I0228 19:25:37.179651 11302 app.go:105] Auto update running every 6 hours I0228 19:25:37.180095 11302 app.go:106] Checking for updates I0228 19:25:42.821295 11302 updatemanager.go:29] Checking bitninja package E0228 19:25:49.664680 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 19:25:49.664680 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0228 19:25:49.664680 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 00:00:32.413432 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 00:00:32.413432 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 00:00:32.413432 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 00:00:32.413941 11302 socket.go:120] Connection closed. Reconnecting... I0301 00:00:32.548612 11302 socket.go:46] Login successful! I0301 00:00:32.548648 11302 socket.go:59] Trying to connect to API Server I0301 00:00:32.657956 11302 socket.go:73] Successfully connected to API Server E0301 01:00:32.289974 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 01:00:32.289974 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 01:00:32.289974 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 01:00:32.290049 11302 socket.go:120] Connection closed. Reconnecting... I0301 01:00:32.451404 11302 socket.go:46] Login successful! I0301 01:00:32.451437 11302 socket.go:59] Trying to connect to API Server I0301 01:00:32.767808 11302 socket.go:73] Successfully connected to API Server I0301 01:25:37.279720 11302 app.go:105] Auto update running every 6 hours I0301 01:25:37.279952 11302 app.go:106] Checking for updates I0301 01:25:42.823931 11302 updatemanager.go:29] Checking bitninja package E0301 01:25:49.409691 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 01:25:49.409691 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 01:25:49.409691 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 02:39:32.965214 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 02:39:32.965214 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 02:39:32.965214 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 02:39:32.965775 11302 socket.go:120] Connection closed. Reconnecting... I0301 02:39:33.178819 11302 socket.go:46] Login successful! I0301 02:39:33.178850 11302 socket.go:59] Trying to connect to API Server I0301 02:39:33.266771 11302 socket.go:73] Successfully connected to API Server E0301 05:00:32.625691 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 05:00:32.625691 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 05:00:32.625691 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 05:00:32.626218 11302 socket.go:120] Connection closed. Reconnecting... I0301 05:00:32.772013 11302 socket.go:46] Login successful! I0301 05:00:32.772044 11302 socket.go:59] Trying to connect to API Server I0301 05:00:32.848093 11302 socket.go:73] Successfully connected to API Server E0301 06:00:32.592241 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 06:00:32.592241 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 06:00:32.592241 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 06:00:32.592325 11302 socket.go:120] Connection closed. Reconnecting... I0301 06:00:32.795031 11302 socket.go:46] Login successful! I0301 06:00:32.795061 11302 socket.go:59] Trying to connect to API Server I0301 06:00:32.911701 11302 socket.go:73] Successfully connected to API Server I0301 07:25:37.278729 11302 app.go:105] Auto update running every 6 hours I0301 07:25:37.279051 11302 app.go:106] Checking for updates I0301 07:25:42.852759 11302 updatemanager.go:29] Checking bitninja package E0301 07:25:49.541106 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 07:25:49.541106 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 07:25:49.541106 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 12:00:59.141146 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 12:00:59.141146 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 12:00:59.141146 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 12:00:59.141576 11302 socket.go:120] Connection closed. Reconnecting... I0301 12:00:59.235730 11302 socket.go:46] Login successful! I0301 12:00:59.235760 11302 socket.go:59] Trying to connect to API Server I0301 12:00:59.329282 11302 socket.go:73] Successfully connected to API Server E0301 12:11:10.286550 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 12:11:10.286550 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF E0301 12:11:10.286550 11302 socket.go:86] read: websocket: close 1006 (abnormal closure): unexpected EOF I0301 12:11:10.286627 11302 socket.go:120] Connection closed. Reconnecting... I0301 12:11:10.331860 11302 socket.go:46] Login successful! I0301 12:11:10.331894 11302 socket.go:59] Trying to connect to API Server I0301 12:11:10.412881 11302 socket.go:73] Successfully connected to API Server I0301 13:25:37.279483 11302 app.go:105] Auto update running every 6 hours I0301 13:25:37.279854 11302 app.go:106] Checking for updates I0301 13:25:43.151482 11302 updatemanager.go:29] Checking bitninja package E0301 13:25:49.943293 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 13:25:49.943293 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k E0301 13:25:49.943293 11302 app.go:109] failed to install bitninja: failed to install package: exit status 1, output: Loaded plugins: universal-hooks 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 Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k
[+]
..
[-] reliable-auto-update.log
[edit]
[-] reliable-auto-update-2026-02-07T19-25-40.349.log.gz
[edit]