yesterday I did the updates on a few servers, everything went through and looked good but today I get something like this:
[root@infra01 ~]# yum clean all && rm -rf /var/cache/yum && yum -y update Loaded plugins: changelog, fastestmirror, nethserver_events Cleaning repos: base centos-sclo-rh centos-sclo-sclo epel extras nethforge nethserver-base nethserver-updates updates Cleaning up everything Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos Cleaning up list of fastest mirrors Loaded plugins: changelog, fastestmirror, nethserver_events Determining fastest mirrors epel/x86_64/metalink | 14 kB 00:00:00 * base: ftp.tugraz.at * epel: mirror.miletic.net * extras: ftp.tugraz.at * nethforge: mrmarkuz.goip.de * nethserver-base: mrmarkuz.goip.de * nethserver-updates: mrmarkuz.goip.de * updates: ftp.tugraz.at base | 3.6 kB 00:00:00 centos-sclo-rh | 3.0 kB 00:00:00 centos-sclo-sclo | 2.9 kB 00:00:00 epel | 4.7 kB 00:00:00 extras | 3.4 kB 00:00:00 nethforge | 4.1 kB 00:00:00 nethserver-base | 2.9 kB 00:00:00 nethserver-updates | 4.1 kB 00:00:00 updates | 3.4 kB 00:00:00 (1/14): base/7/x86_64/group_gz | 166 kB 00:00:00 (2/14): epel/x86_64/group_gz | 84 kB 00:00:00 epel/x86_64/updateinfo FAILED ] 0.0 B/s | 669 kB --:--:-- ETA http://mirror.23media.de/epel/7/x86_64/repodata/3ada5bcbccaa9772074a773b15bd01dd48e753a184ebecfed590de6c389ada03-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. (3/14): centos-sclo-sclo/x86_64/primary_db | 202 kB 00:00:00 (4/14): extras/7/x86_64/primary_db | 104 kB 00:00:00 (5/14): nethforge/7/x86_64/group_gz | 1.7 kB 00:00:00 (6/14): nethserver-base/7/x86_64/primary_db | 241 kB 00:00:00 (7/14): nethserver-updates/7/x86_64/group_gz | 20 kB 00:00:00 (8/14): epel/x86_64/primary_db | 1.6 MB 00:00:01 (9/14): nethserver-updates/7/x86_64/primary_db | 382 kB 00:00:00 (10/14): base/7/x86_64/primary_db | 5.9 MB 00:00:02 (11/14): nethforge/7/x86_64/primary_db | 32 kB 00:00:01 (12/14): updates/7/x86_64/primary_db | 1.0 MB 00:00:01 (13/14): epel/x86_64/updateinfo | 921 kB 00:00:00 (14/14): centos-sclo-rh/x86_64/primary_db | 3.2 MB 00:00:03 One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true file is encrypted or is not a database
How can I be sure that everything will be ok with the server?
Is there a command to make a self-test?