LinuxQuestions.org - autofs hangs, CentOS6.2

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - autofs hangs, CentOS6.2 (https://www.linuxquestions.org/questions/linux-networking-3/autofs-hangs-centos6-2-a-4175421117/)

autofs hangs, CentOS6.2

Hello,

To access some scientific software, I have been running a script on a remote share accessed through autofs and automount. Everything was running fine for months when this script started to hang and it looks like automount is the problem.

When trying to run the script I try to "execute" a symbolic link pointing to the real script at the remote location that automount should mount but this is what happens:

Starting autofs :

Code:

service autofs start

dmesg output :

Code:

SELinux: initialized (dev autofs, type autofs), uses genfs_contexts

/var/log/messages:

Code:

automount[16308]: lookup_read_master: lookup(nisplus): couldn't locate nis+ table auto.master

Then I try to execute the script, command seems to hang, prompt returns only when I hit <CTRL+C>.

dmesg output at this point :

Code:

automount[15825]: segfault at 28 ip 00007f285e149862 sp 00007f28619e1960 error 4 in lookup_hosts.so[7f285e140000+1c000]

/var/log/messages:

Code:

automount[16806]: rpc_get_exports_proto

kernel: automount[16818]: segfault at 28 ip 00007fab18299862 sp 00007fab1b12f960 error 4 in lookup_hosts.so[7fab18290000+1c000]

abrtd: Directory 'ccpp-2012-08-08-22:13:17-16806' creation detected

abrt[16819]: Saved core dump of pid 16806 (/usr/sbin/automount) to /var/spool/abrt/ccpp-2012-08-08-22:13:17-16806 (24166400 bytes)

9-10 seconds later some more appears:

Code:

abrtd: Sending an email...

abrtd: Email was sent to: root@localhost

abrtd: Duplicate: UUID

abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2012-07-21-16:35:37-2125

abrtd: Problem directory is a duplicate of /var/spool/abrt/ccpp-2012-07-21-16:35:37-2125

Deleting problem directory ccpp-2012-08-08-22:13:17-16806 (dup of ccpp-2012-07-21-16:35:37-2125)

Any help will be greatly appreciated!

Sounds like a host lookup issue related to one of the mounts you have setup. Can you do a "host servername" on all the servers you have listed in your autofs config files without error?

Also what does your /etc/nsswitch.conf file look like?

autofs config files are mostly unmodified we only added the following to the auto.master:

Code:

/net /etc/auto.net

auto.net modification is adding "nonstrict" to the opts= list

network shares (should) get mounted when issuing a <command>, executable created as below:

Code:

ln -s /hosts/server.somefed.gov/subdirs/command /usr/bin/command

host server.somefed.gov returns an IP address

also, I can mount manually the "server.somefed.gov/subdirs" directory using a simple mount command:

Code:

mount /hosts/server.somefed.gov/subdirs /mnt

/etc/nsswitch.conf:

Code:

#

# /etc/nsswitch.conf

#

# An example Name Service Switch config file. This file should be

# sorted with the most-used services at the beginning.

#

# The entry '[NOTFOUND=return]' means that the search for an

# entry should stop if the search in the previous entry turned

# up nothing. Note that if the search failed due to some other reason

# (like no NIS server responding) then the search continues with the

# next entry.

#

# Valid entries include:

#

#      nisplus                Use NIS+ (NIS version 3)

#      nis                    Use NIS (NIS version 2), also called YP

#      dns                    Use DNS (Domain Name Service)

#      files                  Use the local files

#      db                      Use the local database (.db) files

#      compat                  Use NIS on compat mode

#      hesiod                  Use Hesiod for user lookups

#      [NOTFOUND=return]      Stop searching if not found so far

#



# To use db, put the "db" in front of "files" for entries you want to be

# looked up first in the databases

#

# Example:

#passwd:    db files nisplus nis

#shadow:    db files nisplus nis

#group:    db files nisplus nis



passwd:    files

shadow:    files

group:      files



#hosts:    db files nisplus nis dns

hosts:      files dns

Any ideas ? Thanks!

ps : sorry for the altered domain name(s), working for a federal research institute I don't want to have my rear kicked because some IT security guy thought I posted sensitive info.

I'm stumped, I thought it might have been due to you using nis as opposed to DNS for lookups but you already have that set. I'll do some more thinking and bounce it off a few people but hopefully someone can post something behind me to help get you there. Your files look correct.

Downgrading autofs-5.0.5-54.el6.x86_64 to autofs-5.0.1-0.rc2.163.el5.x86_64 solved the problem.