"M"

Machine is not on the network

Cause

This error is Remote File Sharing (RFS) specific. It occurs when users try to advertise, unadvertise, mount, or unmount remote resources while the machine has not properly started a network connect.

Technical Notes

The symbolic name for this error is ENONET, errno=64.

mailtool: Can't create dead letter: Permission denied

Cause

An attempt was made to send a message with mailtool(1) from a directory where the user does not have write permission, and the user's home directory is currently unavailable.

Action

Change to another directory and start mailtool(1) again, or use chmod(1) to change permissions for the directory (if possible).

mailtool: Could not initialize the Classing Engine

Cause

When a user runs mailtool(1) on a remote machine, setting the DISPLAY environment back to the local machine, this message might appear inside a dialog box window. The dialog box goes on to say that the Classing Engine must be installed to use Attachments. This problem occurs because rlogin(1) does not propagate the user's environment.

Action

Exit mailtool(1) and set your OPENWINHOME environment variable to /usr/openwin. Then run mailtool(1) again. The error message will not appear, and you will be able to use Attachments.

Technical Notes

Classing Engine is a new name for Tool Talk. Earlier versions of mailtool(1) said Tool Talk: TT_ERR_NOMP instead of Classing Engine.

Mail Tool is confused about the state of your Mail File.

Cause

This message appears in a pop-up dialog box whenever you ask mailtool(1) to access messages after another mail reader has modified your inbox. A request follows: "Please Quit this Mail Tool."

Action

Click "Continue" to close the dialog box, then exit mailtool(1). If you continue trying to read mail, messages deleted by the other mail reader will never appear, and mailtool(1) will fail to see any new messages.

mail: Your mailfile was found to be corrupted (Content-length mismatch).

Cause

This message comes from mail(1) or mailx(1)(1) whenever it detects messages with a different content length than advertised. The mail(1) program tells you which message might be truncated or might have another message concatenated to it.

Two common causes of content length mismatches are the simultaneous use of different mail readers (such as mail(1) and mailtool(1)), or using a mail reading program (or an editor) that does not update the Content-Length field after altering a message.

Action

The mailx(1) program can usually recover from this error and delineate mail message boundaries correctly. Pay close attention to the message that might be truncated or combined with another message, and to all messages after that one. If a mail file becomes hopelessly corrupted, run it through a text editor to eliminate all Content-Length lines, and ensure that each message has a From (no colon) line for each message, preceded by a blank line.

To avoid mailfile corruption, exit from mailtool(1) without saving changes when you are currently running mail(1) or mailx(1).

Machine is not on the network

Cause

This error is Remote File Sharing (RFS) specific. It occurs when users try to advertise, unadvertise, mount, or unmount remote resources while the machine has not properly started a network connect.

Technical Notes

The symbolic name for this error is ENONET, errno=64.

mailtool: Can't create dead letter: Permission denied

Cause

An attempt was made to send a message with mailtool(1) from a directory where the user does not have write permission, and the user's home directory is currently unavailable.

Action

Change to another directory and start mailtool(1) again, or use chmod(1) to change permissions for the directory (if possible).

mailtool: Could not initialize the Classing Engine

Cause

When a user runs mailtool(1) on a remote machine, setting the DISPLAY environment back to the local machine, this message might appear inside a dialog box window. The dialog box goes on to say that the Classing Engine must be installed to use Attachments. This problem occurs because rlogin(1) does not propagate the user's environment.

Action

Exit mailtool(1) and set your OPENWINHOME environment variable to /usr/openwin. Then run mailtool(1) again. The error message does not appear, and you can use Attachments.

Technical Notes

Classing Engine is a new name for Tool Talk. Earlier versions of mailtool(1) said Tool Talk: TT_ERR_NOMP instead of Classing Engine.

Mail Tool is confused about the state of your Mail File.

Cause

