"A"

Accessing a corrupted shared library

Cause

Trying to exec(2) an a.out that requires a static shared library (to be linked in) and exec(2) could not load the static shared library. The static shared library is probably corrupted.

Technical Notes

The symbolic name for this error is ELIBBAD, errno=84.

access violation unknown host IP address

Cause

Solstice Backup Utility fails displaying the error: access violation unknown host IP address on Networker 4.2.2. This is usually caused by corrupted host name in the host NIS/NIS+ map/table.

Action

Check the Networker client configuration for an incorrect host name. If all else fail, a workaround is to add the entry to /etc/hosts.

A command window has exited because its child exited.

Cause

The argument to a cmdtool(1) or a shelltool(1) window looks like it is supposed to be a command, but the system cannot find the command.

Action

To run this command inside a cmdtool(1) or a shelltool(1), make sure the command is spelled correctly and is in your search path (if necessary, use a full path name). If you intended this argument as an option setting, use a minus sign (-) at the beginning of the option.

Technical Notes

Both the cmdtool(1) and the shelltool(1) are OpenWindows terminal emulators.

Address already in use

Cause

User attempted to use an address already in use, and the protocol does not allow this.

Technical Notes

The symbolic name for this error is EADDRINUSE, errno=125.

Address family not supported by protocol family

Cause

An address incompatible with the requested protocol was used.

Technical Notes

The symbolic name for this error is EAFNOSUPPORT, errno=124.

admintool: Received communication service error 4

Cause

AdminTool could not start a display method because a remote procedure call timed out, so it can't send the request. This error results when admintool(1M) tries to access the NIS or NIS+ tables when networking is not enabled.

Action

Verify the system network status with ifconfig -a to make sure the system is connected to the network. Make sure the ethernet cable is connected and the system is configured to run NIS or NIS+.

Advertise error

Cause

This error is RFS specific. It occurs when users try to advertise a resource already advertised, try to stop RFS while there are resources still advertised, or try to force unmount a resource when it is still advertised.

Technical Notes

The symbolic name for this error is EADV, errno=68.

answerbook: XView error: NULL pointer passed to xv_set

Cause

The AnswerBook navigator window comes up, but the document viewer window does not. This message appears on the console, and the message "Could not start new viewer" appears in the navigator window. This situation indicates that you have an unknown client or a problem with the network naming service.

Action

Run the ypmatch(1) or nismatch(1) command o determine if the client hostname is in the hosts map. If it isn't, add it to to NIS hosts map on the NIS master server. Then make sure the /etc/hosts file on the client contains an IP address and entry for that hostname followed by loghost (reboot if you changed the /etc/hosts file). Check that the ypmatch(1) or nismatch(1) client hosts command returns the same IP host address as in the /etc/hosts file. Finally, quit all existing AnswerBooks and restart.

See Also

For more information on the NIS hosts map, see the section on the default search criteria in the NIS+ and FNS Administration Guide. If you are using the AnswerBook, "NIS hosts map" is a good search string.

Arg list too long

Cause

The system could not handle the number of arguments given to a command or program when it combined those arguments with the environment's exported shell variables. The argument list limit is the size of the argument list plus the size of the environment's exported shell variables.

Action

The easiest solution is to reduce the size of the parent process environment by unsetting extraneous environment variables. (See the man page for the shell you're using to find out how to list and change your environment variables.) Then run the program again.

Technical Notes

An argument list longer than ARG_MAX bytes was presented to a member of the exec(2) family of system calls.

The symbolic name for this error is E2BIG, errno=7.

Argument out of domain

Cause

This is a programming error or a data input error.

Action

Ask the program's author to fix this condition, or supply data in a different format.

Technical Notes

This indicates an attempt to evaluate a mathematical programming function at a point where its value is not defined. The argument of a programming function in the math package (3M) is out of the domain of the function. This could happen when taking the square root, power, or log of a negative number, when computing a power to a non-integer, or when passing an out-of-range argument to a hyperbolic programming function.

To help pinpoint a program's math errors, use the matherr(3M) facility.

The symbolic name for this error is EDOM, errno=33.

Arguments too long

Cause

This C shell error message indicates that there are too many arguments after a command. For example, this can happen by invoking rm * in a huge directory. The C shell cannot handle more than 1706 arguments.

Action

Temporarily start a Bourne shell with sh(1) and run the command again. The Bourne shell dynamically allocates command line arguments. Return to your original shell by typing exit.

assertion failed: string, file name, line int

Cause

An unexoected condition in the program has happened.

Action

Contact the vendor or author of the program to ask why it failed. If you have the source code for the program, you can look at the file and line number where the assertion failed. This might give you an idea of how to run the program differently.

Technical Notes

This message results from a diagnostic macro called assert(3C) that a programmer inserted into the specified line of a source file. The expression that evaluated untrue precedes the file name and line number.

Attempting to link in more shared libraries than system limit

Cause

Trying to exec(2) an a.out that requires more static shared libraries than is allowed on the current configuration of the system.

Technical Notes

The symbolic name for this error is ELIBMAX, errno=86.

automountd[int]: server hostname responding

Cause

This automounter message indicates that the system tried to mount a filesystem from an NFS server that is either down or extremely slow to respond. In some cases this message indicates that the network link to the NFS server is broken, although that condition produces other error messages as well.

Action

If you are the system administrator responsible for the non-responding NFS server, check to see whether the machine needs repair or rebooting. Encourage your user community to report such problems quickly but only once. When the NFS server is back in operation, the automounter will be able to access the requested filesystem.

See Also

For more information on NFS failures, see the section on NFS troubleshooting in the NFS Administration Guide. If you are using the AnswerBook, a good search string is "NFS Service."

automount[int]: name: Not a directory

Cause

The file specified after the first colon is not a valid mount point because it is not a directory.

Action

Ensure that the mount point is a directory and not a regular file or a symbolic link.