Bug 222835
Summary: | yum-updatesd does not log updates | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gerald Leung <gerald.leung> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | amyagi, bkearney, bookreviewer, edwinh, gdr, mfreemon, orion, rbh00 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-02-06 07:13:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gerald Leung
2007-01-16 14:36:14 UTC
This also happens when yum is run like the old yum cron: /usr/bin/yum -R 120 -e 0 -d 1 -y shell /etc/yum/yum-daily.yum # cat /etc/yum/yum-daily.yum update ts run exit No updates are logged to /var/log/yum.log. This is with 3.0.3-1.fc6 (upgraded before the general update). My symptom is exactly like Orion's, with the same yum version. Moreover, the "Updated: " lines that as well appeared at /var/log/messages also stopped appearing. In both files /var/log/yum/log and /var/log/messages the very last "Updated: " line reads as follows: Jan 16 04:31:49 Updated: yum.noarch 3.0.3-1.fc6 so it's apparent that the updating of this package caused further writes to /var/log/yum.log and /var/log/messages to stop. I am having the same problem as Orion's. yum stopped logging to /var/log/yum.log after yum.noarch 3.0.3-1.fc6 was installed. However, if I run yum manually, it writes to the log file. In my original comment, I said "If I were to update using Yum through command line, changes to system packages are logged to /var/log/yum.log". By "command line", I meant manually entering a command such as "yum update somepackage" manually to install/update/delete a package. I currently have yum-3.0.3-1.fc6 installed. Having had the same issue (nothing in yum.log after 3.0.3-1 was installed) I played around with this. It seems that you need at least -d2 for yum to write anything to yum.log. Unfortunately at this level it also spouts a load of other debugging information. I too run yum from a cron job (with -e0 -d0 -y) and so don't want any debugging output (unless it fails), but yum.log must be updated so I can track what's actually gone on and so it can be picked up by logwatch. Please can someone address this. I'm only using a cron job because updatesd stopeed logging anywhere, and now it seems that command line yum is now similiarly broken. it's being looked into, now. I'll update here when we have a fix. This should be fixed in the next release of yum. |