SCIENTIFIC-LINUX-USERS Archives

July 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephen Isard <[log in to unmask]>
Reply To:
Stephen Isard <[log in to unmask]>
Date:
Sun, 23 Jul 2017 15:49:46 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
On Sun, 23 Jul 2017 15:55:23 -0400, Nico Kadel-Garcia <[log in to unmask]> wrote:

>I'm going to urge you to do "yum update" manually, *once*, to see if
>the problem occurs today.
>
>And "sl-fastbugs" is never going to be completely stable. Those are
>pre-production bugfixes, highly dynamic and changing quickly, one of
>the places most likely to have a discrepancy between the repodata and
>the published RPMs.

Thanks, Nico.  I've actually done a complete update from the command line, having found that
I could update individual packages.  I didn't have any good reason to think that it would solve the
problem with yum-cron, but the packages did want updating anyway.  

The problem wasn't specific to sl-fastbugs though.  There were a couple of sl-security packages waiting too,
and after I updated all of the fastbug ones, yum-cron still failed with the same error message
on the sl-security packages.

There haven't been any updates available since I did the manual update, so I haven't yet had a chance to
see what yum-cron will do with new ones.

>
>On Thu, Jul 20, 2017 at 12:05 PM, Stephen Isard
><[log in to unmask]> wrote:
>> yum-cron (3.4.3-150.el7.noarch on SL7.3) has stopped working for me. There
>> are a bunch of upgrades to be done in sl-fastbugs, but yum-cron bombs out
>> with an error message
>>
>> Traceback (most recent call last):
>>   File "/sbin/yum-cron", line 729, in <module>
>>     main()
>>   File "/sbin/yum-cron", line 726, in main
>>     base.updatesCheck()
>>   File "/sbin/yum-cron", line 649, in updatesCheck
>>     self.installUpdates(self.opts.update_messages)
>>   File "/sbin/yum-cron", line 570, in installUpdates
>>     result, err = self.sigCheckPkg(po)
>>   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 2758, in
>> sigCheckPkg
>>     sigresult = rpmUtils.miscutils.checkSig(ts, po.localPkg())
>>   File "/usr/lib/python2.7/site-packages/rpmUtils/miscutils.py", line 71, in
>> checkSig
>>     fdno = os.open(package, os.O_RDONLY) OSError: [Errno 2] No such file or
>> directory:
>> '/var/cache/yum/x86_64/7/sl-fastbugs/packages/lvm2-libs-2.02.166-1.el7_3.5.x86_64.rpm'
>>
>> /var/cache/yum/x86_64/7/sl-fastbugs/packages is in fact empty, possibly as a
>> result of a 'yum clean all'.
>>
>> It is nothing to do with lvm2-libs specifically.  I can upgrade that with
>> yum from the command line.  yum-cron then gives the same error on the next
>> package.
>>
>> I haven't knowingly changed anything away from the default yum or yum-cron
>> configuration.  I do notice 'keepcache=0' in /etc/yum.conf, while the man
>> page says that the default is 'keepcache=1'.
>>
>> Any ideas on what could be making yum-cron insist on those cache files when
>> yum itself doesn't, and how to change that?
>>
>> Stephen Isard

ATOM RSS1 RSS2