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 1874010 - After installing lapack package, server shutdown is delayed while man-db-cache-update.service runs
Summary: After installing lapack package, server shutdown is delayed while man-db-cach...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: man-db
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Nikola Forró
QA Contact: Dita Stehlikova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-31 10:02 UTC by Sam Wachira
Modified: 2021-11-10 10:00 UTC (History)
5 users (show)

Fixed In Version: man-db-2.7.6.1-18.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:57:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1678464 0 unspecified CLOSED Consider moving man-db-cache-update to after boot instead of at shutdown 2021-05-25 15:00:06 UTC
Red Hat Product Errata RHBA-2021:4470 0 None None None 2021-11-09 19:57:34 UTC

Description Sam Wachira 2020-08-31 10:02:37 UTC
Description of problem:
After installing lapack package then rebooting the server, shutdown is delayed while man-db-cache-update.service runs
"A start job is running for man-db-cache-update.service (8min 30s / 15min)"

Version-Release number of selected component (if applicable):
lapack-3.8.0-8.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install package on RHEL 8 # dnf install lapack
2. Reboot server

Actual results:
- During shutdown, mandb cache update delays shutdown for up to 15 minutes "A start job is running for man-db-cache-update.service (5min 30s / 15min)"

Expected results:
- Installing lapack package should not add significant time delay during server shutdown.

Additional info:
- A BZ is open upstream. This does not only affect the lapack package.
Consider moving man-db-cache-update to after boot instead of at shutdown
https://bugzilla.redhat.com/show_bug.cgi?id=1678464

- Perhaps mandb update could run automatically in the background after installation?
- Alternatively, change mandb to run after boot as described in BZ#1678464

Comment 2 Nikola Forró 2020-09-03 13:27:36 UTC
mandb update already runs in the background after installation of packages containing man pages, that's the current behaviour. But the running update also prevents system shutdown, to ensure that mandb database stays consistent, because it's not able to recover from an interrupted update.

Changing it so that mandb update runs after boot would mean that the database is out of date until the next reboot, and that would be a regression. In Fedora, I resorted to attempting to restart the update after boot if it was previously interrupted [1], but that's rather fragile. But it does solve this problem, so I might end up backporting it to RHEL anyway.

As a workaround, you can install man-db-cron package and set SERVICE to "no" and CRON to "yes" in /etc/sysconfig/man-db. Doing that effectively reverts to the old behaviour, with mandb update being run as a cron job every day.

[1] https://src.fedoraproject.org/rpms/man-db/c/75b683fe495e761059857c797159610881208ca6?branch=master

Comment 16 errata-xmlrpc 2021-11-09 19:57:33 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 (man-db bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2021:4470


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