Another LDAP weirdness we're seeing.

Another LDAP weirdness we're seeing.

[Mike Marion]

Trying to track down if it's in the client at all, but related to my
last mail.. if we start the daemon with --ghost, sometimes the hosts are
failing to start all the children of /- (or even /- itself). 

The logs I've gotten when it failed were:
Feb  6 13:32:09 k8-032 automount[2243]: starting automounter version
4.1.4, path = /-, maptype = ldap, mapname =
automountmapname=auto.projects,ou=automountMaps,ou=sandiego,ou=qct,dc=qualcomm,dc=com
Feb  6 13:32:11 k8-032 automount[2243]: lookup(ldap): LDAP query failed:
No such object
Feb  6 13:32:11 k8-032 automount[2243]: failed to load map exiting

Trying to start it by running the autofs init script again by hand
shortly after this, it works fine.  Is there some point in the initial
read of the maps that has a timeout?  We're tying to narrow down if it's
the client timing out (ldap servers not responding fast enough) or if
the servers are actually returning a bad value (or the above 'no such
object') which, obviously, shouldn't be happening.

We're still doing further testing, just wondering if anyone's seen
anything similar that might help us fix it faster... didn't see anything
obvious in the mails I have in my box.

-- 
Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com
Drew: "Dear pizza, I do not care, or give a wit, that you are one day old.  
I think you are beautiful, even when you are cold."  -- Drew Cary Show.

Re: Another LDAP weirdness we're seeing.

[Jeff Moyer]

==> On Tue, 6 Feb 2007 14:53:58 -0800, Mike Marion <mmarion@qualcomm.com> said:

Mike> Trying to track down if it's in the client at all, but related to my
Mike> last mail.. if we start the daemon with --ghost, sometimes the hosts are
Mike> failing to start all the children of /- (or even /- itself). 

Mike> The logs I've gotten when it failed were:
Mike> Feb  6 13:32:09 k8-032 automount[2243]: starting automounter version
Mike> 4.1.4, path = /-, maptype = ldap, mapname =
Mike> automountmapname=auto.projects,ou=automountMaps,ou=sandiego,ou=qct,dc=qualcomm,dc=com
Mike> Feb  6 13:32:11 k8-032 automount[2243]: lookup(ldap): LDAP query failed:
Mike> No such object
Mike> Feb  6 13:32:11 k8-032 automount[2243]: failed to load map exiting

Mike> Trying to start it by running the autofs init script again by hand
Mike> shortly after this, it works fine.  Is there some point in the initial
Mike> read of the maps that has a timeout?  We're tying to narrow down if it's
Mike> the client timing out (ldap servers not responding fast enough) or if
Mike> the servers are actually returning a bad value (or the above 'no such
Mike> object') which, obviously, shouldn't be happening.

Post full debug logs and maps.

-Jeff