This message appears in a pop-up dialog box whenever you ask mailtool(1)(1) to access messages after another mail reader has modified your inbox. A request follows: "Please Quit this Mail Tool."

Action

Click "Continue" to close the dialog box, then exit mailtool(1). If you continue trying to read mail, messages deleted by the other mail reader will never appear, and mailtool(1) will fail to see any new messages.

mail: Your mailfile was found to be corrupted (Content-length mismatch).

Cause

This message comes from mail(1) or mailx(1) whenever it detects messages with a different content length than advertised. The mail(1) program tells you which message might be truncated or might have another message concatenated to it.

Two common causes of content length mismatches are the simultaneous use of different mail readers (such as mail(1) and mailtool(1)), or using a mail reading program (or an editor) that does not update the Content-Length field after altering a message.

Action

The mailx(1) program can usually recover from this error and delineate mail message boundaries correctly. Pay close attention to the message that might be truncated or combined with another message, and to all messages after that one. If a mail file becomes hopelessly corrupted, run it through a text editor to eliminate all Content-Length lines, and ensure that each message has a From (no colon) line for each message, preceded by a blank line.

To avoid mailfile corruption, exit from mailtool(1) without saving changes when you are currently running mail(1) or mailx(1).

file name may contain holes - can't swap on it.

Cause

A swapfile was created with the command:

# mkfile -nv 50m /ab/swap_50mb

# swap -a /ab/swap_50mb

/ab/swap_50mb may contain holes - can't swap on it.
/ab/swap_50mb: Error 0

Action

The -n option was supported on SunOS 4, but on SunOS 5 (Solaris 2) -n works only when the file is to be used by NFS. Local swap files cannot be created with the -n option.

mbuf map full

Cause

mbuf allocation

Memory address alignment

Cause

This message can occur when printing large files on a SPARCprinter attached to a SPARCstation 2.

Action

Replace the SPARCstation 2 CPU with one that is at the most recent dash level.

memory leaks

Cause

An application uses up more and more memory, until all swap space is exhausted.

Action

Many developers have found that third party software (such as Purify) can help identify memory leaks in their applications. If you suspect that you have a memory leak, you can use sar(1) to check on the Kernel Memory Allocation (KMA). Any driver or module that uses KMA resources, but does not specifically return the resources before it exits, can create a memory leak.

See Also

For more information on memory leaks, see the section on monitoring system activity in the System Administration Guide, Volume II. If you are using the AnswerBook, "displaying disk usage" is a good search string. Also, see the section on system resource problems in the NIS+ and FNS Administration Guide.

Message too long

Cause

A message sent on a transport provider was larger than the internal message buffer or some other network limit.

Technical Notes

The symbolic name for this error is EMSGSIZE, errno=97.

mount: /dev/dsk/string is already mounted, /string is busy, or...

Cause

While trying to mount a filesystem, the mount(1M) command received a "Device busy" (EBUSY) error code. There are several possible reasons: this /dev/dsk filesystem is already mounted on a different directory, the busy path name is the working directory of an active process, or the system has exceeded its maximum number of mount points (unlikely).

Action

Run /etc/mount to see if the filesystem is already mounted. If not, check to see if any shells are active in the busy directory (did the user cd(1) into the directory?), or if any processes in the ps(1) listing are active in that directory. If the reason for the error message isn't obvious, try using a different directory for the mount point.

mount: giving up on: /string

Cause

An existing server did not respond to an NFS mount request, so after retrying a number of times (default 1000), the mount(1M) command has given up. Nonexistent servers or bad mount points produce different messages.

Action

If the RPC: Program not registered message precedes this one, the requested mount server probably did not share (export) any filesystems, so it has no NFS daemons running. Have the superuser on the mount server share(1M) the filesystem, then run /etc/init.d/nfs.server start to begin NFS service.

If the requested mount server is down or slow to respond, check to see whether the machine needs repair or rebooting.

mount: mount-point /string does not exist.

Cause

