1753587 Members
6924 Online
108796 Solutions
New Discussion юеВ

Re: automount error

 
SOLVED
Go to solution
Dave Olker
HPE Pro

Re: automount error

I'm happy to try to resolve this. If this is something you can reproduce at will then I'd like you to enable debug AutoFS logging and capture a couple of these errors. To do this you send a SIGUSR2 signal to the automountd daemon:

# kill -17

This should toggle on debug logging to the file /var/adm/automount.log. Wait until you see a couple instances of the error message you're concerned about and then send another SIGUSR2 to the same pid to toggle debug logging off.

Either post or send me (dave.olker@hp.com) the following files:

/var/adm/automount.log
/etc/auto_master
ANY other autofs map referenced in the auto_master file
/etc/resolv.conf

That should help me get started.

Regards,

Dave
I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Tim Nelson
Honored Contributor

Re: automount error

Another option.

turn off automount and put entries in /etc/fstab and be done with it ?

shameemsoft
Frequent Advisor

Re: automount error

Thanks Dave,

Kindly find the automount.log details in the attachment.

#cat /etc/auto_master
/net -hosts -nosuid,soft,nobrowse

we are not using DNS. we are using only /etc/hosts for name resolution.

Thanks Tim for your response.



Dave Olker
HPE Pro

Re: automount error

Hi Shameem,

The entire log file is filled with repeating entries like this:

Jan 16 09:21:24 t1 LOOKUP REQUEST: Sat Jan 16 09:21:24 2010
Jan 16 09:21:24 t1 name=usr.scratch[] map=-hosts opts=nosuid,soft,nobrowse path=/net direct=0
Jan 16 09:21:24 t1 mapline: -hosts
Jan 16 09:21:24 t1 do_mapent_hosts: host usr.scratch
Jan 16 09:21:24 t1 ping: usr.scratch timeout=15 request vers=3 min=2
Jan 16 09:21:24 t1 pingnfs FAIL: can't get nfs version
Jan 16 09:21:24 t1 do_lookup1: action=2 wildcard=FALSE error=2
Jan 16 09:21:24 t1 LOOKUP REPLY : status=2


Someone or some application is constantly trying to access the path "/net/usr.scratch" and AutoFS interprets the string "usr.scratch" as the NFS server's hostname. It tries to resolve this host name so it can contact it to discover what filesystems it is exporting.

Something tells me you don't really have a server named "usr.scratch". :)

Does the name "usr.scratch" mean anything significant for the applications you run on this client? Do you have something set incorrectly in one of your environment variables, like PATH or some library pathname variable?

One other comment. AutoFS is an optional product. You're not required to use AutoFS to mount filesystems. Since this entire log file shows no actual MOUNT requests, are you certain you really need to use AutoFS at all? As Tim and others have said, could you configure the NFS filesystems you need in the /etc/fstab file and simply disable AutoFS? Or are there really some NFS filesystem managed by AutoFS used by your applications?

Regards,

Dave
I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Dennis Handly
Acclaimed Contributor

Re: automount error

>Dave: Do you have something set incorrectly in one of your environment variables

Or a symlink to /net/usr.scratch.
shameemsoft
Frequent Advisor

Re: automount error

Thanks Dave/Dennis for your response.

We checked our SAP application and didn't access /net/use.scratch from application level.

Also environment variable & other PATH is configured properly.

We dont have hostname like usr.scratch :)

This error is repeating in 4 servers in our environment.

Also we dont have symblic link for /net/usr.scratch as Dennis said.

>>are there really some NFS filesystem managed by AutoFS used by your applications?

I need to cross check whether AUTOFS used by application or not. I will check and get back to you...

But I would like to find out root cause of this issue ;).

Thanks in Advance
Dennis Handly
Acclaimed Contributor

Re: automount error

>We checked our SAP application and didn't access /net/usr.scratch from application level.

You could use "strings -a" on each of your executables and shlibs and look for "usr.scratch".

You also know it happened at "Jan 16 09:21:24" and other times in your log. What was running then?

You can also use tusc to look at opens.

>Also we don't have symbolic link for /net/usr.scratch as Dennis said.

I assume you used find(1) to search for all symlinks and then grep?

>I would like to find out root cause of this issue

You are trying to open a file in /net/usr.scratch/.
shameemsoft
Frequent Advisor

Re: automount error

Thanks a lot Gentlemen for your response.

Not able to find which application trying to access this share.

Finally I have disabled default map entry.

#/net -hosts -nosuid,soft,nobrowse

Now this error is not repeating..

Thank you all.

Shameem
shameemsoft
Frequent Advisor

Re: automount error

Thank You