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:
The sssd_autofs process crashes shortly after 19:00 each day, with a signal 6 (SIGABRT).   Log file shows:  [sssd[autofs]] [talloc_log_fn] (0x0010): Bad talloc magic value - unknown value

Version-Release number of selected component (if applicable):
sssd-common-1.13.3-58.el6_9

How reproducible:
Occur's shortly after 21:00 daily.  

Steps to Reproduce:
1. Between 21:00 and 21:01 each day sssd_autofs crashes.

Actual results:
sssd_autofs crashes

Expected results:
sssd_autofs doesn't crash

Additional info:
Only happening on one RHEL 6.9 server in environment.   Tried copying sssd.conf file from server that didn't have issue to server that did, and issue still happens daily.   The servers have the same version of the sssd filesets.

Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3752

master:
 7567215

sssd-1-13:
 8cf14ee

As there is no reliable reproducer and 
autofs test are passing 
CI links:
with 389 ds: https://platform-stg-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/sssd/view/rhel-7.6/job/sssd-rhel-7.6-candidate-runtest-ldap-provider-389-automount/31/console

with Openldap ds: https://platform-stg-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/sssd/view/rhel-7.6/job/sssd-rhel-7.6-candidate-runtest-ldap-provider-openldap-automount/17/console

test with sssd-1.16.2-9.el7 

marking this SanityOnly Verified.

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.

https://access.redhat.com/errata/RHSA-2018:3158