 |
» |
|
|
|
Serious logging messages are issued after: ocd closes a connection or pseudonym
that has broken the communication path between the application and
the device. Unexpected conditions impact ocd
or other processes.
ERROR: Unable to
obtain data from network: system error <system_error>:
<system_message> | CAUSE: There was no data
to receive from the network due to the system error given. NOTE: This message is followed by messages
(296), (297), (298), and (299). NOTE: System error 232 - A transport
reset was received from the remote terminal server. System error
238 - A transport connection timeout was received from the remote
terminal server. ACTION: Determine if the terminal server
and device are operational and enable the printer or restart the
application if they are. |
ERROR: Binary negotiation
failed on opening connection | CAUSE: The binary negotiation
was not completed successfully on opening a connection to the device
on the remote terminal server. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device can accept binary data and restart the application if
they can. |
ERROR: Invalid initial
status request received | CAUSE: The initial status
request to the device on the remote terminal server failed. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device are operational and restart the application if they are. |
ERROR: Connection
failed | CAUSE: A connection to the
remote terminal server was not made. NOTE: This message is followed by messages
(296), (297), and (298). ACTION: Determine if the terminal server
and device are operational and enable the printer or restart the
application if they are. |
ERROR: Invalid terminating
status request received | CAUSE: The final status
request to the device on the remote terminal server failed. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device are operational and restart the application if they are. |
ERROR: Give up trying
to obtain connection as number of open connection tries has been
exhausted | CAUSE: The number of tries
to open a connection to the device on the remote terminal server
was exhausted. NOTE: This message is followed by messages
(296), (297), and (298). ACTION: Determine if the terminal server
and device are operational and enable the printer or restart the
application if they are. |
ERROR: Unable to
obtain timing mark negotiation from network: system error <system_error>:
<system_message> | CAUSE: There was no timing
mark negotiation to receive from the network due to the system error
given. NOTE: This message is followed by message
(298). ACTION: Determine if the terminal server
and device are operational and enable the printer if they are. |
ERROR: No timing
mark negotiation to obtain from network within time interval allowed | CAUSE: There was no data
and thus no timing mark negotiation to receive from the network
during the time to wait for such negotiations (most likely because
of the load on the terminal server, network, or system). NOTE: This message is followed by message
(298). ACTION: Determine if the terminal server
and device are operational and enable the printer if they are. |
ERROR: No timing
mark negotiation received in data during time interval allowed | CAUSE: There was no timing
mark negotiation in the data received from the remote terminal server. NOTE: This message is followed by message
(298). ACTION: Enable the printer. |
ERROR: Unable to
obtain status reply from device: system error <system_error>:
<system_message> | CAUSE: There was no status
reply to receive from the network due to the system error given. NOTE: This message is followed by messages
(296), (297), (298), and (299). ACTION: Determine if the terminal server
and device are operational and enable the printer or restart the
application if they are. |
ERROR: No status
reply to obtain from device within time interval allowed | CAUSE: There was no data
and thus no status reply to receive from the network during the
time to wait for that status reply (most likely because of the load
on the terminal server, network, or system). NOTE: This message is followed by messages
(296), (297), (298), and (299). ACTION: Determine if the terminal server
and device are operational and enable the printer or restart the
application if they are. |
ERROR: Printer busy | CAUSE: The printer on the
remote terminal server was busy with another request. ACTION: Wait for the printer to free
up before sending the next printer request. |
ERROR: Printer out
of paper | CAUSE: The printer on the
remote terminal server was out of paper. ACTION: Add paper to the printer, put
it on-line, and send the printer request. |
ERROR: Printer off-line | CAUSE: The printer on the
remote terminal server was off-line. ACTION: Put printer on-line and send
the printer request. |
ERROR: Printer data
error | CAUSE: The printer on the
remote terminal server had a data error. NOTE: This message is followed by messages
(296), (297), (298), and (299). ACTION: Determine if the printer is
operational and enable printer and send the printer request if it
is. |
ERROR: Unknown status
reply <status_reply> | CAUSE: No known status reply
was received in the data from the device on the remote terminal
server. ACTION: Refer to the manual for the
device for an explanation of the status reply. |
ERROR: Printer problem
not fixed within time interval allowed | CAUSE: The printer on the
remote terminal server was not made ready during the time to wait
for a status reply. NOTE: This message is followed by messages
(296), (297), (298), and (299). ACTION: Put printer on-line, enable
printer, and send the printer request. |
ERROR: Unable to
obtain binary negotiation from network: system error <system_error>:
<system_message> | CAUSE: There was no binary
negotiation to receive from the network due to the system error
given. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device are operational and restart the application if they are. |
ERROR: No binary
negotiation to obtain from network within time interval allowed | CAUSE: There was no data
and thus no binary negotiation to receive from the network during
the time to wait for such negotiations (most likely because of the
load on the terminal server, network, or system). NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device are operational and restart the application if they are. |
ERROR: Binary negotiation
not completed on time | CAUSE: There was no binary
negotiation in the data received from the remote terminal server. NOTE: This message is followed by message
(296), (297), and (299). |
ERROR: Received SIGUSR2
signal | |
ERROR: Give up trying
to obtain connection at request of user | CAUSE: Ocd or ocdebug received
a SIGUSR2 signal and any more tries to open a connection to the
device on the remote terminal server were stopped. ACTION: Determine if the terminal server
and device are operational and restart the application if they are. |
Messages Commonly Seen with Non-Standard (User-Written)
Applications | |
ERROR: Control device
request rejected as connection not open | CAUSE: A control device
request was received before an open request was received and after
a close request was received. NOTE: This message is followed by messages
(296) and (297). ACTION: Have all control device requests
for a pseudonym sandwiched between an open request for that pseudonym
and a close request for that pseudonym. |
ERROR: Unable to
obtain control device request argument: system error <system_error>:
<system_message> | CAUSE: The parameters to
set for a set parameters control device request could not be obtained
due to the system error given. ACTION: Determine if the correct structure
(termio) is used and the correct parameters are being set and make
any changes necessary. |
ERROR: Unable to
toggle binary mode off | CAUSE: The binary mode was
not turned off successfully. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device are operational and whether binary mode can be toggled
off for the terminal server and restart the application if all conditions
are met. |
ERROR: Unable to
toggle binary mode on | CAUSE: The binary mode was
not turned on successfully. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
and device are operational and whether binary mode can be toggled
off for the terminal server and restart the application if all conditions
are met. |
ERROR: Unable to
obtain send break request argument: system error <system_error>:
<system_message> | CAUSE: The parameter for
a send break control device request could not be obtained due to
the system error given. ACTION: Determine if the correct structure
(termio) is used and the correct parameters are being set and make
any changes necessary. |
ERROR: Unable to
obtain flow control request argument: system error <system_error>:
<system_message> | CAUSE: The parameter for
a flow control device request could not be obtained due to the system
error given. ACTION: Determine if the correct structure
(termio) is used and the correct parameters are being set and make
any changes necessary. |
ERROR: Give up trying
to obtain connection as connection already established | CAUSE: A connection to the
device on the remote terminal server was already established. ACTION: Establish only one connection
for each device on a remote terminal server. |
ERROR: DO binary
negotiation rejected by remote side | CAUSE: The idea of binary
mode data transfers was rejected by the remote terminal server. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if binary mode can
be toggled on for the terminal server and restart the application
if it can. |
ERROR: DONT binary
negotiation rejected by remote side | CAUSE: The idea of non-binary
mode data transfers was rejected by the remote terminal server. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if binary mode can
be toggled off for the terminal server and restart the application
if it can. |
ERROR: Unable to
obtain data from network or pty | CAUSE: There were no data
or events to be passed on the network or through the pseudonym due
to a system error. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Restart ocd or ocdebug and
restart the application. |
ERROR: Unable to
obtain data: system error <system_error>: <system_message> | CAUSE: There were no data
or events to be passed on the network or through the pseudonym due
to the system error given. ACTION: Look up what the select(2)
man page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
obtain data from pty: system error <system_error>: <system_message> | CAUSE: There were no data
to receive from the pty due to the system error given. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Look up what the read(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
obtain request information from pty: system error <system_error>:
<system_message> | CAUSE: There was no control
request data to receive from the pty due to the system error given. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Look up what the ioctl(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unknown Telnet
state <telnet_state> | CAUSE: A Telnet state discovered
while processing a Telnet command was not a known Telnet state. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
is using the Telnet protocol correctly and restart the application
if it is. |
ERROR: Unknown internal
parameter in port configuration file | CAUSE: The internal port
configuration parameter discovered while processing the port configuration
file is not a known parameter. ACTION: No action. |
ERROR: Give up trying
to obtain connection: system error <system_error>: <system_message> | CAUSE: Any more tries to
open a connection to the device on the remote terminal server were
stopped due to the system error given. NOTE: This message is followed by messages
(296), (297), and (298). ACTION: Look up what the connect(2)
man page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
obtain out-of-band data: system error <system_error>: <system_message> | CAUSE: There was no out-of-band
data to receive from the network due to the system error given. ACTION: Look up what the select(2)
man page states about the system error given and make the correction
as appropriate. |
ERROR: No timing
mark negotiation to obtain from network | CAUSE: Unexpected data was
received from a place other than the network before there was a
timing mark negotiation to receive from the network. NOTE: This message is followed by message
(298). ACTION: Enable the printer and send
the printer request. |
ERROR: Unable to
read timing mark negotiation from network: system error <system_error>:
<system_message> | CAUSE: There was no timing
mark negotiation to read from the network due to the system error
given. NOTE: This message is followed by message
(298). ACTION: Look up what the read(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unknown Telnet
state <telnet_state> during timing mark negotiation | CAUSE: A Telnet state discovered
while processing a Telnet timing mark negotiation was not a known
Telnet state. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Determine if the terminal server
is using the Telnet protocol correctly and restart the application
if it is. |
ERROR: Unable to
read status reply from device: system error <system_error>:
<system_message> | CAUSE: There was no status
reply to read from the network due to the system error given. NOTE: This message is followed by messages
(296), (297), (298), and (299). ACTION: Look up what the read(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: No status
reply to obtain from device | CAUSE: Unexpected data was
received from a place other than the network before there was a
status reply to receive from the network. NOTE: This message is followed by messages
(296), (297), (298), and (299). ACTION: Restart the application, enable
the printer, and send the printer request. |
ERROR: No binary
negotiation to obtain from network | CAUSE: Unexpected data was
received from a place other than the network before there was a
binary negotiation to receive from the network. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Restart the application. |
ERROR: Unable to
read binary negotiation from network: system error <system_error>:
<system_message> | CAUSE: There was no binary
negotiation to read from the network due to the system error given. NOTE: This message is followed by message
(296), (297), and (299). ACTION: Look up what the read(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
get terminal parameters: system error <system_error>: <system_message> | CAUSE: There were no device
file parameters to obtain from the pty due to the system error given. ACTION: Look up what the ioctl(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
set terminal parameters: system error <system_error>: <system_message> | CAUSE: The device file parameters
were not set on the pty due to the system error given. ACTION: Look up what the ioctl(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
write data to pty: system error <system_error>: <system_message> | CAUSE: There were no data
to send to the pty due to the system error given. ACTION: Look up what the write(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
write data to network: system error <system_error>: <system_message> | CAUSE: There were no data
to send to the network due to the system error given. ACTION: Look up what the send(2) man
page states about the system error given and make the correction
as appropriate. |
ERROR: Unable to
delete pseudonym <pseudonym_name> for recreation and use:
system error <system_error>: <system_message> | CAUSE: The pseudonym was
not deleted due to the system error given. ACTION: Delete the pseudonym and restart
ocd or ocdebug. |
ERROR: System returned
error <return_error> while disabling printer: system error
<system_error>: <system_message> | CAUSE: The disable command
had an error as given. This does not affect the disabling of the
printer queue. ACTION: No immediate action is necessary
although enabling the Unix spooler printer queue in the future is
required to restart the printing process for that printer queue. |
Message(s) that Accompany Some Serious Error Messages | |
ERROR: Recreating
pseudonym <pseudonym_name> with new pty | CAUSE: The pseudonym was
recreated and linked to a new pty opened for it. NOTE: This message accompanies messages
(200), (201), (202), (203), (204), (205), (209), (210), (214), (216),
(217), (218), (219), (222), (224), (225), (229), (230), (250), (252),
(253), (254), (256), (260), (261), (262), (263), and (264). ACTION: No action is necessary. |
ERROR: Removing pseudonym
<pseudonym_name> and closing pty <master_pty_name> | CAUSE: The pseudonym was
deleted and its associated pty was closed due to a serious error
with the pseudonym. NOTE: This message accompanies messages
(200), (201), (202), (203), (204), (205), (209), (210), (214), (216),
(217), (218), (219), (222), (224),(225), (229), (230), (250), (252),
(253), (254), (256), (260), (261), (262), (263), and (264). NOTE: This message is followed by message
(432). ACTION: No action is necessary. |
ERROR: Printer disabled | CAUSE: The Unix spooler
printer queue associated with the outbound connection daemon was
disabled. NOTE: This message accompanies messages
(200), (203), (205), (206), (207), (208), (209), (210), (214), (216),
(256), (258), (259), (261), and (262). ACTION: No immediate action is necessary
although enabling the Unix spooler printer queue in the future is
required to restart the printing process for that printer queue. |
ERROR: Closing connection
due to error with data path | CAUSE: The connection to
the device on the remote terminal server was closed due to a serious
error with the connection or with the pseudonym. NOTE: This message accompanies messages
(200), (201), (202), (204), (209),(210), (214), (216), (217), (218),
(219), (224), (225), (229), (230), (250), (252), (253), (254), (260),
(261), (262), (263), and (264). ACTION: No action is necessary. |
|
