Bug 982088 - Delta RPM messages sent by yum-cron
Delta RPM messages sent by yum-cron
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
19
All Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-08 02:32 EDT by Jan ONDREJ
Modified: 2014-06-09 07:02 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-09 07:17:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan ONDREJ 2013-07-08 02:32:19 EDT
Description of problem:
Again, some messages from yum-cron has been sent to wrong output and this causes yum-cron to send unnecessary messages.

Version-Release number of selected component (if applicable):
yum-3.4.3-99.fc19.noarch

How reproducible:
after each update from yum-cron

Actual results:
From: Anacron <root>
Date: Mon,  8 Jul 2013 03:52:04 +0200 (CEST)
To: root
Subject: Anacron job 'cron.daily' on work

/etc/cron.daily/0yum-daily.cron:

Delta RPMs reduced 4.6 M of updates to 2.1 M (54% saved)
delta does not match installed data
Finishing delta rebuilds of 4 package(s) (4.4 M)
Some delta RPMs failed to download or rebuild. Retrying..

Expected results:
--- no mail ---

Additional info:
Comment 1 Jan ONDREJ 2013-07-09 02:06:41 EDT
Presto has similar problem. Please fix this too:

No Presto metadata available for xxxxxxxxx
Comment 2 Zdeněk Pavlas 2013-07-09 04:37:36 EDT
http://lists.baseurl.org/pipermail/yum-devel/2012-November/009718.html

This is an old bug.. see BZ 873428, my patch and discussion.  log messages with "info" log level SHOULD be printed with -q or -d0 Yum options (used by yum cron)

Note that the "delta does not match installed data" and "Some delta RPMs failed to download or rebuild. Retrying.." messages are useful warnings and it's probably ok to report this.
Comment 3 Jan ONDREJ 2013-07-09 07:07:41 EDT
This patch has been rejected and bug is still present. Reopening.
Comment 4 Jan ONDREJ 2013-07-10 08:02:24 EDT
Another message:

Subject: Cron <root@work> run-parts /etc/cron.hourly                            

/etc/cron.hourly/0yum-hourly.cron:

BDB2053 Freeing read locks for locker 0xbd3: 7976/139765745551360
BDB2053 Freeing read locks for locker 0xbd4: 7976/139765745551360
BDB2053 Freeing read locks for locker 0xbd5: 7976/139765745551360
BDB2053 Freeing read locks for locker 0xbd6: 7976/139765745551360
Comment 5 Panu Matilainen 2013-07-10 08:07:49 EDT
Those "freeing read locks" messages come from rpm, telling you that something in the system has been a bad boy and left stale rpmdb locks behind it.
Comment 6 Jan ONDREJ 2013-07-24 01:40:50 EDT
And more messages. These are more disturbing, because they are comming hourly.

Subject: Cron <root@work> run-parts /etc/cron.hourly                            

/etc/cron.hourly/0yum-hourly.cron:

Not using downloaded repomd.xml because it is older than what we have:
  Current   : Sat Jun 29 21:38:11 2013
  Downloaded: Sat Jun 29 00:56:36 2013
Comment 7 Zdeněk Pavlas 2013-07-24 03:52:30 EDT
This is something yum *should* complain about- a repository was replaced with an older version.  Sadly there's no repoid in the message, but you can probably find it by greping the timestamp.  What's the output of:

$ python -c 'import time; print int(time.mktime(time.strptime("Sat Jun 29 21:38:11 2013")))'
1372534691
$ grep 1372534691 $(find /var/cache/yum -name repomd.xml)
Comment 8 Jan ONDREJ 2013-08-05 02:51:53 EDT
I see new options in yum-3.4.3-104.fc19.noarch.

[base]
# Use this to filter Yum core messages
# -4: critical
# -3: critical+errors
# -2: critical+errors+warnings (default)
debuglevel = -2

Was this problem solved by these options?
Comment 9 Zdeněk Pavlas 2013-08-05 03:10:53 EDT
Yes. For some reason, bohdi didn't send BZ messages.
Comment 10 Jan ONDREJ 2013-08-22 01:23:46 EDT
My current settings are:

[ondrejj@ftp ~]$ grep debuglevel /etc/yum/yum-cron.conf
debuglevel = -4

But still getting this message from cron:

Subject: Anacron job 'cron.daily' on ftp.upjs.sk                                

/etc/cron.daily/0yum-daily.cron:

The following updates will be applied on ftp.upjs.sk:
================================================================================
 Package                Arch        Verzia              Repozitár          Veľ. 
================================================================================
Aktualizuje sa:
 libusb                 x86_64      1:0.1.5-2.fc19      updates-upjs       35 k
 tcp_wrappers-libs      x86_64      7.6-75.fc19         updates-upjs       66 k

Zhrnutie transakcie
================================================================================
Upgrade  2 Balíčky
The updates were successfully applied

Is this message really critical? It will send me one email per server for each server with available updates.
Can I stop sending these messages?
Comment 11 Zdeněk Pavlas 2013-08-26 06:41:58 EDT
Yes, these messages are not conditional..  It'd be nice to be able to turn this off. http://lists.baseurl.org/pipermail/yum-devel/2013-August/010334.html
Comment 12 Jan ONDREJ 2013-10-09 01:40:28 EDT
New yum release, new messages:

Subject: Cron <root@work> run-parts /etc/cron.hourly                            

/etc/cron.hourly/0yum-hourly.cron:

Načítané zásuvné moduly:auto-update-debuginfo, langpacks

These are send hourly even if no updates are applied. :-(

Version-Release number of selected component (if applicable):
yum-3.4.3-111.fc19.noarch

Curious, that there is no change in yum version, only in release. Zdenek, can you please apply your patches to avoid all unnecessary messages?
Comment 13 Zdeněk Pavlas 2013-10-09 04:10:55 EDT
[ondrejj@ftp ~]$ grep debuglevel /etc/cron.hourly/0yum-hourly.cron
?

If it's not there, please set it to -2 (you should see only warning then).
debuglevel = -2 is set in the default yum-cron-hourly.conf but RPM keeps the old one if modified.

Note You need to log in before you can comment on or make changes to this bug.