yum check-updates seems broken

[Spork Schivago]

Anyone having trouble with yum check-updates? I have a cron script that runs hourly and I've seen it's failing with the following:

Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/gen/updateinfo.xml', mode 'rt' at 0x1ce80c0>

If I run yum check-updates, I see:

[[email protected] spork]# yum check-updates
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
 * EA4: 69.72.212.11
 * cpanel-addons-production-feed: 69.72.212.11
 * base: mirrors.linode.com
 * epel: fedora-epel.mirrors.tds.net
 * extras: mirrors.linode.com
 * updates: mirrors.linode.com
Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/gen/updateinfo.xml', mode 'rt' at 0x1d175d0>

I've tried a yum clean all, which removes the file, but when I do a yum update or a yum check-updates, it breaks with the same message (different number at the end).

From googling, it seems stuff like this has happened in the past, and it was because of a problem with the repo's server. I'm trying to determine if that is the case here, or if I'm just having this problem.

I put this in the Security section because right now, I cannot get EPEL security updates. I suspect if I disable the repository (just temporarily), then other updates should come through....

Any suggestions?

Thanks!

 

[cPanelMichael]

Hello,

That looks like an issue with the EPEL repository. I'm not seeing the same error message when running "yum check-updates" on test systems with the stock CentOS repos.

Thank you.

 

[JacobPerkins]

This happens to me from time to time with EPEL. I generally just skip that repo for that update and try it again later

 

[Spork Schivago]

Hello,

That looks like an issue with the EPEL repository. I'm not seeing the same error message when running "yum check-updates" on test systems with the stock CentOS repos.

Thank you.

But when you enable the EPEL repository, then you do see the same error message? With the other thread (the one with ModSec and the 127.0.0.1 hostname), I want to make sure this isn't related to a possible security breach. I would think it'd be hard for a person to get into my server with me having ModSec enabled, CSF enabled, and rkhunter running, but I guess in today's world, there's almost always a way around security systems.

 

[JacobPerkins]

I did not specifically see this error earlier, but it's possible yum was using a different mirror than yours.

 

[Spork Schivago]

This happens to me from time to time with EPEL. I generally just skip that repo for that update and try it again later

I missed this post earlier. I think we were posting at the same time. I was worried that this might have something to do with some other issues I'm having on my system. I noticed yum is connecting to some linode repositories. I'm going to see if I can change that, to get it to use a different mirror, at least for the EPEL repository.

 

[Spork Schivago]

Seems to be fixed now. Thanks!