Someone tried to mount a filesystem onto the specified directory, but there is no such directory.

Action

If this is the directory name you want, run mkdir(1) to create this directory as a mount point.

mount: the state of /dev/dsk/string is not okay

Cause

The system was unable to mount the filesystem that was specified because the super-block indicates that the filesystem might be corrupted. This is not an impediment for read-only mounts.

Action

If you don't need to write on this filesystem, mount(1M) it using the -o ro option. Otherwise, do as one of the message continuation lines suggests and run fsck(1M) to correct the filesystem state and update the super-block.

See Also

For more information on using fsck(1M), see the section on checking filesystem integrity in the System Administration Guide, Volume I.

Multihop attempted

Cause

This error occurs when users try to access remote resources that are not directly accessible.

Technical Notes

The symbolic name for this error is EMULTIHOP, errno=74.

mbuf map full

Cause

mbuf allocation

Memory address alignment

Cause

This message can occur when printing large files on a SPARCprinter attached to a SPARCstation 2.

Action

Replace the SPARCstation 2 CPU with one that is at the most recent dash level.

memory leaks

Cause

An application uses up more and more memory, until all swap space is exhausted.

Action

Many developers have found that third party software (such as Purify) can help identify memory leaks in their applications. If you suspect that you have a memory leak, you can use sar(1) to check on the Kernel Memory Allocation (KMA). Any driver or module that uses KMA resources, but does not specifically return the resources before it exits, can create a memory leak.

See Also

For more information on memory leaks, see the section on monitoring system activity in the System Administration Guide, Volume II. If you are using the AnswerBook, "displaying disk usage" is a good search string. Also, see the section on system resource problems in the NIS+ and FNS Administration Guide.

Message too long

Cause

A message sent on a transport provider was larger than the internal message buffer or some other network limit.

Technical Notes

The symbolic name for this error is EMSGSIZE, errno=97.

mount: /dev/dsk/string is already mounted, /string is busy, or...

Cause

While trying to mount a filesystem, the mount(1M) command received a "Device busy" (EBUSY) error code. There are several possible reasons: this /dev/dsk filesystem is already mounted on a different directory, the busy path name is the working directory of an active process, or the system has exceeded its maximum number of mount points (unlikely).

Action

Run /etc/mount to see if the filesystem is already mounted. If not, check to see if any shells are active in the busy directory (did the user cd(1) into the directory?), or if any processes in the ps(1) listing are active in that directory. If the reason for the error message isn't obvious, try using a different directory for the mount point.

mount: giving up on: /string

Cause

An existing server did not respond to an NFS mount request, so after retrying a number of times (default 1000), the mount(1M) command has given up. Nonexistent servers or bad mount points produce different messages.

Action

If the "RPC: Program not registered" message precedes this one, the requested mount server probably did not share (export) any filesystems, so it has no NFS daemons running. Have the superuser on the mount server share(1M) the filesystem, then run /etc/init.d/nfs.server start to begin NFS service.

If the requested mount server is down or slow to respond, check to see whether the machine needs repair or rebooting.

mount: mount-point /string does not exist.

Cause

Someone tried to mount a filesystem onto the specified directory, but there is no such directory.

Action

If this is the directory name you want, run mkdir(1) to create this directory as a mount point.

mount: the state of /dev/dsk/string is not okay

Cause

The system was unable to mount the filesystem that was specified because the super-block indicates that the filesystem might be corrupted. This is not an impediment for read-only mounts.

Action

If you don't need to write on this filesystem, mount(1M) it using the -o ro option. Otherwise, do as one of the message continuation lines suggests and run fsck(1M) to correct the filesystem state and update the super-block.

See Also

For more information on using fsck(1M), see the section on checking filesystem integrity in the System Administration Guide, Volume I.

Multihop attempted

Cause

This error occurs when users try to access remote resources that are not directly accessible.

Technical Notes

The symbolic name for this error is EMULTIHOP, errno=74.