#3234 sssd_be keeps crashing
Closed: Fixed None Opened 3 years ago by lslebodn.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1392444

Description of problem:
Customer said that SSSD was updated as part of yum update command from  RHEL
7.2 to RHEL 7.3, since then sssd keeps crashing whenever they attempted to
start sssd.service.

messages:Nov  4 12:26:47 host abrt-hook-ccpp: Process 30558 (sssd_be) of user
0 killed by SIGSEGV - dumping core
messages:Nov  4 12:26:47 host abrt-hook-ccpp: Process 30561 (sssd_be) of user
0 killed by SIGSEGV - ignoring (repeated crash)
messages:Nov  4 12:26:49 host abrt-hook-ccpp: Process 30599 (sssd_be) of user
0 killed by SIGSEGV - ignoring (repeated crash)
messages:Nov  4 12:26:53 host abrt-hook-ccpp: Process 30941 (sssd_be) of user
0 killed by SIGSEGV - ignoring (repeated crash)


From yum.log:
Nov 04 12:22:18 Updated: sssd-common-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-krb5-common-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-common-pac-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-ad-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-ipa-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-ldap-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-krb5-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-proxy-1.14.0-43.el7.x86_64
Nov 04 12:22:18 Updated: sssd-1.14.0-43.el7.x86_64

