#3523 ABRT crash - /usr/libexec/sssd/sssd_nss in setnetgrent_result_timeout
Closed: Fixed 2 years ago Opened 2 years ago by lslebodn.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1487944

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
sssd is having an ABRT crash on the server.

Version-Release number of selected component (if applicable):
RHEL 6.9
sssd-common-1.13.3-56.el6.x86_64

How reproducible:
Deterministic

Actual results:
sssd has an ABRT crash

Expected results:
sssd should run without crashing

Additional info:
I am collecting more information from the customer for clarity on what commands
are being run while observing the crash.

(gdb) bt
#0  0x0000003b55c32495 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x0000003b55c33c75 in abort () at abort.c:92
#2  0x0000003b5900248c in talloc_abort (reason=0x3b5900af98 "Bad talloc magic value - unknown value") at ../talloc.c:399
#3  0x0000003b5900a5e8 in talloc_abort_unknown_value (ptr=0xcc0ef0, name=0x423424 "struct getent_ctx") at ../talloc.c:417
#4  talloc_chunk_from_ptr (ptr=0xcc0ef0, name=0x423424 "struct getent_ctx") at ../talloc.c:436
#5  __talloc_get_name (ptr=0xcc0ef0, name=0x423424 "struct getent_ctx") at ../talloc.c:1419
#6  talloc_check_name (ptr=0xcc0ef0, name=0x423424 "struct getent_ctx") at ../talloc.c:1442
#7  0x0000000000411c5a in setnetgrent_result_timeout (ev=<value optimized out>, te=<value optimized out>, current_time=..., pvt=<value optimized out>)
    at src/responder/nss/nsssrv_netgroup.c:701
#8  0x0000003b5dc08c61 in tevent_common_loop_timer_delay (ev=0xcad450) at ../tevent_timed.c:341
#9  0x0000003b5dc09ca2 in epoll_event_loop_once (ev=0xcad450, location=<value optimized out>) at ../tevent_epoll.c:911
#10 0x0000003b5dc082d6 in std_event_loop_once (ev=0xcad450, location=0x373ce5dd40 "src/util/server.c:668") at ../tevent_standard.c:114
#11 0x0000003b5dc03c3d in _tevent_loop_once (ev=0xcad450, location=0x373ce5dd40 "src/util/server.c:668") at ../tevent.c:533
#12 0x0000003b5dc03cbb in tevent_common_loop_wait (ev=0xcad450, location=0x373ce5dd40 "src/util/server.c:668") at ../tevent.c:637
#13 0x0000003b5dc08246 in std_event_loop_wait (ev=0xcad450, location=0x373ce5dd40 "src/util/server.c:668") at ../tevent_standard.c:140
#14 0x000000373ce42ab3 in server_loop (main_ctx=0xcae8a0) at src/util/server.c:668
#15 0x00000000004061d8 in main (argc=6, argv=<value optimized out>) at src/responder/nss/nsssrv.c:626

Reported also in FAF https://retrace.fedoraproject.org/faf/problems/bthash/?bth=2da3490d4d20bd6068014f04924d6810c950b9d4&bth=566f9ae1675a9eb18da56175d01fab9f17576335&bth=76077b06aa56f5c7068b2468a13dc337778dc506&bth=8295e8f1960e1847e50f98a9dac34b6a4346b291&bth=bce86a13b027c766cfd51bb6bf2879d3f1b79124&bth=d04e387ad16318f5039fc161f832c76ba4075af1&bth=da1e21227a202a56d19143e77d8940955dcddba5


Metadata Update from @lslebodn:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1487944

2 years ago

Cannot find 'nsssrv_netgroup.c'
inside src/responder/nss on latest 1.15.4

@amitkumar25nov, please, mind that the bug was reported against sssd-1.13.3-56.el6.

It's expected that a lot of changes happened between that version and our current versions.

Metadata Update from @fidencio:
- Issue set to the milestone: None

2 years ago

On (25/09/17 10:35), Amit Kumar wrote:

amitkumar25nov added a new comment to an issue you are following:
Cannot find 'nsssrv_netgroup.c' inside src/responder/nss on latest 1.15.4

Bug is in 1.13 and 1.14 branch.

LS

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.13.5

2 years ago

Name of the function in 1.13 and 1.15 is different but it looks similar.

Metadata Update from @lslebodn:
- Issue set to the milestone: None (was: SSSD 1.13.5)

2 years ago

Metadata Update from @jhrozek:
- Issue assigned to fidencio
- Issue set to the milestone: SSSD 1.16.1
- Issue tagged with: PR, bug

2 years ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata