Re: [autofs] autofs5: unable to locate ldap master map
Sorry for this late reply, I was caught by work and hollidays. Ian Kent wrote: Your example above won't work. Have you actually read the INSTALL file which tells you what options autofs configure understands? I didn't tested it, and I indeed meant --with-confdir. I just wanted to express that it was quite weird to have to ressort to explicit option to stick to standards. At least it's configurable and these defaults can be changed fairly easily. Perhaps I had this sort of issue in mind when I did it and clearly you would like to make use of it until the climate is right for it to change. Personally, I'd rather take advantage of a new major version release for this kind of changes, where people expect non-transparent changes, and the fact than most of these directives didn't existed previously, rather than some later 5.0 - 5.1 transition. Fact is that for configuration to be at all usefull autofs has to understand it and cooperate with it. The only reason I added these configure options was in an effort to make it easier for those who wish to use different locations to customise them. If it doesn't meet with your approval then I'm sorry but I like it and it works well for me. And I don't see any patch submissions from you for discussion so I guess you'll just have to live with it. I don't see the point of investing time to produce patches that will be rejected, so I usually try to reach agreement before. Now, if all you want is a patch, I can easily produce one, once we agree on the following points: - is is desirable to have distinct directories for automount configuration and master map location (aka --with-confdir and --with-mapdir switches) ? I think so. Certainly the map directory is different on different distributions so that's definitely a good thing to have. And your point above would imply having the configuration directory configurable is good as well. Distributions enforce constraints on distribution-specific items, such as init scripts for instance. I don't think neither map or autofs daemon configuration can get considered as distribution specific. But you actually answer to my question n°3 here, aka should they be configurable ? My question n°1 was should they be distinct ? What would be wrong having maps _and_ autofs configuration in the same directory ? - if they differ does, autofs_ldap_auth.conf belongs to automount configuration or master map location ? Good point. But I would refer back to my original reason for the division. Perhaps as time passes and people become familiar with the change we can move the program configuration file to the map directory without to much confusion. - is is really desirable to make those directories configurable, whereas a fixed /etc/autofs would be perfectly fine ? I think so for the reasons I pointed out above. I don't want to have to go and modify the source code if it's decided to change this in the future. The configure script is much easier to change if we need to change these defaults. I was not discussing changing code or configure script issue, but the use of configure script specific switches for those directories, instead of just standard sysconfdir variable, that is already configurable. - do you want initscript-related corresponding options, such as --with-initscriptdir and --with-initscriptconfigdir ? Don't think that is needed. I think the main issue being discussed here is the location of the program configuration only. Hopefully the rest is ok. Agreed. -- Guillaume Rousse Projet Estime, INRIA Domaine de Voluceau Rocquencourt - B.P. 105 78153 Le Chesnay Cedex - France ___ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
[autofs] AutoFS problem with OpenLDAP server
Greetings all- I have a strange problem with AutoFS under Fedora Core 5. Can't seem to automount via ldap the way I should be able to. If I have: automount: files ldap in /etc/nsswitch.conf, and have: /projects ldap://ldapserver.domain.com/nisMapName=auto.projects,dc=domain,dc=com in /etc/auto.master, everything works. However, I don't want my clients to be configured this way because I have two redundant OpenLDAP servers and would like AutoFS to automatically try a second LDAP server if the first one goes down. So I put this in /etc/nsswitch.conf: automount: ldap and tried to restart AutoFS, and got the error: [EMAIL PROTECTED] default]# /etc/init.d/autofs start Starting automount: No Mountpoints Defined [ OK ] [EMAIL PROTECTED] default]# But there ARE automount maps in OpenLDAP, as the first method works. If I try the automount command manually, I get this in the logs: Jul 26 13:06:34 sunbright automount[22965]: starting automounter version 4.1.4-19, path = /projects, maptype = ldap, mapname = nisMapName=auto.projects,dc=domain,dc=com Jul 26 13:06:34 starbright automount[22965]: lookup(ldap): couldn't bind to default server The server does accept anonymous lookups. I even watched the traffic (via tcpdump) from the client to the server and there was no traffic at all! Seems the client isn't even trying to contact any of my LDAP servers. Does anyone have any ideas as to what's happening? Like I said I would like the automounter to try each of my 3 servers in order listed in /etc/ldap.conf, so manually specifying one server in /etc/auto.master isn't very appealing... Thanks in advance for any insight! ciao, erich ___ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
Re: [autofs] AutoFS problem with OpenLDAP server
OK, I figured out that AutoFS looks at /etc/openldap/ldap.conf and NOT
/etc/ldap.conf. I'm one step closer. However, when I copy my
ldap.conf over to /etc/openldap/ldap.conf, and do a /etc/init.d/autofs
start, it still gives me the:
Starting automount: No Mountpoints Defined
Error at the command line. I *DO* see traffic to the Openldap server
this time though, and in the OpenLDAP logs I see:
ber_scanf fmt ({mm}) ber:
ber_scanf fmt ({mm}) ber:
filter: ((?=undefined)(?=undefined))
ber_scanf fmt ({M}}) ber:
attrs: automountMapName automountInformation
== limits_get: conn=10642 op=6 dn=[anonymous]
= bdb_search
bdb_dn2entry(dc=domain,dc=com)
So it looks like the automounter is searching for automountMapName and
automountInformation. Which is bad, because my maps are in the form
of nisMapName and nisMapEntry. Does anyone know if there is an easy
way to tell the automounter to look for the other attributes? Or do I
have to try to set up some kind of aliasing on my OpenLDAP server?
Thanks for your patience with me!
ciao, erich
Erich Weiler wrote:
Greetings all-
I have a strange problem with AutoFS under Fedora Core 5. Can't seem to
automount via ldap the way I should be able to. If I have:
automount: files ldap
in /etc/nsswitch.conf, and have:
/projects
ldap://ldapserver.domain.com/nisMapName=auto.projects,dc=domain,dc=com
in /etc/auto.master, everything works. However, I don't want my clients
to be configured this way because I have two redundant OpenLDAP servers
and would like AutoFS to automatically try a second LDAP server if the
first one goes down. So I put this in /etc/nsswitch.conf:
automount: ldap
and tried to restart AutoFS, and got the error:
[EMAIL PROTECTED] default]# /etc/init.d/autofs start
Starting automount: No Mountpoints Defined [ OK ]
[EMAIL PROTECTED] default]#
But there ARE automount maps in OpenLDAP, as the first method works. If
I try the automount command manually, I get this in the logs:
Jul 26 13:06:34 sunbright automount[22965]: starting automounter version
4.1.4-19, path = /projects, maptype = ldap, mapname =
nisMapName=auto.projects,dc=domain,dc=com
Jul 26 13:06:34 starbright automount[22965]: lookup(ldap): couldn't bind
to default server
The server does accept anonymous lookups. I even watched the traffic
(via tcpdump) from the client to the server and there was no traffic at
all! Seems the client isn't even trying to contact any of my LDAP servers.
Does anyone have any ideas as to what's happening? Like I said I would
like the automounter to try each of my 3 servers in order listed in
/etc/ldap.conf, so manually specifying one server in /etc/auto.master
isn't very appealing...
Thanks in advance for any insight!
ciao, erich
--
===
Erich Weiler
UNIX Systems Administrator
School of Engineering
University of California Santa Cruz
[EMAIL PROTECTED]
===
___
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
Re: [autofs] AutoFS problem with OpenLDAP server
== Regarding Re: [autofs] AutoFS problem with OpenLDAP server; Erich Weiler
[EMAIL PROTECTED] adds:
weiler OK, I figured out that AutoFS looks at /etc/openldap/ldap.conf and
NOT
weiler /etc/ldap.conf. I'm one step closer. However, when I copy my
weiler ldap.conf over to /etc/openldap/ldap.conf, and do a /etc/init.d/autofs
weiler start, it still gives me the:
weiler Starting automount: No Mountpoints Defined
weiler Error at the command line. I *DO* see traffic to the Openldap server
weiler this time though, and in the OpenLDAP logs I see:
weiler ber_scanf fmt ({mm}) ber:
weiler ber_scanf fmt ({mm}) ber:
weiler filter: ((?=undefined)(?=undefined))
weiler ber_scanf fmt ({M}}) ber:
weiler attrs: automountMapName automountInformation
== limits_get: conn=10642 op=6 dn=[anonymous]
weiler = bdb_search
weiler bdb_dn2entry(dc=domain,dc=com)
weiler So it looks like the automounter is searching for
weiler automountMapName and automountInformation. Which is bad,
weiler because my maps are in the form of nisMapName and nisMapEntry.
weiler Does anyone know if there is an easy way to tell the automounter to
weiler look for the other attributes? Or do I have to try to set up some
weiler kind of aliasing on my OpenLDAP server?
The autofs init script in autofs v4 will invoke a command,
autofs-ldap-auto-master, to determine if there is an auto.master available
on your ldap server. It should try 3 schemas before giving up.
You didn't mention whether you actually had an auto.master in ldap. Do you?
-Jeff
___
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
Re: [autofs] AutoFS problem with OpenLDAP server
Hi Jeff, The autofs init script in autofs v4 will invoke a command, autofs-ldap-auto-master, to determine if there is an auto.master available on your ldap server. It should try 3 schemas before giving up. You didn't mention whether you actually had an auto.master in ldap. Do you? No, I don't have an auto.master in LDAP, I guess I was figuring Linux's AutoFS would kind of figure it out like it does with Solaris. So AutoFS requires a auto.master in LDAP? Do you know what I need to do to tweak this by any chance? Thanks for the response! ciao, erich ___ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
Re: [autofs] AutoFS problem with OpenLDAP server
Somehow I feel I didn't send this correctly last time, resending: Hi Jeff, The autofs init script in autofs v4 will invoke a command, autofs-ldap-auto-master, to determine if there is an auto.master available on your ldap server. It should try 3 schemas before giving up. You didn't mention whether you actually had an auto.master in ldap. Do you? No, I don't have an auto.master in LDAP, I guess I was figuring Linux's AutoFS would kind of figure it out like it does with Solaris. So AutoFS requires a auto.master in LDAP? Do you know what I need to do to tweak this by any chance? Or maybe point me to a how-to or something of that nature? Thanks for the response! ciao, erich ___ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
