[Samba] winbind pam trouble

Rowland penny rpenny at samba.org
Tue Apr 12 12:28:00 UTC 2016


On 12/04/16 13:10, Rowland penny wrote:
> On 12/04/16 12:55, lists wrote:
>> On 12-4-2016 10:24, lists wrote:
>>
>> From log.wb-DOMAIN:
>>>
>>> [2016/04/11 20:39:01.330173,  0] ../lib/util/fault.c:79(fault_report)
>>>   INTERNAL ERROR: Signal 11 in pid 4899 (4.2.9-SerNet-Debian-8.wheezy)
>>>   Please read the Trouble-Shooting section of the Samba HOWTO
>>> [2016/04/11 20:39:01.330199,  0] ../lib/util/fault.c:81(fault_report)
>>> ===============================================================
>>> [2016/04/11 20:39:01.330217,  0] 
>>> ../source3/lib/util.c:788(smb_panic_s3)
>>>   PANIC (pid 4899): internal error
>>> [2016/04/11 20:39:01.330733,  0]
>>> ../source3/lib/util.c:899(log_stack_trace)
>>>   BACKTRACE: 29 stack frames:
>>
>> I am trying to trigger the above panic:
>>
>> wbinfo -u (lists all users)
>> wbinfo -g (lists all groups)
>> wbinfo -t (checking trust succeeds)
>> wbinfo --list-status (all three reported online)
>> wbinfo --authenticate=user%password (authentication succeeds)
>> wbinfo --dc-info=DOMAIN (lists only ONE of our three DCs, but no panic)
>>
>> The above panic happened yesterday while nsswitch.conf contained
>> > passwd:         compat winbind
>> > group:          compat winbind
>> > shadow:         compat winbind
>>
>> Currently nsswitch.conf has
>> > passwd: compat sss
>> > group: compat sss
>> > shadow: compat sss
>> and winbind is running without crashes.
>>
>> Since this is production, I'd rather not put back winbind in 
>> nsswitch.conf, because the winbind panic will break fileserving from 
>> this member server.
>>
>> Any ideas how to approach this..?
>>
>> BTW: wheezy 7.10, x64, sernet-samba 4.2.9-8.
>>
>> MJ
>>
>
> I never alter 'shadow' and winbind doesn't crash for me i.e. relevant 
> part of /etc/nsswitch.conf:
>
> passwd:         compat winbind
> group:          compat winbind
> shadow:         compat
>
> wheezy 7.10, x64, sernet-samba 4.2.4-7
>
> I will upgrade sernet samba and see what happens.
>
> Rowland
>
>

OK, now using sernet-samba 4.2.9 and no difference, everything still 
works, I can login via ssh to another machine and I can login via ssh 
from another machine.

Rowland




More information about the samba mailing list