automount daemon hangs on startup with utopic

Bug #1385895 reported by John Affleck
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
autofs5 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

With autofs 5.0.7-3ubuntu1.1 and autofs-ldap 5.0.7-3ubuntu1.1, automount starts up fine. With the new version (5.0.8-1ubuntu1) in utopic, it hangs shortly after displaying the ldap lookup information:

With 5.0.8-1ubuntu1
% automount -V

Linux automount version 5.0.8

Directories:
 config dir: /etc/default
 maps dir: /etc
 modules dir: /usr/lib/x86_64-linux-gnu/autofs

Compile options:
  ENABLE_FORCED_SHUTDOWN ENABLE_IGNORE_BUSY_MOUNTS WITH_HESIOD
  WITH_LDAP WITH_SASL LIBXML2_WORKAROUND

% automount -dvm
lookup_nss_read_master: reading master files ou=auto.master,ou=automount,dc=oddment,dc=net
lookup_nss_read_master: reading master ldap ou=auto.master,ou=automount,dc=oddment,dc=net

(hangs)

With the version from trusty (autofs-ldap_5.0.7-3ubuntu1.1)
% automount -V

Linux automount version 5.0.7

Directories:
 config dir: /etc/default
 maps dir: /etc
 modules dir: /usr/lib/x86_64-linux-gnu/autofs

Compile options:
  ENABLE_FORCED_SHUTDOWN ENABLE_IGNORE_BUSY_MOUNTS WITH_HESIOD
  WITH_LDAP WITH_SASL LIBXML2_WORKAROUND

% automount -dvm

autofs dump map information
===========================

global options: none configured

Mount point: /home

source(s):
WARNING: gnome-keyring:: C_Initialize called twice for same process

  type: ldap
  map: ldap:ou=auto.home,ou=automount,dc=oddment,dc=net

.....

Stack trace from hung automount:
(gdb) where
#0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1 0x00007f1e512b356a in _L_lock_913 () from /lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007f1e512b3390 in __GI___pthread_mutex_lock (mutex=0x7f1e50237720 <ldapinit_mutex>) at ../nptl/pthread_mutex_lock.c:79
#3 0x00007f1e50018d90 in init_ldap_connection () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#4 0x00007f1e50019062 in __init_ldap_connection () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#5 0x00007f1e50018da4 in init_ldap_connection () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#6 0x00007f1e5001912a in ?? () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#7 0x00007f1e500194c0 in ?? () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#8 0x00007f1e500198ac in ?? () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#9 0x00007f1e5001b188 in lookup_read_master () from /usr/lib/x86_64-linux-gnu/autofs/lookup_ldap.so
#10 0x00007f1e51700881 in ?? ()
#11 0x00007f1e51701251 in lookup_nss_read_master ()
#12 0x00007f1e516f5439 in main ()

% lsb_release -rd
Description: Ubuntu 14.10
Release: 14.10

% apt-cache policy autofs-ldap
autofs-ldap:
  Installed: 5.0.8-1ubuntu1
  Candidate: 5.0.8-1ubuntu1
  Version table:
 *** 5.0.8-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in autofs5 (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.