automount error conditions

All automount error messages are prefixed by the string ``automount: ''. The messages are listed here in alphabetical order, ignoring all variable strings. Therefore, if you cannot locate your message by the first word, check it under the second.

Some error messages (as indicated in their descriptions) are generated only if you use the verbose option (-v) in addition to any other automount options:

automount -v -your_options

You should run the verbose option if automount fails to start properly.

server:pathname already mounted on mountpoint

automount is attempting to mount over a previous mount of the same filesystem. This could happen if an entry appears both in /etc/default/filesys
and in an automount map (either by accident or because the output of mount -p was redirected to default/filesys). Delete one of the redundant entries. This message is produced only when the -v option is given.

bad entry in map mapname

The map entry is malformed, and automount cannot interpret it. Recheck the entry; perhaps there are characters in it that need escaping.

bad key key in direct map mapname

While scanning a direct map, automount found an entry key without a prepended ``/''. Keys in direct maps must be full pathnames. This message is produced only when the -v option is given.

bad key key in indirect map mapname

While scanning an indirect map, automount found an entry key containing a ``/''. Indirect map keys must be simple names, not pathnames. This message is produced only when the -v option is given.

Cannot create socket for nfs: rpc_err

Indicates problems attempting to reach servers for a replicated filesystem using the ping command. This may indicate a network problem.

cannot create UDP service

automount cannot establish a UDP connection.

can't get my address

automount cannot find an entry for its host in /etc/hosts, hosts.byname), or the Domain Name Service (DNS).

can't mount mountpoint: reason

automount could not mount its daemon at mountpoint.

can't mount server:pathname: reason

The mount daemon on the server refuses to provide a file handle for server:pathname. Check the export table on server. This message is produced only when the -v option is given.

couldn't create mntpnt mountpoint: reason

automount cannot create a mount point required for a mount. This usually occurs when attempting to mount hierarchically all of a server's exported filesystems. A required mount point may exist only in a filesystem that cannot be mounted (it may not be exported) and it cannot be created because the exported parent filesystem is exported read-only. This message is produced only when the -v option is given.

couldn't create pathname: reason

Here pathname is /tmp_mnt or the argument to the -M command line option.

dir mountpoint must start with ``/''

The automount mount point must be given as the full pathname. Check the spelling and pathname of the mount point.

exiting

This is an advisory message only. automount has received a SIGTERM (has been killed) and is exiting.

hierarchical mountpoints: pathname1 and pathname2

automount does not allow its mount points to have a hierarchical relationship; that is, an automount mount point must not be contained within another automounted filesystem.

hostname : exports: rpc_err

There is an error getting the export list from hostname. This indicates a server or network problem.

host server not responding

automount attempted to contact server but received no response.

leading space in map entry entry text inmapname

automount discovered an entry in a map that contains leading spaces. This is usually an indication of an improperly continued map entry. For example:

   /usr/local  /bin    ra:/usr/local/bin
               /src    laidbak:/usr/src

In this example, the warning is generated when automount encounters the second line, because the first line should be terminated with a backslash (\). This message is produced only when the -v option is given.

map mapname, key key: bad

The map entry is malformed, and automount cannot interpret it. Recheck the entry; perhaps there are characters in it that need escaping.

mount of server:pathname on mountpoint: reason

automount failed to do a mount. This may indicate a server or network problem.

nfscast: cannot receive reply: reason

automount cannot receive replies from any of the servers in a list of replicated filesystem locations.

nfscast: Cannot send packet: reason

automount cannot send a query packet to a server in a list of replicated filesystem locations.

nfscast:select: reason

Indicates problems attempting to reach servers for a replicated filesystem using the ping command. This may indicate a network problem.

NIS bind failed

automount cannot communicate with the ypbind daemon. This is information only. automount continues to function correctly provided it requires no explicit NIS support. If you need NIS, check whether a ypbind daemon is running. This message is produced only when the -v option is given.

mapname: not found

The required map cannot be located. This message is produced only when the -v option is given. Check the spelling and pathname of the map name.

mountpoint: Not a directory

automount cannot mount itself on mountpoint because it is not a directory. Check the spelling and pathname of the mount point.

server:pathname no longer mounted

automount is acknowledging that server:pathname, which it mounted earlier, has been unmounted by the umount command. automount notices this within 1 minute of the unmount or immediately if it receives a SIGHUP.

no mount maps specified

automount was invoked with no maps to serve, and it cannot find the NIS auto.master map. It exits. Recheck the command, or restart NIS if that was the intention.This message is produced only when the -v option is given.

pathok: couldn't find devid device id

This is an internal automount error.

remount server:pathname on mountpoint : server not responding

automount failed to remount a filesystem it previously unmounted. This message may appear at intervals until the filesystem is successfully remounted This message is produced only when the -v option is given.

svc_register failed

automount cannot register itself as an NFS server. Because automount must register itself with portmap(NADM), use rpcinfo to make sure the portmapper (/etc/portmap) is running.

trymany: servers not responding: reason

No server in a replicated list is responding. This may indicate a network problem.

WARNING: mountpoint already mounted on

automount is attempting to mount over an existing mount point. This indicates an automount internal error. This message is produced only when the -v option is given.

WARNING: default option `option' ignored for map mapname

Here option is an unrecognized default mount option for the map mapname.

WARNING: option ignored for key in mapname

automount detected an unknown mount option. This is advisory only. Correct the entry in the appropriate map.

WARNING: mountpoint not empty!

The mount point is not an empty directory. The directory mountpoint contains entries that are hidden while automount is mounted there. This is advisory only. This message is produced only when the -v option is given.

mapname: yp_err

There is an error in looking up an entry in an NIS map. It may indicate NIS problems.

Home Notes Home MCSE MCSE MCITP + Security CCNA MCITP 2008  Boot Camp Schedule Register Frequently Asked Questions Course Fees Contact US Boot Camp Location Compare us to our competitors Testimonials Sitemap

Testimonials

Join MCSE MCITP Boot Camp & CCNA Boot Camp Back to Back Certification Today. links  270  290    291  293    294  298  299   Security  640-801  routing 811  821   831  Resources MCSE MCITP + CCNA  Training  Card pay  Papal  MCSE MCITP Notes  CCNA Notes    index main   root   link  resources home    Ref1 Ref2

Vibrant offers MCSE MCITP certification training boot camp for $5400 all inclusive, instructor led at California and Baltimore.