PDA

View Full Version : SLES11SP3: winbind crash & strange behavior with AD accounts



TL
25-Feb-2015, 09:55
Hi all,

we've running some SLES11SP3-64 servers and using ActiveDirectory accounts for ssh logins.

Everything works fine with SP1, but after upgrading to SP2/3 we have the following effects:

1) winbind crashes when an users tries to login and his account is locked:


Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.808446, 0] lib/fault.c:47(fault_report)
Feb 25 08:57:26 v979l001 winbindd[4469]: ================================================== =============
Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.808735, 0] lib/fault.c:48(fault_report)
Feb 25 08:57:26 v979l001 winbindd[4469]: INTERNAL ERROR: Signal 11 in pid 4469 (3.6.3-0.56.1-3368-SUSE-CODE11-x86_64)
Feb 25 08:57:26 v979l001 winbindd[4469]: Please read the Trouble-Shooting section of the Samba3-HOWTO
Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.808796, 0] lib/fault.c:50(fault_report)
Feb 25 08:57:26 v979l001 winbindd[4469]:
Feb 25 08:57:26 v979l001 winbindd[4469]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.808848, 0] lib/fault.c:51(fault_report)
Feb 25 08:57:26 v979l001 winbindd[4469]: ================================================== =============
Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.808884, 0] lib/util.c:1117(smb_panic)
Feb 25 08:57:26 v979l001 winbindd[4469]: PANIC (pid 4469): internal error
Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.810642, 0] lib/util.c:1221(log_stack_trace)
Feb 25 08:57:26 v979l001 winbindd[4469]: BACKTRACE: 17 stack frames:
Feb 25 08:57:26 v979l001 winbindd[4469]: #0 /usr/sbin/winbindd(log_stack_trace+0x1a) [0x7f35ebfd791a]
Feb 25 08:57:26 v979l001 winbindd[4469]: #1 /usr/sbin/winbindd(smb_panic+0x2b) [0x7f35ebfd79eb]
Feb 25 08:57:26 v979l001 winbindd[4469]: #2 /usr/sbin/winbindd(+0x1af210) [0x7f35ebfc8210]
Feb 25 08:57:26 v979l001 winbindd[4469]: #3 /lib64/libc.so.6(+0x32920) [0x7f35e8e81920]
Feb 25 08:57:26 v979l001 winbindd[4469]: #4 /usr/sbin/winbindd(netlogon_creds_client_authenticator+0xd) [0x7f35ec0d58bd]
Feb 25 08:57:26 v979l001 winbindd[4469]: #5 /usr/sbin/winbindd(rpccli_netlogon_sam_network_logon+0x18c) [0x7f35ec33b1ac]
Feb 25 08:57:26 v979l001 winbindd[4469]: #6 /usr/sbin/winbindd(+0xee9fb) [0x7f35ebf079fb]
Feb 25 08:57:26 v979l001 winbindd[4469]: #7 /usr/sbin/winbindd(winbindd_dual_pam_auth+0x2f7) [0x7f35ebf09ec7]
Feb 25 08:57:26 v979l001 winbindd[4469]: #8 /usr/sbin/winbindd(+0x107c22) [0x7f35ebf20c22]
Feb 25 08:57:26 v979l001 winbindd[4469]: #9 /usr/sbin/winbindd(+0x108745) [0x7f35ebf21745]
Feb 25 08:57:26 v979l001 winbindd[4469]: #10 /usr/lib64/libtevent.so.0(tevent_common_loop_immediate+0xea) [0x7f35e98013fa]
Feb 25 08:57:26 v979l001 winbindd[4469]: #11 /usr/sbin/winbindd(run_events_poll+0x3b) [0x7f35ebfe6a9b]
Feb 25 08:57:26 v979l001 winbindd[4469]: #12 /usr/sbin/winbindd(+0x1ce1d2) [0x7f35ebfe71d2]
Feb 25 08:57:26 v979l001 winbindd[4469]: #13 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x90) [0x7f35e9800190]
Feb 25 08:57:26 v979l001 winbindd[4469]: #14 /usr/sbin/winbindd(main+0x7f3) [0x7f35ebef90e3]
Feb 25 08:57:26 v979l001 winbindd[4469]: #15 /lib64/libc.so.6(__libc_start_main+0xe6) [0x7f35e8e6dc36]
Feb 25 08:57:26 v979l001 winbindd[4469]: #16 /usr/sbin/winbindd(+0xdd689) [0x7f35ebef6689]
Feb 25 08:57:26 v979l001 winbindd[4469]: [2015/02/25 08:57:26.821478, 0] lib/fault.c:372(dump_core)
Feb 25 08:57:26 v979l001 winbindd[4469]: dumping core in /var/log/samba/cores/winbindd

2) Before upgrading to SP2/3 the ssh login prompt shows some infos like "Your password will expire in x days", "You need to change your password now" or "Your account has been locked. Please contact your system administrator". Now it shows absolutly nothing then the normal password prompt again and again.

Any hints for this?

Thank you,
Thomas

Automatic reply
01-Mar-2015, 14:30
TL,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com