[Samba] winbind : suspend nightmare

[Jeremy Allison]

On Mon, Oct 21, 2019 at 10:07:20AM +0200, Prunk Dump via samba wrote:
> 
> I don't know if winbind "officially" support suspending. Currently I
> have written a systemd hook that kill winbind before suspend and
> restarting it after.

It hasn't been tested in that mode as far as I know.

Congratulations, you're the first ! :-).

> 07:44:43  connection_ok: Connection to fichdc01.samdom.com for domain
> SAMDOM is not connected
> 07:44:43  Successfully contacted LDAP server 172.16.0.30
> 07:44:43  get_dc_list: preferred server list: "fichdc01.samdom.com, *"
> 07:44:43  Connecting to 172.16.0.30 at port 445
> 07:44:43  ldb_wrap open of secrets.ldb
> 07:44:43  Connecting to 172.16.0.30 at port 135
> 07:44:43  Connecting to 172.16.0.30 at port 49153
> 07:44:43  Connecting to 172.16.0.30 at port 135
> 07:44:43  Connecting to 172.16.0.30 at port 49153
> 07:44:43  Connecting to 172.16.0.30 at port 135
> 07:44:43  Connecting to 172.16.0.30 at port 49152
> 07:44:45  ads: fetch sequence_number for SAMDOM
> 07:44:45  get_dc_list: preferred server list: "fichdc01.samdom.com, *"
> 07:44:45  Successfully contacted LDAP server 172.16.0.30
> 07:44:45  Connected to LDAP server fichdc01.samdom.com
> 07:46:40  connection_ok: Connection to fichdc01.samdom.com for domain
> SAMDOM is not connected
> 07:46:40  cldap_multi_netlogon_send: cldap_socket_init failed for
> ipv4:172.16.0.30:389  error NT_STATUS_NETWORK_UNREACHABLE

OK, the above line is the problem. Why does that
happen if above we have:

07:44:45  Successfully contacted LDAP server 172.16.0.30

cldap_multi_netlogon_send() does a UDP cldap ping
to the server (172.16.0.30). Getting NT_STATUS_NETWORK_UNREACHABLE
looks like the network interface isn't up yet.

Can you start winbind under strace in this case so we
can see what syscalls are being done and exactly how they're
failing ?

Thanks,

Jeremy.