Bug 1577335

Summary: /usr/libexec/sssd/sssd_autofs SIGABRT crash daily
Product: Red Hat Enterprise Linux 7 Reporter: Brian Smith <briasmit>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED ERRATA QA Contact: sssd-qe <sssd-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: briasmit, fidencio, grajaiya, jhrozek, lslebodn, mkosek, mupadhye, mzidek, pbrezina, sgoveas, tscherf
Target Milestone: beta   
Target Release: 7.6   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: sssd-1.16.2-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:42:30 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:

Description Brian Smith 2018-05-11 18:23:23 UTC
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):

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.

Comment 11 Jakub Hrozek 2018-05-31 10:35:06 UTC
Upstream ticket:

Comment 12 Fabiano FidĂȘncio 2018-05-31 21:03:57 UTC

Comment 13 Fabiano FidĂȘncio 2018-05-31 21:20:51 UTC

Comment 18 errata-xmlrpc 2018-10-30 10:42:30 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.