Yum failing check-updateError during yum updateyum update failing each timeCan't run yum updateCentOS 7 update using “yum update” does not workyum repository install issue with cent os 7How can i fix “ ”Failed to connect to 2001:19f0:0:2a:225:90ff:fe08:f840: Network is unreachable“”yum remove silently failingcannot offline install vnc server on CentOS 7YUM ERROR: Failed to retrieve group file for repository: rhel-x86_64-server-7How to resolve Transaction check error while installing xrdp?
Fixing obscure 8080 emulator bug?
Why would future John risk sending back a T-800 to save his younger self?
System.StringException: Unexpected end of expression
Should an arbiter claim draw at a K+R vs K+R endgame?
Is open-sourcing the code of a webapp not recommended?
Soft question: Examples where lack of mathematical rigour cause security breaches?
Impedance ratio vs. SWR
Medieval flying castle propulsion
Character descriptions
SQL counting distinct over partition
How to forge a multi-part weapon?
bash script: "*.jpg" expansion not working as expected inside $(...), for picking a random file
Were Alexander the Great and Hephaestion lovers?
Winning Strategy for the Magician and his Apprentice
Is counterpoint still used today?
SOQL Not Recognizing Field?
Preventing employees from either switching to competitors or opening their own business
How to handle self harm scars on the arm in work environment?
Passing multiple files through stdin (over ssh)
Why is the tail group of virtually every airplane swept instead of straight?
Cycle through MeshStyle directives in ListLinePlot
Déjà vu, again?
Project Euler #7 10001st prime in C++
Compiling C files on Ubuntu and using the executable on Windows
Yum failing check-update
Error during yum updateyum update failing each timeCan't run yum updateCentOS 7 update using “yum update” does not workyum repository install issue with cent os 7How can i fix “ ”Failed to connect to 2001:19f0:0:2a:225:90ff:fe08:f840: Network is unreachable“”yum remove silently failingcannot offline install vnc server on CentOS 7YUM ERROR: Failed to retrieve group file for repository: rhel-x86_64-server-7How to resolve Transaction check error while installing xrdp?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Starting this morning I'm getting errors checking for updates to packages with yum on Centos 7.6. When I run:
$ sudo yum clean all && sudo yum check-update
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Cleaning repos: base epel extras google-cloud-compute google-cloud-sdk updates
Cleaning up list of fastest mirrors
Other repos take up 1.5 M of disk space (use --verbose for details)
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Determining fastest mirrors
epel/x86_64/metalink | 15 kB 00:00:00
* base: mirror.cogentco.com
* epel: mirror.steadfastnet.com
* extras: mirror.cogentco.com
* updates: mirror.cogentco.com
base | 3.6 kB 00:00:00
epel | 4.9 kB 00:00:00
extras | 3.4 kB 00:00:00
google-cloud-compute/signature | 454 B 00:00:00
google-cloud-compute/signature | 1.8 kB 00:00:00 !!!
google-cloud-sdk/signature | 454 B 00:00:00
google-cloud-sdk/signature | 1.4 kB 00:00:00 !!!
updates | 3.4 kB 00:00:00
(1/9): base/7/x86_64/group_gz | 166 kB 00:00:00
(2/9): extras/7/x86_64/primary_db | 200 kB 00:00:00
(3/9): epel/x86_64/group_gz | 88 kB 00:00:00
(4/9): base/7/x86_64/primary_db | 6.0 MB 00:00:00
(5/9): epel/x86_64/primary_db | 6.7 MB 00:00:00
(6/9): updates/7/x86_64/primary_db | 5.0 MB 00:00:00
(7/9): google-cloud-compute/updateinfo | 1.1 kB 00:00:00
(8/9): google-cloud-compute/primary | 3.6 kB 00:00:00
(9/9): google-cloud-sdk/primary | 100 kB 00:00:00
google-cloud-compute 10/10
google-cloud-sdk 705/705
Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck', mode 'rt' at 0x7f4a26819ed0>
So it looks like it doesn't like the EPEL updateinfo but... what can I do about that? How can I fix this?
I found this, but I don't understand how it might apply to me?
Edit: Apparently updates work, only check-update fails. Which is a nuisance because cron runs check-update hourly and my inbox explodes. But I can still run updates.
Edit 2: It appears maybe something is going wrong with EPEL at the moment and I have to adjust my cron jobs for now.
centos yum
asked May 29 at 15:30
ChrisChris
456314
|
show 1 more comment
Starting this morning I'm getting errors checking for updates to packages with yum on Centos 7.6. When I run:
$ sudo yum clean all && sudo yum check-update
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Cleaning repos: base epel extras google-cloud-compute google-cloud-sdk updates
Cleaning up list of fastest mirrors
Other repos take up 1.5 M of disk space (use --verbose for details)
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Determining fastest mirrors
epel/x86_64/metalink | 15 kB 00:00:00
* base: mirror.cogentco.com
* epel: mirror.steadfastnet.com
* extras: mirror.cogentco.com
* updates: mirror.cogentco.com
base | 3.6 kB 00:00:00
epel | 4.9 kB 00:00:00
extras | 3.4 kB 00:00:00
google-cloud-compute/signature | 454 B 00:00:00
google-cloud-compute/signature | 1.8 kB 00:00:00 !!!
google-cloud-sdk/signature | 454 B 00:00:00
google-cloud-sdk/signature | 1.4 kB 00:00:00 !!!
updates | 3.4 kB 00:00:00
(1/9): base/7/x86_64/group_gz | 166 kB 00:00:00
(2/9): extras/7/x86_64/primary_db | 200 kB 00:00:00
(3/9): epel/x86_64/group_gz | 88 kB 00:00:00
(4/9): base/7/x86_64/primary_db | 6.0 MB 00:00:00
(5/9): epel/x86_64/primary_db | 6.7 MB 00:00:00
(6/9): updates/7/x86_64/primary_db | 5.0 MB 00:00:00
(7/9): google-cloud-compute/updateinfo | 1.1 kB 00:00:00
(8/9): google-cloud-compute/primary | 3.6 kB 00:00:00
(9/9): google-cloud-sdk/primary | 100 kB 00:00:00
google-cloud-compute 10/10
google-cloud-sdk 705/705
Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck', mode 'rt' at 0x7f4a26819ed0>
So it looks like it doesn't like the EPEL updateinfo but... what can I do about that? How can I fix this?
I found this, but I don't understand how it might apply to me?
Edit: Apparently updates work, only check-update fails. Which is a nuisance because cron runs check-update hourly and my inbox explodes. But I can still run updates.
Edit 2: It appears maybe something is going wrong with EPEL at the moment and I have to adjust my cron jobs for now.
centos yum
asked May 29 at 15:30
ChrisChris
456314
1
you can disable the epel repo until they get their act together?
– Grump
May 29 at 16:03
Can you check if 'baseurl:' line is uncommented and comment 'metalink:' line works for you in your epel repo?
– asktyagi
May 29 at 16:44
If your problem is not alleviated by usingyum clean allor pointing to another mirror, then the error is most likely with EPEL itself, and you would need to wait until they get it fixed. It looks like you may be able to comment out themetalinkline in the EPEL repo config and uncomment thebaseurlto get it working until it gets fixed upstream. If none of that works, will need to disable the EPEL repo until they fix it properly.
– GracefulRestart
May 29 at 17:08
@asktyagi @GracefulRestart I commentedmetalinkand uncommentedbaseurland it's still throwing the same error. I can update most packages by disabling epel like @Grump suggested...
– Chris
May 29 at 17:30
have you commented metalink and uncommented baseurl, post that clean the repo and tried to update? try sequentially not inline.
– asktyagi
May 29 at 17:33
|
show 1 more comment
Starting this morning I'm getting errors checking for updates to packages with yum on Centos 7.6. When I run:
$ sudo yum clean all && sudo yum check-update
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Cleaning repos: base epel extras google-cloud-compute google-cloud-sdk updates
Cleaning up list of fastest mirrors
Other repos take up 1.5 M of disk space (use --verbose for details)
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Determining fastest mirrors
epel/x86_64/metalink | 15 kB 00:00:00
* base: mirror.cogentco.com
* epel: mirror.steadfastnet.com
* extras: mirror.cogentco.com
* updates: mirror.cogentco.com
base | 3.6 kB 00:00:00
epel | 4.9 kB 00:00:00
extras | 3.4 kB 00:00:00
google-cloud-compute/signature | 454 B 00:00:00
google-cloud-compute/signature | 1.8 kB 00:00:00 !!!
google-cloud-sdk/signature | 454 B 00:00:00
google-cloud-sdk/signature | 1.4 kB 00:00:00 !!!
updates | 3.4 kB 00:00:00
(1/9): base/7/x86_64/group_gz | 166 kB 00:00:00
(2/9): extras/7/x86_64/primary_db | 200 kB 00:00:00
(3/9): epel/x86_64/group_gz | 88 kB 00:00:00
(4/9): base/7/x86_64/primary_db | 6.0 MB 00:00:00
(5/9): epel/x86_64/primary_db | 6.7 MB 00:00:00
(6/9): updates/7/x86_64/primary_db | 5.0 MB 00:00:00
(7/9): google-cloud-compute/updateinfo | 1.1 kB 00:00:00
(8/9): google-cloud-compute/primary | 3.6 kB 00:00:00
(9/9): google-cloud-sdk/primary | 100 kB 00:00:00
google-cloud-compute 10/10
google-cloud-sdk 705/705
Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck', mode 'rt' at 0x7f4a26819ed0>
So it looks like it doesn't like the EPEL updateinfo but... what can I do about that? How can I fix this?
I found this, but I don't understand how it might apply to me?
Edit: Apparently updates work, only check-update fails. Which is a nuisance because cron runs check-update hourly and my inbox explodes. But I can still run updates.
Edit 2: It appears maybe something is going wrong with EPEL at the moment and I have to adjust my cron jobs for now.
centos yum
asked May 29 at 15:30
ChrisChris
456314
Starting this morning I'm getting errors checking for updates to packages with yum on Centos 7.6. When I run:
$ sudo yum clean all && sudo yum check-update
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Cleaning repos: base epel extras google-cloud-compute google-cloud-sdk updates
Cleaning up list of fastest mirrors
Other repos take up 1.5 M of disk space (use --verbose for details)
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Determining fastest mirrors
epel/x86_64/metalink | 15 kB 00:00:00
* base: mirror.cogentco.com
* epel: mirror.steadfastnet.com
* extras: mirror.cogentco.com
* updates: mirror.cogentco.com
base | 3.6 kB 00:00:00
epel | 4.9 kB 00:00:00
extras | 3.4 kB 00:00:00
google-cloud-compute/signature | 454 B 00:00:00
google-cloud-compute/signature | 1.8 kB 00:00:00 !!!
google-cloud-sdk/signature | 454 B 00:00:00
google-cloud-sdk/signature | 1.4 kB 00:00:00 !!!
updates | 3.4 kB 00:00:00
(1/9): base/7/x86_64/group_gz | 166 kB 00:00:00
(2/9): extras/7/x86_64/primary_db | 200 kB 00:00:00
(3/9): epel/x86_64/group_gz | 88 kB 00:00:00
(4/9): base/7/x86_64/primary_db | 6.0 MB 00:00:00
(5/9): epel/x86_64/primary_db | 6.7 MB 00:00:00
(6/9): updates/7/x86_64/primary_db | 5.0 MB 00:00:00
(7/9): google-cloud-compute/updateinfo | 1.1 kB 00:00:00
(8/9): google-cloud-compute/primary | 3.6 kB 00:00:00
(9/9): google-cloud-sdk/primary | 100 kB 00:00:00
google-cloud-compute 10/10
google-cloud-sdk 705/705
Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck', mode 'rt' at 0x7f4a26819ed0>
So it looks like it doesn't like the EPEL updateinfo but... what can I do about that? How can I fix this?
I found this, but I don't understand how it might apply to me?
Edit: Apparently updates work, only check-update fails. Which is a nuisance because cron runs check-update hourly and my inbox explodes. But I can still run updates.
Edit 2: It appears maybe something is going wrong with EPEL at the moment and I have to adjust my cron jobs for now.
centos yum
centos yum
asked May 29 at 15:30
ChrisChris
456314
asked May 29 at 15:30
ChrisChris
456314
edited May 29 at 21:40
Chris
asked May 29 at 15:30
ChrisChris
456314
asked May 29 at 15:30
ChrisChris
456314
asked May 29 at 15:30
ChrisChris
456314
456314
1
you can disable the epel repo until they get their act together?
– Grump
May 29 at 16:03
Can you check if 'baseurl:' line is uncommented and comment 'metalink:' line works for you in your epel repo?
– asktyagi
May 29 at 16:44
If your problem is not alleviated by usingyum clean allor pointing to another mirror, then the error is most likely with EPEL itself, and you would need to wait until they get it fixed. It looks like you may be able to comment out themetalinkline in the EPEL repo config and uncomment thebaseurlto get it working until it gets fixed upstream. If none of that works, will need to disable the EPEL repo until they fix it properly.
– GracefulRestart
May 29 at 17:08
@asktyagi @GracefulRestart I commentedmetalinkand uncommentedbaseurland it's still throwing the same error. I can update most packages by disabling epel like @Grump suggested...
– Chris
May 29 at 17:30
have you commented metalink and uncommented baseurl, post that clean the repo and tried to update? try sequentially not inline.
– asktyagi
May 29 at 17:33
|
show 1 more comment
1
you can disable the epel repo until they get their act together?
– Grump
May 29 at 16:03
Can you check if 'baseurl:' line is uncommented and comment 'metalink:' line works for you in your epel repo?
– asktyagi
May 29 at 16:44
If your problem is not alleviated by usingyum clean allor pointing to another mirror, then the error is most likely with EPEL itself, and you would need to wait until they get it fixed. It looks like you may be able to comment out themetalinkline in the EPEL repo config and uncomment thebaseurlto get it working until it gets fixed upstream. If none of that works, will need to disable the EPEL repo until they fix it properly.
– GracefulRestart
May 29 at 17:08
@asktyagi @GracefulRestart I commentedmetalinkand uncommentedbaseurland it's still throwing the same error. I can update most packages by disabling epel like @Grump suggested...
– Chris
May 29 at 17:30
have you commented metalink and uncommented baseurl, post that clean the repo and tried to update? try sequentially not inline.
– asktyagi
May 29 at 17:33
1
1
you can disable the epel repo until they get their act together?
– Grump
May 29 at 16:03
you can disable the epel repo until they get their act together?
– Grump
May 29 at 16:03
Can you check if 'baseurl:' line is uncommented and comment 'metalink:' line works for you in your epel repo?
– asktyagi
May 29 at 16:44
Can you check if 'baseurl:' line is uncommented and comment 'metalink:' line works for you in your epel repo?
– asktyagi
May 29 at 16:44
If your problem is not alleviated by using
yum clean all or pointing to another mirror, then the error is most likely with EPEL itself, and you would need to wait until they get it fixed. It looks like you may be able to comment out the metalink line in the EPEL repo config and uncomment the baseurl to get it working until it gets fixed upstream. If none of that works, will need to disable the EPEL repo until they fix it properly.– GracefulRestart
May 29 at 17:08
If your problem is not alleviated by using
yum clean all or pointing to another mirror, then the error is most likely with EPEL itself, and you would need to wait until they get it fixed. It looks like you may be able to comment out the metalink line in the EPEL repo config and uncomment the baseurl to get it working until it gets fixed upstream. If none of that works, will need to disable the EPEL repo until they fix it properly.– GracefulRestart
May 29 at 17:08
@asktyagi @GracefulRestart I commented
metalink and uncommented baseurl and it's still throwing the same error. I can update most packages by disabling epel like @Grump suggested...– Chris
May 29 at 17:30
@asktyagi @GracefulRestart I commented
metalink and uncommented baseurl and it's still throwing the same error. I can update most packages by disabling epel like @Grump suggested...– Chris
May 29 at 17:30
have you commented metalink and uncommented baseurl, post that clean the repo and tried to update? try sequentially not inline.
– asktyagi
May 29 at 17:33
have you commented metalink and uncommented baseurl, post that clean the repo and tried to update? try sequentially not inline.
– asktyagi
May 29 at 17:33
|
show 1 more comment
2 Answers
2
active
oldest
votes
This is due to a bug in the bodhi-4.0.0 release which is apparently in the framework of the epel repo infrastructure. The bug caused incompatible update files to be generated and pushed to the production repos. A new update has been released and the repos should be repaired soon.
answered May 30 at 0:07
ChrisChris
456314
add a comment |
it seems to be new version of bodhi (bodhi-4.0.0) deployed.it should fix this issue. Please refer this https://pagure.io/releng/issue/8392 .
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521770%2fyum-failing-check-update%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is due to a bug in the bodhi-4.0.0 release which is apparently in the framework of the epel repo infrastructure. The bug caused incompatible update files to be generated and pushed to the production repos. A new update has been released and the repos should be repaired soon.
answered May 30 at 0:07
ChrisChris
456314
add a comment |
This is due to a bug in the bodhi-4.0.0 release which is apparently in the framework of the epel repo infrastructure. The bug caused incompatible update files to be generated and pushed to the production repos. A new update has been released and the repos should be repaired soon.
answered May 30 at 0:07
ChrisChris
456314
add a comment |
This is due to a bug in the bodhi-4.0.0 release which is apparently in the framework of the epel repo infrastructure. The bug caused incompatible update files to be generated and pushed to the production repos. A new update has been released and the repos should be repaired soon.
answered May 30 at 0:07
ChrisChris
456314
This is due to a bug in the bodhi-4.0.0 release which is apparently in the framework of the epel repo infrastructure. The bug caused incompatible update files to be generated and pushed to the production repos. A new update has been released and the repos should be repaired soon.
answered May 30 at 0:07
ChrisChris
456314
answered May 30 at 0:07
ChrisChris
456314
answered May 30 at 0:07
ChrisChris
456314
answered May 30 at 0:07
ChrisChris
456314
456314
add a comment |
add a comment |
it seems to be new version of bodhi (bodhi-4.0.0) deployed.it should fix this issue. Please refer this https://pagure.io/releng/issue/8392 .
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
it seems to be new version of bodhi (bodhi-4.0.0) deployed.it should fix this issue. Please refer this https://pagure.io/releng/issue/8392 .
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
it seems to be new version of bodhi (bodhi-4.0.0) deployed.it should fix this issue. Please refer this https://pagure.io/releng/issue/8392 .
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
it seems to be new version of bodhi (bodhi-4.0.0) deployed.it should fix this issue. Please refer this https://pagure.io/releng/issue/8392 .
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
answered May 30 at 1:10
Singaravelan RSingaravelan R
411
411
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Singaravelan R is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521770%2fyum-failing-check-update%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
you can disable the epel repo until they get their act together?
– Grump
May 29 at 16:03
Can you check if 'baseurl:' line is uncommented and comment 'metalink:' line works for you in your epel repo?
– asktyagi
May 29 at 16:44
If your problem is not alleviated by using
yum clean allor pointing to another mirror, then the error is most likely with EPEL itself, and you would need to wait until they get it fixed. It looks like you may be able to comment out themetalinkline in the EPEL repo config and uncomment thebaseurlto get it working until it gets fixed upstream. If none of that works, will need to disable the EPEL repo until they fix it properly.– GracefulRestart
May 29 at 17:08
@asktyagi @GracefulRestart I commented
metalinkand uncommentedbaseurland it's still throwing the same error. I can update most packages by disabling epel like @Grump suggested...– Chris
May 29 at 17:30
have you commented metalink and uncommented baseurl, post that clean the repo and tried to update? try sequentially not inline.
– asktyagi
May 29 at 17:33