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
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.
Is 127.0.0.1 not up yet ? Having no interfaces might make us a little flakey, don't we need to have at least 127.0.0.1 and why does connman need to be running to get loopback up ?
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.
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 127.0.0.1 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 127.0.0.1 is up and we still don't start then that's a bug I can fix.
Is 127.0.0.1 up when winbindd aborts ?