#2288 sssd is crashing after several quick invokes of automount -m
Closed: Fixed None Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1079237

Description of problem:

I have a strange problem with sssd, ldap and autofs. I am using sssd and ldap
for authentication and automount. Our fileserver has 4 shares, while the 4. is
a new one. The mounting of the 4. share is not stabil and the systems have
problems to see the possible mounts. While still investigating this problem i
found a strange effect now describing here:

When i involve automount -m the output is sometimes hanging at this strange
share. But not everytime. When i re-involve automount -m very quick and very
often and it hangs again and than make several CTRL-C, than sssd is crashed.


Version-Release number of selected component (if applicable):
sssd-common-1.11.4-1.fc20.x86_64
sssd-client-1.11.4-1.fc20.i686
sssd-1.11.4-1.fc20.x86_64
sssd-ldap-1.11.4-1.fc20.x86_64
sssd-client-1.11.4-1.fc20.x86_64
autofs-5.0.7-40.fc20.x86_64

How reproducible:

See above


Steps to Reproduce:
1. See above
2.
3.

Actual results:

Making several CTRL-C at hanging automount -m output:

....
Mount point: /data

source(s):
Segmentation fault (core dumped)

And than:

[root@pxe-122 log]# systemctl status sssd
sssd.service - System Security Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled)
   Active: failed (Result: exit-code) since Fri 2014-03-21 09:28:09 CET; 5s ago
  Process: 488 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=0/SUCCESS)
 Main PID: 563 (code=exited, status=1/FAILURE)




Expected results:

Normal output of automount -m . No crash of sssd.


Additional info:

Mar 21 09:27:18 pxe-122 kernel: [ 1571.044469] traps: sssd_be[1164] general
protection ip:7fe295f1561a sp:7fffcbb365f8 error:0 in
libc-2.18.so[7fe295e8f000+1b4000]
Mar 21 09:27:18 pxe-122 kernel: traps: sssd_be[1164] general protection
ip:7fe295f1561a sp:7fffcbb365f8 error:0 in libc-2.18.so[7fe295e8f000+1b4000]
Mar 21 09:27:18 pxe-122 sssd[be[default]]: Starting up
Mar 21 09:27:19 pxe-122 automount[4745]: setautomntent: lookup(sss):
setautomntent: No such file or directory
Mar 21 09:27:21 pxe-122 kernel: [ 1574.493951] traps: sssd_be[4751] general
protection ip:7f8b58e2f61a sp:7fffd0bf44a8 error:0 in
libc-2.18.so[7f8b58da9000+1b4000]
Mar 21 09:27:21 pxe-122 kernel: traps: sssd_be[4751] general protection
ip:7f8b58e2f61a sp:7fffd0bf44a8 error:0 in libc-2.18.so[7f8b58da9000+1b4000]
Mar 21 09:27:23 pxe-122 sssd[be[default]]: Starting up
Mar 21 09:27:47 pxe-122 kernel: [ 1600.703958] traps: sssd_be[4764] general
protection ip:7f567182761a sp:7fff371c6ed8 error:0 in
libc-2.18.so[7f56717a1000+1b4000]
Mar 21 09:27:47 pxe-122 kernel: traps: sssd_be[4764] general protection
ip:7f567182761a sp:7fff371c6ed8 error:0 in libc-2.18.so[7f56717a1000+1b4000]
Mar 21 09:27:51 pxe-122 sssd[be[default]]: Starting up
Mar 21 09:28:09 pxe-122 kernel: [ 1622.336917] traps: sssd_be[4834] general
protection ip:7fcba70b861a sp:7fff04291f88 error:0 in
libc-2.18.so[7fcba7032000+1b4000]
Mar 21 09:28:09 pxe-122 kernel: traps: sssd_be[4834] general protection
ip:7fcba70b861a sp:7fff04291f88 error:0 in libc-2.18.so[7fcba7032000+1b4000]
Mar 21 09:28:09 pxe-122 kernel: [ 1622.338391] automount[4840]: segfault at 0
ip 00007fd58451791f sp 00007fffa34b86b0 error 4 in
libsss_autofs.so[7fd584515000+4000]
Mar 21 09:28:09 pxe-122 sssd[autofs]: Shutting down
Mar 21 09:28:09 pxe-122 kernel: automount[4840]: segfault at 0 ip
00007fd58451791f sp 00007fffa34b86b0 error 4 in
libsss_autofs.so[7fd584515000+4000]
Mar 21 09:28:09 pxe-122 sssd[pam]: Shutting down
Mar 21 09:28:09 pxe-122 sssd[nss]: Shutting down
Mar 21 09:28:09 pxe-122 systemd: sssd.service: main process exited,
code=exited, status=1/FAILURE
Mar 21 09:28:09 pxe-122 systemd: Unit sssd.service entered failed state.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
owner: somebody => lslebodn
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.12 beta

2 years ago

Login to comment on this ticket.

Metadata