Bug 7793 - winbindd aborts when no interfaces found; local cached winbind login fails
Summary: winbindd aborts when no interfaces found; local cached winbind login fails
Status: NEW
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 3.5.6
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: Michael Adam
QA Contact: Samba QA Contact
Depends on:
Reported: 2010-11-12 04:07 UTC by David Woodhouse
Modified: 2010-12-22 14:35 UTC (History)
1 user (show)

See Also:

Samba / Winbindd log files (10.83 KB, application/x-compressed)
2010-12-22 05:39 UTC, Geoffroy
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Woodhouse 2010-11-12 04:07:20 UTC
In an 'Enterprise' build of MeeGo we're using winbind for authentication, with cached logins so that it works offline. 

Sometimes we find that we cannot log in, because winbindd aborts at startup:

[2010/11/12 13:44:59.963128,  0] lib/interface.c:519(load_interfaces)
  ERROR: Could not determine network interfaces, you must use a interfaces
config line

This presumably happens when connman is slow to bring up the network interfaces.

I could try to deal with that race condition, but I don't *want* to — if I've enabled cached logins, winbindd needs to work even *without* network interfaces.
Comment 1 Jeremy Allison 2010-11-16 18:37:11 UTC
Is not up yet ? Having no interfaces might make us a little flakey, don't we need to have at least and why does connman need to be running to get loopback up ?


Comment 2 Geoffroy 2010-12-22 05:39:58 UTC
Created attachment 6157 [details]
Samba / Winbindd log files

I've run across this issue again and captured some debug output from winbind ('-d 9' option). I hope this can help you understand the issue and resolve it.
Comment 3 Jeremy Allison 2010-12-22 14:35:05 UTC
No, dumping log files on me when I didn't ask for them isn't helpful I'm afraid. All it's telling me is no network interface is up, not even loopback as far as I can see. 

So, what I need to know is - is up when winbindd starts ? If not, I don't think it's reasonable for winbindd to startup and just wait for a network interface as loopback is used for many things like IPC. If is up and we still don't start then that's a bug I can fix.

Is up when winbindd aborts ?