268 Chapter 5: Application Module and IPE Module error messages
Table 12
Application messages that appear in the SysLog file (continued)
Message
hlinkHDLC: read (conf) - errno
='UNIX error number'
hlinkHDLC: ldatq( ) - errno
='UNIX error number'
hlnkHDLC: msgget( ) - errno
='UNIX error number'
hlnkHDLC error in wait_msg_q( )
- errno ='UNIX error number'
hlnkHDLC: above event not
processed
hlnkHDLC: write to trace file
failed
hlnkHDLC: bad event:'event
number' - state:'state number'
hlnkHDLC: 'file name': can't open
hlnkHDLC: invalid ipc state sent
from Mlink
553-3211-510 Standard 1.0 October 1998
Description
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
This message is normally generated when the
application is started, and should be ignored.
There is a problem writing to the trace file for link 1.
The file system may be full. Log in as maint and enter
diskuse. Refer to the filedelete command if the disk
usage is greater than 95 percent. If the file system is
not full, restart the trace by logging in as mlusr and
using untrace link 1 followed by trace link 1.
It is normal for this message to appear when the
application is started. If it appears any other time, it
indicates an internal application problem. Use
Procedure 2: SBC restart.
There is a problem opening the trace file for link 1.
The file system may be full. Log in as maint and use
the diskuse command. Refer to the filedelete
command if the disk usage is greater than 95 percent.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Ñ continued Ñ