* Re: udev ldap wait
2007-08-25 13:29 udev ldap wait Jan Engelhardt
@ 2007-08-25 14:44 ` Kay Sievers
2007-08-25 14:57 ` Jan Engelhardt
2007-08-25 15:51 ` Kay Sievers
2 siblings, 0 replies; 4+ messages in thread
From: Kay Sievers @ 2007-08-25 14:44 UTC (permalink / raw)
To: linux-hotplug
On 8/25/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> ttyS0 picked this up on boot.
>
> Welcome to Aurora SPARC Linux
> Press 'I' to enter interactive startup.
> Setting clock (localtime): Sat Aug 25 15:21:39 CEST 2007 [ OK ]
> Starting udev: udevd[370]: nss_ldap: failed to bind to LDAP server ldar
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.000.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)...
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)...
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 16 seconds)...
> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't conr
> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 32 seconds)...
>
> Well, that happens if you have 'bind_policy hard_open' in
> /etc/ldap.conf. Looks like a bad idea, I admit. But does udev really
> need to getpwfoo()?
Make sure, that all the system users and groups, used in udev rules,
exist in the local database, and that the local files are used before
you lookup any other directory service. It will not even try to use
the network, just like /etc/hosts can prevent dns lookups. System
users and groups should exist on the local machine for various
reasons, it's not only udev that has problems with it.
Kay
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: udev ldap wait
2007-08-25 13:29 udev ldap wait Jan Engelhardt
2007-08-25 14:44 ` Kay Sievers
@ 2007-08-25 14:57 ` Jan Engelhardt
2007-08-25 15:51 ` Kay Sievers
2 siblings, 0 replies; 4+ messages in thread
From: Jan Engelhardt @ 2007-08-25 14:57 UTC (permalink / raw)
To: linux-hotplug
On Aug 25 2007 16:44, Kay Sievers wrote:
>> Starting udev: udevd[370]: nss_ldap: failed to bind to LDAP server ldar
>> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.000.1: Can't conr
>> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)...
>>
>> Well, that happens if you have 'bind_policy hard_open' in
>> /etc/ldap.conf. Looks like a bad idea, I admit. But does udev really
>> need to getpwfoo()?
[ Minor correction: Fedora (duh) comes with a "bind_policy hard"
default conf. ]
>
>Make sure, that all the system users and groups, used in udev rules,
>exist in the local database,
>[...]
>System users and groups should exist on the local machine for various reasons,
>it's not only udev that has problems with it.
That is guaranteed. The LDAP slave just carries the users with portable UIDs,
which, as it stands, is limited to accounts for real-world people.
>and that the local files are used before
>you lookup any other directory service.
That is set too in nsswitch.conf ("passwd: files ldap")
>It will not even try to use
>the network, just like /etc/hosts can prevent dns lookups.
Still it does trigger nss_ldap. I have now forced 'bind_policy soft' (also a
SUSE default), and I can ignore the warnings.
Jan
--
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: udev ldap wait
2007-08-25 13:29 udev ldap wait Jan Engelhardt
2007-08-25 14:44 ` Kay Sievers
2007-08-25 14:57 ` Jan Engelhardt
@ 2007-08-25 15:51 ` Kay Sievers
2 siblings, 0 replies; 4+ messages in thread
From: Kay Sievers @ 2007-08-25 15:51 UTC (permalink / raw)
To: linux-hotplug
On Sat, 2007-08-25 at 16:57 +0200, Jan Engelhardt wrote:
> On Aug 25 2007 16:44, Kay Sievers wrote:
> >> Starting udev: udevd[370]: nss_ldap: failed to bind to LDAP server ldar
> >> udevd[370]: nss_ldap: failed to bind to LDAP server ldap://127.000.1: Can't conr
> >> udevd[370]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)...
> >>
> >> Well, that happens if you have 'bind_policy hard_open' in
> >> /etc/ldap.conf. Looks like a bad idea, I admit. But does udev really
> >> need to getpwfoo()?
> [ Minor correction: Fedora (duh) comes with a "bind_policy hard"
> default conf. ]
> >
> >Make sure, that all the system users and groups, used in udev rules,
> >exist in the local database,
> >[...]
> >System users and groups should exist on the local machine for various reasons,
> >it's not only udev that has problems with it.
>
> That is guaranteed. The LDAP slave just carries the users with portable UIDs,
> which, as it stands, is limited to accounts for real-world people.
>
> >and that the local files are used before
> >you lookup any other directory service.
>
> That is set too in nsswitch.conf ("passwd: files ldap")
>
> >It will not even try to use
> >the network, just like /etc/hosts can prevent dns lookups.
>
> Still it does trigger nss_ldap. I have now forced 'bind_policy soft' (also a
> SUSE default), and I can ignore the warnings.
Hmm, there must be an entry in a rules file, that doesn't exist in the
local db.
On the running system, can you put an invalid ldap IP addess in the
config, or disconnect the box from the network and do:
$ killall udevd
$ killall nscd
$ udevd -v
It shows here (after a long timeout):
udevd -v
[9575] parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file
[9575] parse_file: reading '/etc/udev/rules.d/10-local.rules' as rules file
[9575] lookup_group: error resolving group 'does-not-exist': Connection timed out
[9575] parse_file: reading '/etc/udev/rules.d/40-alsa.rules' as rules file
...
Kay
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 4+ messages in thread