| Summary: | yum should not output a critical error if it's waiting for a lock | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Devin Bayer <dev> |
| Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | admiller, dev, ffesti, firas.alkafri, jzeleny, packaging-team-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-19 20:04:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
yum tries to lock /var/run/yum.pid and if another running process owns the lock, it continues trying every two seconds. Each attempt produces a critical error message: Existing lock /var/run/yum.pid: another copy is running as pid 16502. Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 89 M RSS (361 MB VSZ) Started: Mon Dec 16 04:16:09 2013 - 00:03 ago State : Running, pid: 16502 If the other process is transient, yum continues normally. But the critical error level means it can't be filtered out. We run a configuration management system every five minutes which calls "yum check-update" and yum-cron, which updates all packages daily. When we're unlucky, their runs coincide and an we receive an error email from cron. I would like to see that yum does not consider a normal and transient state as a critical error so it's not output if --quiet or --errorlevel=0 is used.