[Samba] winbindd crashing -- how to auto-heal?

Rowland Penny rpenny at samba.org
Mon Sep 3 09:16:32 UTC 2018


On Sun, 2 Sep 2018 22:37:05 -0400
Jamie Jackson via samba <samba at lists.samba.org> wrote:

> Thanks for the workaround, Luca. I might end up going with:
> 
> #!/bin/bash
> getent group | grep -q 'Domain Users' && exit 0
> echo "restarting winbind"
> sudo systemctl restart winbind
> 
> 
> Rowland, it crashed again. Here's some info. Please let me know if I
> should provide more:
> https://gist.github.com/jamiejackson/8aa60fb0ac1f407ba73776aaaeaa542f
> 

The last few lines of the log are these:

[2018/09/01 23:19:27.748555,  3, pid=9795] ../source3/winbindd/winbindd_msrpc.c:244(msrpc_name_to_sid)
  msrpc_name_to_sid: name=REDACTED\ROOT
[2018/09/01 23:19:27.748585,  3, pid=9795] ../source3/winbindd/winbindd_msrpc.c:258(msrpc_name_to_sid)
  name_to_sid [rpc] REDACTED\ROOT for domain REDACTED
[2018/09/01 23:20:28.475336,  0, pid=9795] ../source3/winbindd/winbindd.c:281(winbindd_sig_term_handler)
  Got sig[15] terminate (is_parent=0)

It looks like you ran you script/commands on Sun Sep  2 21:35:39 EDT
2018

To my eye, there is nothing really wrong, there certainly isn't any
evidence of a crash, the only evidence that I can see is that winbind
has exited.

So I went back to the info you posted earlier, at that time I
concentrated on the smb.conf, this time I looked a lot more closely at
this:

$ ps -aux | grep '\(samba\|smb\|winbind\)'
root     12600  0.0  0.0 399284  2324 ?        Ss   Aug31   0:16 /usr/sbin/winbindd --foreground --no-process-group
root     12602  0.0  0.0 424328  5948 ?        S    Aug31   0:01 /usr/sbin/winbindd --foreground --no-process-group
root     12857  0.0  0.0 406020   964 ?        S    Aug31   0:03 /usr/sbin/winbindd --foreground --no-process-group
root     12858  0.0  0.0 399144  1416 ?        S    Aug31   0:00 /usr/sbin/winbindd --foreground --no-process-group
root     12859  0.0  0.0 399144  1504 ?        S    Aug31   0:00  /usr/sbin/winbindd --foreground --no-process-group

If I run the same command on a Unix domain member, I get this:

root      2231  0.0  0.1 398220 17912 ?        Ss   Aug29   0:03 /usr/sbin/winbindd
root      2593  0.0  0.1 455004 20328 ?        S    Aug29   0:10 /usr/sbin/winbindd
root      2630  0.0  0.0 307728 15336 ?        Ss   Aug29   0:00 /usr/sbin/smbd -D
root      2683  0.0  0.0 296524  4516 ?        S    Aug29   0:00 /usr/sbin/smbd -D
root      2684  0.0  0.0 296524  4516 ?        S    Aug29   0:00 /usr/sbin/smbd -D
root      2730  0.0  0.0 265088  9696 ?        S    Aug29   0:00 /usr/sbin/winbindd
root      2745  0.0  0.0 265220  9560 ?        S    Aug29   0:00 /usr/sbin/winbindd
root      2746  0.0  0.1 403600 16412 ?        S    Aug29   0:01 /usr/sbin/winbindd

So, from that, can I ask these questions:

Why isn't 'smbd' running ?
Is 'nmbd' running ?
Why aren't you running 'winbind' as a daemon ?
Why do feel you don't need a process group for winbind ?

Rowland



More information about the samba mailing list