So glad I took the time to report this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
Upstream seems silent; bug remains in NEW state and no follow-up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubuntu 18.04
To manage
Sure.
Let's see what upstream comes up with after the last round of comments
there. If it's a patch that can be backported to the bionic version, we
might go that route. If not, then adding the network-online target it
is.
--
You received this bug notification because you are a member of Ubuntu
Actually, no, that doesn't work for me. Was expecting it would given the
comments on the samba bug, but, well, no. It *does* work to send HUP
once booted:
rene@t5500:~$ ping WD-NETCENTER
ping: WD-NETCENTER: Name or service not known
rene@t5500:~$ sudo kill -HUP $(systemctl show winbind -p MainPID
As a workaround, could you try creating this file: /usr/lib/networkd-
dispatcher/routable.d/10-winbind
with these contents:
#!/bin/sh
pid=$(systemctl show winbind -p MainPID --value)
if [ "$pid" -ne "0" ]; then
kill -HUP $pid
fi
Then make it executable: sudo chmod +x
/usr/lib/networkd-dis
As to the reply you got on
https://bugzilla.samba.org/show_bug.cgi?id=13607, I can deny a "net
cache flush" doing anything to get WINS name resolving going for me when
booted with the original service file:
rene@t5500:~$ ping WD-NETCENTER
ping: WD-NETCENTER: Name or service not known
rene@t5500:~$
** Bug watch added: Samba Bugzilla #13607
https://bugzilla.samba.org/show_bug.cgi?id=13607
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=13607
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs
Ah, and that's only in the "no wins specified" case, otherwise it
recovers just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Mint 19 / Ubu
basically if the interface is available when winbind starts, winbind
keeps working if it's brought down and up again. But if winbind starts
when the interface isn't available, then it won't recover without a
restart. That's my finding so far.
--
You received this bug notification because you are
> This is to say that I do not in fact have a WINS server specified; that
> judging by the logs
> my winbind is relying on broadcasts, and bombing out in that case if started
> before
> network-online.target.
Ok, reproduced. When there is no wins server specified, somehow winbind
doesn't "detect
** Attachment added: "winbind.service-working"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185183/+files/winbind.service-working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Thanks much for checking. I see; I was expecting this to be an
"immediately obvious" sort of thing to someone with unlike me an actual
clue about samba/winbind, but I have with the above guidance nos
supplied more information.
Specifically, it would appear that your explicitly mentioned "wins
serv
** Attachment added: "log.winbindd-working"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185181/+files/log.winbindd-working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "winbind.service-nonworking"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185184/+files/winbind.service-nonworking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "log.winbindd-nonworking"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185182/+files/log.winbindd-nonworking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Oh, and the mentioned vanilla smb.conf...
** Attachment added: "smb.conf"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+attachment/5185185/+files/smb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
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)
Just to add: the issue's the same and fully constant on an Intel Xeon
E5606 @2,13GHz with 8GiB running Mint 19 Cinnamon 64-bit, and an Intel
Core 2 Duo E8400 @ 3GHz withj 4GiB running Mint 19 Xfce 64-bit.
That is... it's not a subtle race and I assume anyone will see this if
installing only "winbi
Yes, the network itself comes up fine. "Does not work" simply means that
NetBIOS name resolution is unavailable even after it does; that e.g.
"ping NAS" for "NAS" the NetBIOS name of my, well, NAS, tells me the
name cannot be resolved.
There would not appear to be relevant logs nor configuration f
Thanks for filing this bug in Ubuntu.
What do you mean by "does not work", exactly?
Doesn't the network come up eventually? Or is this a desktop machine
where the network is wireless and only available after someone logs in?
Please show exactly what is not working, your configuration files, and
20 matches
Mail list logo
