Nortel Meridian Meridian 1 Maintenance Manual page 285

Table 12
Application messages that appear in the SysLog file (continued)
Message
hlinklan: bind( ) Ð errno = ÔUNIX
error numberÕ
hlinklan: fcntl( ) Ð errno = ÔUNIX
error numberÕ
hlinklan: socket read error Ð
errno = ÔUNIX error numberÕ
hlinklan: socket write error Ð
errno = ÔUNIX error numberÕ
hlinklan: bad header ie rcvd on
tcp link
hlinklan: msg receive retry limit
exceeded
hlinklan: msg send retry limit
exceeded
hlinklan: assoc_id already in use
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Chapter 5: Application Module and IPE Module error messages 273
Description
This message can occur during a bind( ) function
operation which indicates a critical error, meaning that
the bind operation failed.
This message can occur during an fcntl( ) operation
which performs some type of file control on a socket
file descriptor.
This message can occur during a socket read
operation which indicates that an error occurred
during this operation.
This message can occur during a socket write
operation which indicates the byte data being written
could not be sent.
This message can occur during meridian link message
validation. It indicates that a bad header IE was
received, meaning that the byte pattern 0xff 0x0a was
not seen in the message header.
This message can occur during a socket read
operation. If the whole message cannot be read within
a maximum retry limit, then the message receiving
process is stopped and a log error message is
produced.
This message can occur during a socket write
operation. If the whole message cannot be written on
a socket fd within a maximum retry limit, then the
message sending process is stopped and a log error
message is produced.
This message can occur during the application
registration process, which indicates that the
association id given from the tsmain process is
already in use.
Ñ continued Ñ