RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 742363 - yum-cron runs at nice 10 (from anacrontab), restarted service inherit that priority
Summary: yum-cron runs at nice 10 (from anacrontab), restarted service inherit that pr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.1
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 795455
TreeView+ depends on / blocked
 
Reported: 2011-09-29 20:29 UTC by Orion Poplawski
Modified: 2014-01-21 06:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The anacron scheduler starts the yum-cron utility with the "nice" value of 10. This caused Yum's RPM transactions to run at very low priority level. Also, any updated service inherited this "nice" value, which influenced the system behavior. This update adds the "reset_nice" configuration option, which allows Yum to reset the "nice" value to 0 before running an RPM transaction. With this option set, Yum's RPM transactions run at normal priority level so that updated services are restarted with normal priority as expected.
Clone Of:
Environment:
Last Closed: 2012-06-20 13:53:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 676427 0 unspecified CLOSED yum-updatesd runs with "nice 19", and that is inherited when it restarts services 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2012:0857 0 normal SHIPPED_LIVE yum bug fix and enhancement update 2012-06-19 20:48:27 UTC

Internal Links: 676427

Description Orion Poplawski 2011-09-29 20:29:01 UTC 
Description of problem:

yum-cron runs at nice 10 (from anacrontab), restarted service inherit that priority.

Adding:

# Reset our priority so restarted services don't inherit the lower priority
# from cron
renice 0 $$

To the 0yum.cron script should fix.

Version-Release number of selected component (if applicable):
yum-cron-3.2.29-17.el6.noarch
Comment 2 Orion Poplawski 2011-09-30 01:45:16 UTC 
Looks like you would want:

renice 0 $$ > /dev/null

to avoid the output from renice.
Comment 3 RHEL Program Management 2011-10-07 16:20:36 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 4 Mike Lococo 2011-10-07 21:08:45 UTC 
yum-updatesd suffers from the same issue (at nice +19 instead of nice +10), see Bug 552279 for details and a workaround.

packagekit-cron is probably the last option for doing automatic updates on a
standalone RHEL6 system.  I haven't tested it to see whether it suffers from a
similar bug, but it's a more ambitious framework than either yum-updatesd or
yum-cron so it might address the issue.

Alternately one would have to look at satellite or spacewalk, which are pretty
heavyweight solutions generally targeted toward large shops.
Comment 12 Miroslav Svoboda 2012-02-27 10:08:50 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The anacron scheduler starts the yum-cron utility with the "nice" value of 10. This caused Yum's RPM transactions to run at very low priority level. Also, any updated service inherited this "nice" value, which influenced the system behavior. This update adds the "reset_nice" configuration option, which allows Yum to reset the "nice" value to 0 before running an RPM transaction. With this option set, Yum's RPM transactions run at normal priority level so that updated services are restarted with normal priority as expected.
Comment 16 errata-xmlrpc 2012-06-20 13:53:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0857.html
Note You need to log in before you can comment on or make changes to this bug.