Bug 11043 - winbind does not work without IPv4
Summary: winbind does not work without IPv4
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.1.11
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-09 21:36 UTC by Steinar H. Gunderson (dead mail address)
Modified: 2015-01-14 22:40 UTC (History)
0 users

See Also:


Attachments
/var/log/samba, newly cleared before starting samba and winbind (65.64 KB, application/gzip)
2015-01-09 22:02 UTC, Steinar H. Gunderson (dead mail address)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steinar H. Gunderson (dead mail address) 2015-01-09 21:36:53 UTC
Hi,

I've got an IPv6-only Linux machine (Debian wheezy, with Samba 4.1 from backports). It turns out that while it can use Samba itself just fine, winbind not so much. Any operation I do (e.g. wbinfo -u) yields WBC_ERR_DOMAIN_NOT_FOUND.

Adding a working IPv4 address, e.g. by running dhclient eth0, pretty much immediately makes winbind work.

As far as I understand, AD is supposed to work fine in a singlestacked IPv6 world, and I haven't seen any problems running AD over IPv6-only in Windows 7 (against the same AD PDC), so I suppose this is a client issue.
Comment 1 Jeremy Allison 2015-01-09 21:55:55 UTC
Can you run winbindd and wbinfo with debug 10 and get some logs for us to look at please ?
Comment 2 Steinar H. Gunderson (dead mail address) 2015-01-09 22:02:51 UTC
Created attachment 10609 [details]
/var/log/samba, newly cleared before starting samba and winbind
Comment 3 Steinar H. Gunderson (dead mail address) 2015-01-09 22:03:04 UTC
Of course. Attached. I tried running (with some typos inbetween):

root@nemesis:~# wbinfo -u
root@nemesis:~# wbinfo -u
root@nemesis:~# wbinfo -i sesse
failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND
Could not get info for user sesse

I don't know, unfortunately, how to run wbinfo itself with debug 10. Could you enlighten me?
Comment 4 Jeremy Allison 2015-01-09 23:57:07 UTC
Just use:

wbinfo -d10 <other args>
Comment 5 Steinar H. Gunderson (dead mail address) 2015-01-09 23:59:03 UTC
Nope, that gives me “Invalid option”.
Comment 6 Jeremy Allison 2015-01-10 00:02:04 UTC
Oh, my mistake - that should work globally in all Samba tools but I guess it got hijacked here for the "domain" option.

Try setting:

debug level = 10

in the smb.conf and re-doing the wbinfo.
Comment 7 Steinar H. Gunderson (dead mail address) 2015-01-10 00:04:48 UTC
Nope, wbinfo does not output any debug info even with debug level = 10. It doesn't even read smb.conf, from what I can gather from an strace.
Comment 8 Steinar H. Gunderson (dead mail address) 2015-01-14 22:22:25 UTC
Hm. I started debugging this, and now I'm suddenly unable to reproduce it. I can reboot and do operations just fine with IPv6-only. A bunch of things have changed, so it's hard to say what happened, but I'm closing this for now.
Comment 9 Jeremy Allison 2015-01-14 22:32:47 UTC
Great ! Did anything in winbindd change, or was it only other components ?
Comment 10 Steinar H. Gunderson (dead mail address) 2015-01-14 22:40:49 UTC
I didn't change any code short of applying the patch from #11049, which seems unrelated. So I believe the difference must either be a) luck, or b) configuration/environment/LDAP contents changes (of which there were quite a few).