The following are error messages you may see if the automounter fails.
: Not found
The required map cannot be located. This message is produced only when the -v (verbose) option is given. Check the spelling and pathname of the map name.
dir mountpoint must start with '/'
The automounter mount point must be given as full pathname. Check the spelling and pathname of the mount point.
: Not a directory
The mountpoint exists but it is not a directory. Check the spelling and pathname of the mount point.
hierarchical mountpoint: mountpoint
The automounter will not allow itself to be mounted within an automounted directory. You will have to think of another strategy.
WARNING: mountpoint not empty!
The mount point is not an empty directory. This message is produced only when the -v (verbose) option is given, and it is only a warning. All it means is that the previous contents of mountpoint will not be accessible.
Can't mount mountpoint: reason
The automounter cannot mount itself at mountpoint because of reason.
already mounted on mountpoint
The automounter is attempting to mount a resource on a mount point, but the resource is already mounted on that mount point. An entry in /etc/vfstab is duplicated in an automounter map (either by accident or because the output of mount -p was redirected to vfstab). Delete one of the redundant entries.
WARNING: hostname:filesystem already mounted on mountpoint
The automounter is mounting itself on top of an existing mount point.
couldn't create directory: reason
The system could not create a directory because of reason.
bad entry in map mapname "map entry"
The map entry in map mapname is incorrect.
map mapname, key map key: bad
The map entry is malformed, and the automounter cannot interpret it. Check the entry; perhaps there are characters in it that need escaping.
: exports: rpc_err
An error occurs when the automounter tries to get a share list from hostname. This indicates a server or network problem.
not responding
A resource was trying to be mounted from host hostname while the host was down.
server not responding
A resource that is currently mounted from host hostname (that is down) has been accessed.
Mount of hostname:filesystem on mountpoint: reason
These error messages occur after the automounter attempts to mount from hostname but gets no response or fails. This may indicate a server or network problem.
from hostname: absolute symbolic link
When mounting a resource, the automounter has detected that mountpoint is an absolute symbolic link (beginning with /). The content of the link is pathname. This may have undesired consequences on the client; for example, if the content of the link were /usr, it would overlay the standard /usr directory, making common system services unavailable.
Cannot create socket for broadcast rpc: rpc_err
Many_cast select problem: rpc_err
Cannot send broadcast packet: rpc_err
Cannot receive reply to many_cast: rpc_err
All these error messages indicate problems attempting to ``ping'' servers for a replicated filesystem. This may indicate a network problem.
trymany: servers not responding: reason
No server in a replicated list is responding. This may indicate a network problem.
Remount hostname:filesystem on mountpoint: server not responding
An attempted remount after an unmount failed. This indicates a server problem.
NFS server (pidn@mountpoint) not responding still trying
An NFS request that was made to the automount daemon having PID n and serving mountpoint has timed out. The automounter may be overloaded temporarily, or dead. Wait a few minutes; if the condition persists, reboot the client. If you don't want to reboot, exit all processes that make use of automounted resources (or change to a nonautomounted resource, in the case of a shell), kill the current automount process, and restart it again from the command line. If this fails, you must reboot.