"O"

Object is remote

Cause

This error occurs when users try to share a resource that is not on the local machine, or try to mount/unmount a device or path name that is on a remote machine.

Technical Notes

The symbolic name for this error is EREMOTE, errno=66.

ok

Cause

This is the OpenBoot PROM monitor prompt. From this prompt, you can boot the system (from disk, CD-ROM, or net), or you can use the go command to continue where you left off.

Action

If you suddenly see this prompt, look at the messages above it to see if the system crashed. If no other messages appear, and you just typed Stop-A or plugged in a new keyboard, type go to continue. You might need to Refresh the window system from its Workspace Menu.

Technical Notes

Never invoke sync from the ok prompt without first running the fsck(1M) command, especially if the filesystem has changed.

Operation already in progress

Cause

An operation was attempted on a non-blocking object that already had an operation in progress.

Technical Notes

The symbolic name for this error is EALREADY, errno=149.

Operation canceled

Cause

The associated asynchronous operation was canceled before completion.

Technical Notes

The symbolic name for this error is ECANCELED, errno=47.

operation failed [error 185], unknown group error 0, string

Cause

When you use admintool to add a user to a newly-created group, admintool issues this error.

Action

Apply patch 101384-05 to fix bug ID 1151837 and to provide a workaround for bug ID 1153087.

Operation not applicable

Cause

This error indicates that no system support exists for some function that the application requested.

Action

Ask the system vendor for an upgrade, or contact the vendor or author of the application for an update.

Technical Notes

This message indicates that no system support exists for an operation. Many modules set this error when a programming function is not yet implemented. If you are writing a program that produces this message while calling a system library, try to find and use an alternative library function. Future versions of the system might support this operation; check system release notes for further information.

The symbolic name for this error is ENOSYS, errno=89.

Operation not supported on transport endpoint

Cause

For example, trying to accept a connection on a datagram transport endpoint.

Technical Notes

The symbolic name for this error is EOPNOTSUPP, errno=122.

Operation now in progress

Cause

An operation that takes a long time to complete (such as a connect) was attempted on a non-blocking object.

Technical Notes

The symbolic name for this error is EINPROGRESS, errno=150.

/opt/bin/jws: /solaris/bin/locate_dirs: not found

Cause

This error message occurred when the customer used the link from /opt/bin/jws to /opt/SUNWjws/JWS/sparc-S2/bin/jws, to start Java Workshop. Typing in the full pathname works fine, typing jws gives the error.

Action

This happens because /opt/bin/jws is not /opt/SUNWjws/JWS/sparc-S2/bin/jws, which a script that runs another script: $_SS_JWS_HOME/solaris/bin/locate_dirs.

So whatever /opt/bin/jws is, it is not setting $_SS_JWS_HOME correctly. Take that out of your path and put /opt/SUNWjws/JWS/sparc-S2/bin/jws in your path so which jws returns: /opt/SUNWjws/JWS/sparc-S2/bin/jws.

Option not supported by protocol

Cause

A bad option or level was specified when getting or setting options for a protocol.

Technical Notes

The symbolic name for this error is ENOPROTOOPT, errno=99.

out of memory

Cause

Hundreds of different programs can produce this message when the system is running many large applications simultaneously. This message usually means that the system has run out of swap space (virtual memory).

Action

See the message "Not enough space" for details. Any data written during this condition will probably be lost.

Out of stream resources

Cause

During a STREAMS open, either no STREAMS queues or no STREAMS head data structures were available. This is a temporary condition; one may recover from it if other processes release resources.

Technical Notes

The symbolic name for this error is ENOSR, errno=63.

overlapping swap volume

Cause

After creating volumes in rootdg to be used as additional swap and adding these to the /etc/vfstab file, an error message is displayed at boot time complaining about overlapping swap volumes.

Action

Change the names of these volumes to read swap1, swap2, etc...

If you still get this message after making the above change, edit the /sbin/swapadd script. Find the line:

c=`$SWAP -l | grep -c '\\<'${special}'\>'`

and change it to

=`$SWAP -l | grep -c ''${special}''`

Also see bug number 1215062 for more information on this behavior.