autofs fails to look up master map from ldap in Intrepid

Bug #332677 reported by Matt Hollingsworth
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
autofs (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: autofs

I am unable to get automount to be configured via ldap.

If I start automount with this command:

sudo automount -f ldap:ou=auto.master,ou=automount,dc=example,dc=com

the following error occurs:

open_lookup:95: cannot open lookup module ldap (/usr/lib/autofs/lookup_ldap.so: undefined symbol: do_verbose)

System information:

lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

apt-cache policy autofs:

autofs:
  Installed: (none)
  Candidate: 4.1.4+debian-2.1ubuntu2
  Version table:
     4.1.4+debian-2.1ubuntu2 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Chuck Short (zulcss) wrote :

Hi,

I was wondering if you were still having this problem.

Regards
chuck

Changed in autofs (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Chuck Short (zulcss) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in autofs (Ubuntu):
status: Incomplete → Won't Fix
Mike N (michael-l-north)
Changed in autofs (Ubuntu):
status: Won't Fix → New
Revision history for this message
Mike N (michael-l-north) wrote :

I can confirm that this problem still exists in Ubuntu 9.10

Dec 9 01:26:07 human automount[11065]: using kernel protocol version 5.01
Dec 9 01:26:07 human automount[11065]: lookup_nss_read_master: reading master file /etc/auto.master
Dec 9 01:26:07 human automount[11065]: parse_init: parse(sun): init gathered global options: (null)
Dec 9 01:26:07 human automount[11065]: lookup_read_master: lookup(file): read entry +auto.master
Dec 9 01:26:07 human automount[11065]: lookup_nss_read_master: reading master files auto.master
Dec 9 01:26:07 human automount[11065]: parse_init: parse(sun): init gathered global options: (null)
Dec 9 01:26:07 human automount[11065]: lookup_nss_read_master: reading master ldap auto.master
Dec 9 01:26:07 human automount[11065]: open_lookup:90: cannot open lookup module ldap (/usr/lib/autofs/lookup_ldap.so: undefined symbol: do_verbose)
Dec 9 01:26:07 human automount[11065]: lookup(file): failed to read included master map auto.master
Dec 9 01:26:07 human automount[11065]: no mounts in table

My /etc/auto.master has nothing in it except the default uncommented line (+auto.master at the end of the file).

I have made the following changes to /etc/default/autofs

LOGGING="debug"

LDAP_URI="ldap://localhost"

SEARCH_BASE="ou=automount,dc=mydomain,dc=com"

MAP_OBJECT_CLASS="automountMap"
ENTRY_OBJECT_CLASS="automount"
MAP_ATTRIBUTE="ou"
ENTRY_ATTRIBUTE="cn"
VALUE_ATTRIBUTE="automountInformation"

I have several machines running CentOS 5.3, and everything worked perfectly as soon as I renamed auto.master to auto_bak.master (literally -- install, set up ldap authentication and rename the file. Nothing more.). I assume this means we can rule out LDAP-related problems.

If it makes a difference, this bug is occurring on both of my Ubuntu servers, and they are the OpenLDAP servers. All configuration is done with a non-LDAP user. Slapd confirmed to be up and running from the point of view of a CentOS machine.

LDAP automounts are in the form:

dn: cn=myNfsShare,ou=auto.u,ou=automount,dc=mydomain,dc=com
objectClass: automount
objectClass: top
automountInformation: -fstype=nfs,rw,soft,intr,rsize=8192,wsize=8192 shareHostName:/myNfsShare
cn: myNfsShare
creatorsName: cn=root,dc=com
hasSubordinates: FALSE
structuralObjectClass: automount
subschemaSubentry: cn=Subschema

and maps are in the form:

dn: ou=auto.machines,ou=automount,dc=mydomain,dc=com
objectClass: automountMap
objectClass: top
ou: auto.machines
creatorsName: cn=root,dc=com
hasSubordinates: TRUE
structuralObjectClass: automountMap
subschemaSubentry: cn=Subschema

I have to manually keep my auto.* files in sync on the ubuntu machines until this bug gets fixed, so please let me know if there's any other information you need in order to investigate.

Revision history for this message
Mike N (michael-l-north) wrote :

Here is some more info on the affected systems:

cat proc/version

Linux version 2.6.31.4.custom (miken@human) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #1 SMP Thu Nov 19 02:08:38 EST 2009

OpenLDAP:

@(#) $OpenLDAP: slapd 2.4.18 (Sep 8 2009 17:47:22) $
 buildd@crested:/build/buildd/openldap-2.4.18/debian/build/servers/slapd

Automount:

Linux automount version 5.0.4

Directories:
 config dir: /etc/default
 maps dir: /etc
 modules dir: /usr/lib/autofs

Compile options:
  ENABLE_FORCED_SHUTDOWN ENABLE_IGNORE_BUSY_MOUNTS WITH_HESIOD
  WITH_LDAP WITH_SASL LIBXML2_WORKAROUND

Revision history for this message
Christopher Nighswonger (cnighswonger) wrote :

Problem confirmed on 10.04 Lucid. Symptoms are exactly the same as Mike described.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Affects 2 people, changing status to Confirmed.

Changed in autofs (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.