Solved One of the configured repositories failed (Unknown)
-
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
Does anyone have an idea on how to work this problem?
Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: reflector.westga.edu * epel: ftp.cse.buffalo.edu * extras: mirror.atlanticmetro.net * remi-php71: repo1.ash.innoscale.net * remi-safe: repo1.ash.innoscale.net * updates: ftpmirror.your.org One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). 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 databaseDid you try any of the things it said to try to fix it?
I have no idea which repo is the culprit, so no I'm not going to just start disabling every repo one by one to see which is broken.
It tells you.
-
@Obsolesce said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
Does anyone have an idea on how to work this problem?
Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: reflector.westga.edu * epel: ftp.cse.buffalo.edu * extras: mirror.atlanticmetro.net * remi-php71: repo1.ash.innoscale.net * remi-safe: repo1.ash.innoscale.net * updates: ftpmirror.your.org One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). 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 databaseDid you try any of the things it said to try to fix it?
I have no idea which repo is the culprit, so no I'm not going to just start disabling every repo one by one to see which is broken.
It tells you.
No it specifically says unknown, the top of the list are the base repos, of which are all required for the system to operate. Which disabling those would be paramount to not receiving updates ever again.
-
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
Does anyone have an idea on how to work this problem?
Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: reflector.westga.edu * epel: ftp.cse.buffalo.edu * extras: mirror.atlanticmetro.net * remi-php71: repo1.ash.innoscale.net * remi-safe: repo1.ash.innoscale.net * updates: ftpmirror.your.org One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). 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 databaseDid you try any of the things it said to try to fix it?
I have no idea which repo is the culprit, so no I'm not going to just start disabling every repo one by one to see which is broken.
It tells you.
No it specifically says unknown, the top of the list are the base repos, of which are all required for the system to operate. Which disabling those would be paramount to not receiving updates ever again.
But you cannot update now either. So you can disable one, try it, put it back if not the one.
-
@Obsolesce said in One of the configured repositories failed (Unknown):
But you cannot update now either. So you can disable one, try it, put it back if not the one.
This is true, but if I can't update currently, then the issue is with an upstream repo. It's not critical to update today for me. I was just checking to see if anyone else has seen this and worked with the issue.
-
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
But you cannot update now either. So you can disable one, try it, put it back if not the one.
This is true, but if I can't update currently, then the issue is with an upstream repo. It's not critical to update today for me. I was just checking to see if anyone else has seen this and worked with the issue.
-
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
But you cannot update now either. So you can disable one, try it, put it back if not the one.
This is true, but if I can't update currently, then the issue is with an upstream repo. It's not critical to update today for me. I was just checking to see if anyone else has seen this and worked with the issue.
Comment out each repo one by one and try update. That's about all you can do
-
Install yum-cron, set it up to email you when updates are installed and stop worrying about updates.
-
@marcinozga said in One of the configured repositories failed (Unknown):
Install yum-cron, set it up to email you when updates are installed and stop worrying about updates.
That doesn't fix a broken repo, you will still get errors
-
@IRJ said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
But you cannot update now either. So you can disable one, try it, put it back if not the one.
This is true, but if I can't update currently, then the issue is with an upstream repo. It's not critical to update today for me. I was just checking to see if anyone else has seen this and worked with the issue.
Comment out each repo one by one and try update. That's about all you can do
Commented each repo one by one in
/etc/yum.repos.d/epel.repoand tried again with no change.Since there are all of these
CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo epel-testing.repo ius.repo remi-glpi91.repo remi-glpi93.repo remi-modular.repo remi-php70.repo remi-php72.repo remi.repo CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo epel.repo ius-archive.repo ius-testing.repo remi-glpi92.repo remi-glpi94.repo remi-php54.repo remi-php71.repo remi-php73.repo remi-safe.repoI'm just gonna wait till later on and see if this is resolved upstream.
-
@DustinB3403 said in One of the configured repositories failed (Unknown):
@IRJ said in One of the configured repositories failed (Unknown):
@DustinB3403 said in One of the configured repositories failed (Unknown):
@Obsolesce said in One of the configured repositories failed (Unknown):
But you cannot update now either. So you can disable one, try it, put it back if not the one.
This is true, but if I can't update currently, then the issue is with an upstream repo. It's not critical to update today for me. I was just checking to see if anyone else has seen this and worked with the issue.
Comment out each repo one by one and try update. That's about all you can do
Commented each repo one by one in
/etc/yum.repos.d/epel.repoand tried again with no change.Since there are all of these
CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo epel-testing.repo ius.repo remi-glpi91.repo remi-glpi93.repo remi-modular.repo remi-php70.repo remi-php72.repo remi.repo CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo epel.repo ius-archive.repo ius-testing.repo remi-glpi92.repo remi-glpi94.repo remi-php54.repo remi-php71.repo remi-php73.repo remi-safe.repoI'm just gonna wait till later on and see if this is resolved upstream.
There can be more than one file in that directory. Make sure there are no other files
-
@IRJ In
/etc/yum.repos.dthere are all of these.CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo epel-testing.repo ius.repo remi-glpi91.repo remi-glpi93.repo remi-modular.repo remi-php70.repo remi-php72.repo remi.repo CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo epel.repo ius-archive.repo ius-testing.repo remi-glpi92.repo remi-glpi94.repo remi-php54.repo remi-php71.repo remi-php73.repo remi-safe.repoAnd I'm not interesting with going through and commenting each and every one of these, one by one to find out which is broken.
-
What does this return ?
yum repolist -
yum clean all && rm -rf /var/cache/yum/* && yum updateSee if that helps.
-
yum repolist Loaded plugins: fastestmirror Determining fastest mirrors epel/x86_64/metalink | 17 kB 00:00:00 * base: mirror.atlanticmetro.net * epel: reflector.westga.edu * extras: mirror.atlanticmetro.net * remi-php71: repo1.ash.innoscale.net * remi-safe: repo1.ash.innoscale.net * updates: centos.mirror.constant.com base | 3.6 kB 00:00:00 extras | 3.4 kB 00:00:00 ius | 1.3 kB 00:00:00 remi-php71 | 3.0 kB 00:00:00 remi-safe | 3.0 kB 00:00:00 updates | 3.4 kB 00:00:00 updates/7/x86_64/primary_db | 7.4 MB 00:00:00 ius 829/829 repo id repo name status base/7/x86_64 CentOS-7 - Base 10,019 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 13,343 extras/7/x86_64 CentOS-7 - Extras 435 ius/x86_64 IUS for Enterprise Linux 7 - x86_64 829 remi-php71 Remi's PHP 7.1 RPM repository for Enterprise Linux 7 - x86_64 425 remi-safe Safe Remi's RPM repository for Enterprise Linux 7 - x86_64 3,553 updates/7/x86_64 CentOS-7 - Updates 2,500 repolist: 31,104 -
@marcinozga Getting this
sudo yum clean all && rm -rf /var/cache/yum/* && yum update Loaded plugins: fastestmirror Cleaning repos: base epel extras ius remi-php71 remi-safe updates Cleaning up list of fastest mirrors rm: cannot remove ‘/var/cache/yum/x86_64/7/base/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/base/packages’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/extras/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/extras/packages’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/updates/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/updates/packages’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/timedhosts’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/epel/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/epel/packages’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/.gpgkeyschecked.yum’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/ius/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/ius/packages’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-safe/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-safe/packages’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-php71/gen’: Permission denied rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-php71/packages’: Permission denied -
I also think you may be looking at the wrong file.
In Ubuntu it is located here
/etc/apt/sources.listYou can also add sources by file here
/etc/apt/sources.list.d/ -
@DustinB3403 said in One of the configured repositories failed (Unknown):
@marcinozga Getting this
sudo yum clean all && rm -rf /var/cache/yum/* && yum update
Loaded plugins: fastestmirror
Cleaning repos: base epel extras ius remi-php71 remi-safe updates
Cleaning up list of fastest mirrors
rm: cannot remove ‘/var/cache/yum/x86_64/7/base/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/base/packages’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/extras/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/extras/packages’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/updates/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/updates/packages’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/timedhosts’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/epel/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/epel/packages’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/.gpgkeyschecked.yum’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/ius/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/ius/packages’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-safe/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-safe/packages’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-php71/gen’: Permission denied
rm: cannot remove ‘/var/cache/yum/x86_64/7/remi-php71/packages’: Permission deniedNeed sudo for all 3 commands
-
@IRJ Rebooting resolved it, at least now updates are able to be run.
-
@DustinB3403 said in One of the configured repositories failed (Unknown):
@IRJ Rebooting resolved it, at least now updates are able to be run.
That doesnt make much sense to me. Did you try to update after cleaning cache?
-
@IRJ He couldn't clean it as visible in that screen. There was probably a zombie yum process somewhere locking cache files.