Version-Release number of selected component (if applicable):
sssd-1.14.0-43.el7.x86_64                                   Fri Nov  4 12:22:18
2016


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
From the core dump:
Core was generated by `/usr/libexec/sssd/sssd_be --domain redecorp --uid 0
--gid 0 --debug-to-files'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007fa2766492a2 in ad_subdom_reinit
(subdoms_ctx=subdoms_ctx@entry=0x7fa286512aa0) at
src/providers/ad/ad_subdomains.c:626
626         canonicalize = dp_opt_get_bool(

(gdb) backtrace
#0  0x00007fa2766492a2 in ad_subdom_reinit
(subdoms_ctx=subdoms_ctx@entry=0x7fa286512aa0) at
src/providers/ad/ad_subdomains.c:626
#1  0x00007fa27664afb3 in ad_subdomains_init (mem_ctx=<optimized out>,
be_ctx=0x7fa2864b9540, ad_id_ctx=<optimized out>, dp_methods=0x7fa2865186a0)
    at src/providers/ad/ad_subdomains.c:1528
#2  0x00007fa2857552d6 in dp_target_run_constructor (be_ctx=0x7fa2864b9540,
target=0x7fa2864d4bc0) at src/providers/data_provider/dp_targets.c:246
#3  dp_target_init (target=0x7fa2864d4bc0, modules=0x7fa2864d3840,
provider=0x7fa2864d3b60, be_ctx=0x7fa2864b9540)
    at src/providers/data_provider/dp_targets.c:358
#4  dp_load_targets (modules=0x7fa2864d3840, targets=0x7fa2864d4a70,
provider=0x7fa2864d3b60, be_ctx=0x7fa2864b9540)
    at src/providers/data_provider/dp_targets.c:484
#5  dp_init_targets (mem_ctx=mem_ctx@entry=0x7fa2864d3b60,
be_ctx=be_ctx@entry=0x7fa2864b9540, provider=provider@entry=0x7fa2864d3b60,
    modules=0x7fa2864d3840) at src/providers/data_provider/dp_targets.c:530
#6  0x00007fa28575466b in dp_init (ev=0x7fa2864b0c10,
be_ctx=be_ctx@entry=0x7fa2864b9540, uid=<optimized out>, gid=0)
    at src/providers/data_provider/dp.c:120
#7  0x00007fa28574cc77 in be_process_init (mem_ctx=<optimized out>,
be_domain=0x7fa2864aa220 "redecorp", uid=<optimized out>, gid=0,
    ev=0x7fa2864b0c10, cdb=0x7fa2864b2170) at
src/providers/data_provider_be.c:450
#8  0x00007fa28574ba59 in main (argc=8, argv=<optimized out>) at
src/providers/data_provider_be.c:562

(gdb) frame 1
#1  0x00007fa27664afb3 in ad_subdomains_init (mem_ctx=<optimized out>,
be_ctx=0x7fa2864b9540, ad_id_ctx=<optimized out>, dp_methods=0x7fa2865186a0)
    at src/providers/ad/ad_subdomains.c:1528
1528        ret = ad_subdom_reinit(sd_ctx);
(gdb) list
1523            DEBUG(SSSDBG_CRIT_FAILURE, "Unable to setup ptask "
1524                  "[%d]: %s\n", ret, sss_strerror(ret));
1525            /* Ignore, responders will trigger refresh from time to time.
*/
1526        }
1527
1528        ret = ad_subdom_reinit(sd_ctx);
1529        if (ret != EOK) {
1530            DEBUG(SSSDBG_MINOR_FAILURE, "Could not reinitialize subdomains.
"
1531                  "Users from trusted domains might not be resolved
correctly\n");
1532            /* Ignore this error and try to discover the subdomains later
*/

Fields changed blockedby: => blocking: => changelog: => coverity: => description: Ticket was cloned from Red Hat Bugzilla (product ''Red Hat Enterprise Linux 7''): [https://bugzilla.redhat.com/show_bug.cgi?id=1392444 Bug 1392444] {{{ Description of problem: Customer said that SSSD was updated as part of yum update command from RHEL 7.2 to RHEL 7.3, since then sssd keeps crashing whenever they attempted to start sssd.service. messages:Nov 4 12:26:47 koror abrt-hook-ccpp: Process 30558 (sssd_be) of user 0 killed by SIGSEGV - dumping core messages:Nov 4 12:26:47 koror abrt-hook-ccpp: Process 30561 (sssd_be) of user 0 killed by SIGSEGV - ignoring (repeated crash) messages:Nov 4 12:26:49 koror abrt-hook-ccpp: Process 30599 (sssd_be) of user 0 killed by SIGSEGV - ignoring (repeated crash) messages:Nov 4 12:26:53 koror abrt-hook-ccpp: Process 30941 (sssd_be) of user 0 killed by SIGSEGV - ignoring (repeated crash) From yum.log: Nov 04 12:22:18 Updated: sssd-common-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-krb5-common-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-common-pac-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-ad-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-ipa-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-ldap-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-krb5-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-proxy-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-1.14.0-43.el7.x86_64 Version-Release number of selected component (if applicable): sssd-1.14.0-43.el7.x86_64 Fri Nov 4 12:22:18 2016 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: From the core dump: Core was generated by `/usr/libexec/sssd/sssd_be --domain redecorp --uid 0 --gid 0 --debug-to-files'. Program terminated with signal 11, Segmentation fault. #0 0x00007fa2766492a2 in ad_subdom_reinit (subdoms_ctx=subdoms_ctx@entry=0x7fa286512aa0) at src/providers/ad/ad_subdomains.c:626 626 canonicalize = dp_opt_get_bool( (gdb) backtrace #0 0x00007fa2766492a2 in ad_subdom_reinit (subdoms_ctx=subdoms_ctx@entry=0x7fa286512aa0) at src/providers/ad/ad_subdomains.c:626 #1 0x00007fa27664afb3 in ad_subdomains_init (mem_ctx=<optimized out="">, be_ctx=0x7fa2864b9540, ad_id_ctx=<optimized out="">, dp_methods=0x7fa2865186a0) at src/providers/ad/ad_subdomains.c:1528 #2 0x00007fa2857552d6 in dp_target_run_constructor (be_ctx=0x7fa2864b9540, target=0x7fa2864d4bc0) at src/providers/data_provider/dp_targets.c:246 #3 dp_target_init (target=0x7fa2864d4bc0, modules=0x7fa2864d3840, provider=0x7fa2864d3b60, be_ctx=0x7fa2864b9540) at src/providers/data_provider/dp_targets.c:358 #4 dp_load_targets (modules=0x7fa2864d3840, targets=0x7fa2864d4a70, provider=0x7fa2864d3b60, be_ctx=0x7fa2864b9540) at src/providers/data_provider/dp_targets.c:484 #5 dp_init_targets (mem_ctx=mem_ctx@entry=0x7fa2864d3b60, be_ctx=be_ctx@entry=0x7fa2864b9540, provider=provider@entry=0x7fa2864d3b60, modules=0x7fa2864d3840) at src/providers/data_provider/dp_targets.c:530 #6 0x00007fa28575466b in dp_init (ev=0x7fa2864b0c10, be_ctx=be_ctx@entry=0x7fa2864b9540, uid=<optimized out="">, gid=0) at src/providers/data_provider/dp.c:120 #7 0x00007fa28574cc77 in be_process_init (mem_ctx=<optimized out="">, be_domain=0x7fa2864aa220 "redecorp", uid=<optimized out="">, gid=0, ev=0x7fa2864b0c10, cdb=0x7fa2864b2170) at src/providers/data_provider_be.c:450 #8 0x00007fa28574ba59 in main (argc=8, argv=<optimized out="">) at src/providers/data_provider_be.c:562 (gdb) frame 1 #1 0x00007fa27664afb3 in ad_subdomains_init (mem_ctx=<optimized out="">, be_ctx=0x7fa2864b9540, ad_id_ctx=<optimized out="">, dp_methods=0x7fa2865186a0) at src/providers/ad/ad_subdomains.c:1528 1528 ret = ad_subdom_reinit(sd_ctx); (gdb) list 1523 DEBUG(SSSDBG_CRIT_FAILURE, "Unable to setup ptask " 1524 "[%d]: %s\n", ret, sss_strerror(ret)); 1525 /* Ignore, responders will trigger refresh from time to time. */ 1526 } 1527 1528 ret = ad_subdom_reinit(sd_ctx); 1529 if (ret != EOK) { 1530 DEBUG(SSSDBG_MINOR_FAILURE, "Could not reinitialize subdomains. " 1531 "Users from trusted domains might not be resolved correctly\n"); 1532 /* Ignore this error and try to discover the subdomains later */ }}} => Ticket was cloned from Red Hat Bugzilla (product ''Red Hat Enterprise Linux 7''): [https://bugzilla.redhat.com/show_bug.cgi?id=1392444 Bug 1392444] {{{ Description of problem: Customer said that SSSD was updated as part of yum update command from RHEL 7.2 to RHEL 7.3, since then sssd keeps crashing whenever they attempted to start sssd.service. messages:Nov 4 12:26:47 host abrt-hook-ccpp: Process 30558 (sssd_be) of user 0 killed by SIGSEGV - dumping core messages:Nov 4 12:26:47 host abrt-hook-ccpp: Process 30561 (sssd_be) of user 0 killed by SIGSEGV - ignoring (repeated crash) messages:Nov 4 12:26:49 host abrt-hook-ccpp: Process 30599 (sssd_be) of user 0 killed by SIGSEGV - ignoring (repeated crash) messages:Nov 4 12:26:53 host abrt-hook-ccpp: Process 30941 (sssd_be) of user 0 killed by SIGSEGV - ignoring (repeated crash) From yum.log: Nov 04 12:22:18 Updated: sssd-common-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-krb5-common-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-common-pac-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-ad-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-ipa-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-ldap-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-krb5-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-proxy-1.14.0-43.el7.x86_64 Nov 04 12:22:18 Updated: sssd-1.14.0-43.el7.x86_64 Version-Release number of selected component (if applicable): sssd-1.14.0-43.el7.x86_64 Fri Nov 4 12:22:18 2016 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: From the core dump: Core was generated by `/usr/libexec/sssd/sssd_be --domain redecorp --uid 0 --gid 0 --debug-to-files'. Program terminated with signal 11, Segmentation fault. #0 0x00007fa2766492a2 in ad_subdom_reinit (subdoms_ctx=subdoms_ctx@entry=0x7fa286512aa0) at src/providers/ad/ad_subdomains.c:626 626 canonicalize = dp_opt_get_bool( (gdb) backtrace #0 0x00007fa2766492a2 in ad_subdom_reinit (subdoms_ctx=subdoms_ctx@entry=0x7fa286512aa0) at src/providers/ad/ad_subdomains.c:626 #1 0x00007fa27664afb3 in ad_subdomains_init (mem_ctx=<optimized out="">, be_ctx=0x7fa2864b9540, ad_id_ctx=<optimized out="">, dp_methods=0x7fa2865186a0) at src/providers/ad/ad_subdomains.c:1528 #2 0x00007fa2857552d6 in dp_target_run_constructor (be_ctx=0x7fa2864b9540, target=0x7fa2864d4bc0) at src/providers/data_provider/dp_targets.c:246 #3 dp_target_init (target=0x7fa2864d4bc0, modules=0x7fa2864d3840, provider=0x7fa2864d3b60, be_ctx=0x7fa2864b9540) at src/providers/data_provider/dp_targets.c:358 #4 dp_load_targets (modules=0x7fa2864d3840, targets=0x7fa2864d4a70, provider=0x7fa2864d3b60, be_ctx=0x7fa2864b9540) at src/providers/data_provider/dp_targets.c:484 #5 dp_init_targets (mem_ctx=mem_ctx@entry=0x7fa2864d3b60, be_ctx=be_ctx@entry=0x7fa2864b9540, provider=provider@entry=0x7fa2864d3b60, modules=0x7fa2864d3840) at src/providers/data_provider/dp_targets.c:530 #6 0x00007fa28575466b in dp_init (ev=0x7fa2864b0c10, be_ctx=be_ctx@entry=0x7fa2864b9540, uid=<optimized out="">, gid=0) at src/providers/data_provider/dp.c:120 #7 0x00007fa28574cc77 in be_process_init (mem_ctx=<optimized out="">, be_domain=0x7fa2864aa220 "redecorp", uid=<optimized out="">, gid=0, ev=0x7fa2864b0c10, cdb=0x7fa2864b2170) at src/providers/data_provider_be.c:450 #8 0x00007fa28574ba59 in main (argc=8, argv=<optimized out="">) at src/providers/data_provider_be.c:562 (gdb) frame 1 #1 0x00007fa27664afb3 in ad_subdomains_init (mem_ctx=<optimized out="">, be_ctx=0x7fa2864b9540, ad_id_ctx=<optimized out="">, dp_methods=0x7fa2865186a0) at src/providers/ad/ad_subdomains.c:1528 1528 ret = ad_subdom_reinit(sd_ctx); (gdb) list 1523 DEBUG(SSSDBG_CRIT_FAILURE, "Unable to setup ptask " 1524 "[%d]: %s\n", ret, sss_strerror(ret)); 1525 /* Ignore, responders will trigger refresh from time to time. */ 1526 } 1527 1528 ret = ad_subdom_reinit(sd_ctx); 1529 if (ret != EOK) { 1530 DEBUG(SSSDBG_MINOR_FAILURE, "Could not reinitialize subdomains. " 1531 "Users from trusted domains might not be resolved correctly\n"); 1532 /* Ignore this error and try to discover the subdomains later */ }}} design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 patch: => 0 review: True => 0 selected: => testsupdated: => 0

Fields changed

owner: somebody => sbose
patch: 0 => 1
status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.3

resolution: => fixed
status: assigned => closed

Metadata Update from @lslebodn:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.14.3

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4267

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata