I'm trying to check why winbind won't recover from the network being
down, so I setup a lxd container where I installed just winbind and the
nss module.
My /etc/nsswitch.conf reads:
hosts: files wins dns
(I would have ordinarily put dns before wins, but ok, let's try to
reproduce this)
smb.conf has:
[global]
...
wins server = 10.10.222.254
That IP is another samba server I have.
I then disabled dhcp on eth0, and rebooted the container. It came back
up with no IP on eth0. winbind was running, and name resolution via wins
was obviously not working. I logged in using "lxc exec <containername>
bash" instead of ssh).
I then just ran "dhclient eth0", and retried the name resolution (ping
-c <netbiosname> was my test), and it worked right away. So it was able
to use the newly functional interface.
I didn't see anything out of the ordinary in winbind's logs.
I'll try again with a vm, which should be a bit slower than a lxd
container. And maybe also try without a network card at all, then add
one, and see if winbind needs to be restarted.
In the meantime, can you perhaps grab me some winbind logs during a
machine boot showing the problem? Maybe add "debug level = 3" or 5 to
smb.conf as well.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
