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.

Description of problem:

We use nss module winbind as our Linux hosts are joined to AD. When a software upgrade is done on winbind, and winbind is replaced, we restart winbind, but if crond previously loaded the old nss-winbind library because it was executing user jobs, then when the new module is put into place, crond will segfault each time it tries to run user jobs. 

Version-Release number of selected component (if applicable):

1.4.11-23

Steps to Reproduce:
1. Start crond
2. Make crond execute a job for a user who is in AD
3. Update nss-winbind library
4. Wait for cron to execute the next cron job. It will segfault.

Expected results:

I would expect that crond would close and re-open the nss library between runs.

Additional info:

If I restart crond after replacing winbind, there is no problem.

My very rough guess is that crond is keeping old references to user information in it's internal representation (database) of the tasks to execute, and when it tries to switch to the user to actually execute the job, something explodes.

However, without the dumped core, I'm afraid I won't be able to move much further on this. Would you be able to provide one?

Given no response to the NEEDINFO in 2 months, and RHEL 7 being in limited support phase, I'm not seeing this issue as being likely to get addressed. If this is also a problem in more recent RHEL version(s), feel free to re-open this, or report a new issue against the appropriate RHEL version.