Bug 7647 - ERROR: Could not determine network interfaces
ERROR: Could not determine network interfaces
Status: NEW
Product: Samba 3.5
Classification: Unclassified
Component: Winbind
3.5.4
Other Linux
: P3 normal
: ---
Assigned To: Michael Adam
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-25 10:30 UTC by David Woodhouse
Modified: 2010-08-25 17:18 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Woodhouse 2010-08-25 10:30:15 UTC
Sometimes after a reboot, I find that winbindd isn't running. I find this in the logs:

[2010/08/25 16:18:50.710516,  0] lib/interface.c:519(load_interfaces)
  ERROR: Could not determine network interfaces, you must use a interfaces config line

It looks like winbindd aborts after this... and then half a second later when the network does come up, authentication doesn't work.

Winbindd should have opened a netlink socket to listen for notifications from the kernel about network configuration changes, and been patient.

(The only interface it can use to talk to the corporate network is vpn0 anyway, which it tends to ignore for some reason.)
Comment 1 Jeremy Allison 2010-08-25 12:36:52 UTC
"Winbindd should have opened a netlink socket to listen for notifications from
the kernel about network configuration changes, and been patient."

This would make winbindd Linux-only. I know OpenSolaris is dying, but it's not dead yet... :-).

I'm happy with feature specific code in winbindd, but it has to be #defined with an "#if defined(HAVE_NETLINK_SOCKET_INTERFACE)" etc.

Jeremy.
Comment 2 Volker Lendecke 2010-08-25 12:43:44 UTC
We could use dbus properly #ifdef'ed, right? Isn't that a *bit* more generic?

Volker
Comment 3 David Woodhouse 2010-08-25 17:18:44 UTC
I'll settle for 'should have been more patient'. I don't really mind how it happens, as long as winbindd hasn't aborted by the time the network comes up.

And ideally, if offline, winbindd would try to reconnect to the domain *immediately* when it gets notification that a new network device has come up.