ERRNET(2) — Series 300, 500, and 800 Only
NAME
errnet − indicate network errors
SYNOPSIS
extern int errnet;
DESCRIPTION
Errnet is an external variable whose value is set whenever a remote file access error occurs. The value can be used to obtain a description of the error. The value of errnet should be checked whenever an error occurs and errno has the value [ENET].
The following list describes the errnet values and their names and meanings:
256 NE_INTERNAL
Internal error. This may indicate that either rfa or bsdipc is not configured in the kernel. Requires HP notification.
257 NE_NETSTATE
1. Network needs to be powered up before a request can be fulfilled.
2. Network is already powered up and cannot be powered up again without re-booting the system.
Returned to Series 300 and 500 systems only.
258 NE_BADFILE
Network file is bad.
259 NE_HARDWARE
Hardware failure. The failure could be in the HP-IB card connected to the 2285A LAN Unit, in the LAN Interface, in the transceiver, or in any of the cables.
The network may have been powered up with the wrong or a non-existent LAN Interface card.
Returned to Series 300 and 500 systems only.
261 NE_TIMEOUT
A LAN operation has timed out.
For some IPC, NetIPC, and diagnostic operations, you can set the timeout value. If this error occurs, check to see if the other system is up, and if a corresponding IPC or NetIPC process on the remote system exists.
262 NE_PROTOVIOL
Network protocol violation has occurred. If this error occurs frequently, it requires HP notification.
263 NE_NOSERV
Requested service is not supported.
264 NE_NOREMOTE
Series 300: Remote node does not respond to a connection request. Series 500 and 800: Specified remote system cannot be found.
The node may not be powered up or connected to the network.
265 NE_CONNLOST
Connection to a remote system was lost or aborted by the other system.
The other system may have shut down.
266 NE_NOCONNECT
1. IPC connection attempt failed.
2. Source system for a network file transfer cannot make the specified connection.
Returned to Series 300 and 500 systems only.
271 NE_RSRCREM
1. Not enough available memory on a remote system.
2. Network memory limit on the remote system was exceeded.
Returned to Series 300 and 500 systems only.
272 NE_NOLOGIN
Specified login is invalid.
Returned to Series 300 and 500 systems only.
273 NE_NOUSERS
Limit for network service instances on the local system was exceeded.
300 NE_DUPNAME
Specified name already exists for a source socket. This error may indicate that a process is still running and an attempt was made to run another copy of the process.
Returned to Series 300 and 500 systems only.
301 NE_NONAME
Name specified for uipclookup could not be found. This error may indicate that the corresponding process is not executing or has not yet named its source socket.
Returned to Series 300 and 500 systems only.
302 NE_SOCKDIED
Virtual circuit connection was aborted.
Returned to Series 300 and 500 systems only.
303 NE_CANTNAME
An attempt was made to name a virtual circuit socket.
Returned to Series 300 and 500 systems only.
304 NE_CONNPEND
Request for an IPC connection was made but has not yet been accepted.
Returned to Series 300 and 500 systems only.
305 NE_DONTOWN
A process attempted to erase the name of a socket that it did not own.
Returned to Series 300 and 500 systems only.
306 NE_NONBLOCK
The IPC intrinsic could not complete without suspending execution of the current process. This situation results in an error if the socket has been set to non-blocking mode with uipccontrol.
Returned to Series 300 and 500 systems only.
350 NE_BADPROG
A program specified by a urpmcreate call could not be executed for one of the following reasons:
1. Specified pathname is invalid.
2. User specified by the login parameter does not have execute permission.
3. File does not have a valid magic number. This may mean that the specified file is a shellscript or can only be executed on different hardware.
4. File is currently open for writing.
5. An I/O error occurred while attempting to load the file.
Returned to Series 300 and 500 systems only.
DEPENDENCIES
Implemented on Series 300, 500, and 800 only.
AUTHOR
HP
SEE ALSO
Hewlett-Packard Company — May 11, 2021