[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Note that there are more error and logging messages possible than are listed here. Most of them are self-explanatory. Refer to the program sources for more details on the rest.
12.1 Log Messages |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In the following sections a brief explanation is given of some of the
log messages made by Amd. Where the message is in `typewriter'
font, it corresponds exactly to the message produced by Amd. Words
in italic are replaced by an appropriate string. Variables,
${var}
, indicate that the value of the appropriate variable is
output.
Log messages are either sent directly to a file, or logged via the syslog(3) mechanism. See section log_file Parameter. In either case, entries in the file are of the form:
date-string hostname amd[pid] message |
12.1.1 Fatal errors | ||
12.1.2 Info messages |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Amd attempts to deal with unusual events. Whenever it is not possible to deal with such an error, Amd will log an appropriate message and, if it cannot possibly continue, will either exit or abort. These messages are selected by `-x fatal' on the command line. When syslog(3) is being used, they are logged with level `LOG_FATAL'. Even if Amd continues to operate it is likely to remain in a precarious state and should be restarted at the earliest opportunity.
The prototype mount point created during a filesystem restart did not contain a reference to the restarted filesystem. This error "should never happen".
A specific NIS domain was requested on the command line, but no server for that domain is available on the local net.
When Amd starts it determines its own IP address. If this lookup fails then Amd cannot continue. The hostname it looks up is that obtained returned by gethostname(2) system call.
Amd creates its own file handles for the automount points. When it mounts itself as a server, it must pass these file handles to the local kernel. If the filehandle is not obtainable the mount point is ignored. This error "should never happen".
To prevent embarrassment, Amd makes sure it has appropriate system
privileges. This amounts to having an euid of 0. The check is made
after argument processing complete to give non-root users a chance to
access the -v
option.
No automount points were given on the command line and so there is no work to do.
While attempting to malloc some memory, the memory space available to Amd was exhausted. This is an unrecoverable error.
While attempting to realloc some memory, the memory space available to Amd was exhausted. This is an unrecoverable error.
Either the NFS or AMQ endpoint could not be created.
The gethostname(2) system call failed during startup.
The gethostname(2) system call returned a zero length host name. This can happen if Amd is started in single user mode just after booting the system.
An internal error occurred while restarting a pre-mounted filesystem. This error "should never happen".
An error occurred while Amd was mounting itself.
Somehow the main NFS server loop failed. This error "should never happen".
The incoming arguments to the AMQ server could not be free'ed.
The incoming arguments to the NFS server could not be free'ed.
The AMQ server could not be registered with the local portmapper or the internal RPC dispatcher.
The NFS server could not be registered with the internal RPC dispatcher.
XXX: This section needs to be updated
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Amd generates information messages to record state changes. These messages are selected by `-x info' on the command line. When syslog(3) is being used, they are logged with level `LOG_INFO'.
The messages listed below can be generated and are in a format suitable for simple statistical analysis. mount-info is the string that is displayed by Amq in its mount information column and placed in the system mount table.
An automount point has been timed out by the Amq command.
No access to the automount point has been made within the timeout period.
The mount daemon refused to return a file handle for the requested filesystem.
The mount daemon gave some other error for the requested filesystem.
Amd is about to exit with the given exit status.
The named map has been modified and the internal cache is being re-synchronized.
An automount point has timed out, but the corresponding file server is known to be down. This message is only produced once for each mount point for which the server is down.
An NFS file server that was previously up is now down.
An NFS file server that was previously down is now up.
A new NFS file server has been referenced and is known to be down.
A new NFS file server has been referenced and is known to be up.
Attempts to mount a filesystem for the given automount point have failed to complete within 30 seconds.
A new file system has been mounted.
Amd is using a pre-mounted filesystem to satisfy a mount request.
A file system has been unmounted.
A file system of which only a sub-directory was in use has been unmounted.
A pre-mounted file system has been noted.
XXX: This section needs to be updated
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Erez Zadok on November, 27 2006 using texi2html 1.76.