 |
» |
|
|
|
Warning logging messages are issued when an unexpected condition
occurs that does not affect normal operation of ocd
or other processes. Usage messages are caused by syntax errors. USAGE MESSAGE: ocd:
unknown option: <option> (ignored) | CAUSE: The option given
was not a valid option. ACTION: Remove the option from the
command line. |
WARNING: Invalid
logging level <log_level> (valid values are 0, 1, 2, or
3) | CAUSE: The logging level
given was not 0, 1, 2, or 3. ACTION: Use a logging level of 0, 1,
2, or 3. |
WARNING: Port configuration
file not specified or not specified correctly | CAUSE: The -c option was
not specified. NOTE: This message is followed by message
(350). ACTION: Use a correct configuration
file name. |
WARNING: Timing mark
negotiation disabled because Telnet mode disabled | CAUSE: Timing mark negotiation
was enabled but the Telnet mode was disabled. ACTION: Either enable the Telnet mode
or disable the timing mark negotiation. |
WARNING: Pseudonym
<pseudonym_name> not specified in /dev/telnet | CAUSE: The pseudonym specified
was not to be placed into the directory /dev/telnet set aside for
all pseudonyms. ACTION: Place all pseudonym names in
/dev/telnet. |
WARNING: Unable to
change permissions of pseudonym <pseudonym_name> to <permission>:
system error <system_error>: <system_message> | CAUSE: The permissions of
the pseudonym were not changed to optimal values (0666) due to the
system error given. ACTION: Look up what the chmod(2) man
page states about the system error given and make the correction
as appropriate. |
WARNING: Unable to
enable packet mode on pty: system error <system_error>:
<system_message> | CAUSE: Packet mode on the
pty could not be enabled 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. |
WARNING: Unable to
enable non-blocking mode on pty: system error <system_error>:
<system_message> | CAUSE: Non-blocking mode
on the pty could not be enabled 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. |
WARNING: Application
canceled open request | CAUSE: The application closed
the pty before the open request had completed. ACTION: Restart the application. |
WARNING: Unable to
enable non-blocking mode on network socket: system error <system_error>:
<system_message> | CAUSE: Non-blocking mode
on the network could not be enabled 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. |
WARNING: Close not
completed as data processing not complete | CAUSE: There was still data
to send to the device on the remote terminal server as the close
was requested. ACTION: No action is necessary. |
WARNING: Close request
ignored as connection not open | CAUSE: The close request
was received and ignored as the connection was not open. This occurred
because of an application sending a close request at the wrong time
or because of an error that previously closed the connection. ACTION: Generally, no action is necessary
unless a close request is not sent after an open request. |
WARNING: Binary mode
cannot be turned off as permanently turned on | CAUSE: The application requested
that the binary mode be turned off when the binary mode is turned
on for the connection using the port configuration file and thus
cannot be turned off. ACTION: Determine if the binary mode
is necessary at all times and disable it if it is not. |
WARNING: Unable to
perform flush operation | CAUSE: The application requested
a flush operation and ocd and ocdebug do not support that operation. ACTION: Determine if a flush operation
is necessary by the application and do not perform it if it is not. |
WARNING: Cannot open
port configuration file: system error <system_error>: <system_message> | CAUSE: The open of the port
configuration file failed due to the system error given. NOTE: This message is followed by message
(350). ACTION: Verify the port configuration
file name, location, and permissions. |
WARNING: Unknown
parameter <parameter_name> in port configuration file (ignored) | CAUSE: The port configuration
parameter specified is not valid and has been ignored. ACTION: Verify the port configuration
parameter name. |
WARNING: Unable to
set keep alive option on network socket: system error <system_error>:
<system_message> | CAUSE: The keep alive option
on the network could not be set due to the system error given. ACTION: Look up what the setsockopt(2)
man page states about the system error given and make the correction
as appropriate. |
WARNING: Unable to
set option on network socket as unable to obtain protocol attributes:
system error <system_error>: <system_message> | CAUSE: The no delay option
on the network could not be set as the protocol could not be obtained
due to the system error given. ACTION: Look up what the getprotobyname(3N)
man page states about the system error given and make the correction
as appropriate. |
WARNING: Unable to
set no delay option on network socket: system error <system_error>:
<system_message> | CAUSE: The no delay option
on the network could not be set due to the system error given. ACTION: Look up what the setsockopt(2)
man page states about the system error given and make the correction
as appropriate. |
WARNING: Unable to
reply to control device request: system error <system_error>:
<system_message> | CAUSE: The control device
reply to the control device request could not complete due to the
system error given. A reply is made for each request sent by an
application and must be made for the application to continue. ACTION: Look up what the ioctl(2) man
page states about the system error given and make the correction
as appropriate. |
WARNING: Unable to
obtain negotiation from network: system error <system_error>:
<system_message> | CAUSE: There was no Telnet
negotiation 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. |
WARNING: No negotiation
to obtain from network within time interval allowed | CAUSE: There was no data
and thus no Telnet 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). ACTION: Determine if the terminal server
and device are operational and make them operational if they are
not. |
WARNING: Unable to
read negotiation from network: system error <system_error>:
<system_message> | CAUSE: There was no Telnet
negotiation to read from the network due to the system error given. ACTION: Look up what the read(2) man
page states about the system error given and make the correction
as appropriate. |
WARNING: No negotiation
to obtain from network | CAUSE: Unexpected data was
received from a place other than the network before there was a
Telnet negotiation to receive from the network. ACTION: No action is necessary. |
WARNING: No status
reply from device | CAUSE: No status reply was
received in the data from the device on the remote terminal server. ACTION: No action is necessary. |
WARNING: Status reply
received <number_of_characters> characters | CAUSE: A status reply of
more than one character was received in the data from the device
on the remote terminal server. ACTION: No action is necessary. |
WARNING: Unable to
send interrupt signal to application: system error <system_error>:
<system_message> | CAUSE: An interrupt could
not be sent to the application 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. |
WARNING: Unable to
send break to application: system error <system_error>:
<system_message> | CAUSE: A break could not
be sent to the application 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. |
WARNING: Unable to
write <number_of_bytes> bytes to pty | CAUSE: An attempt to write
all data to the pty failed because the pty had no room for the amount
of data specified. ACTION: Determine if the application
is running correctly and draining data from the pty regularly and
restart the application if it is not. |
WARNING: Unable to
write <number_of_bytes> bytes of normal data to network | CAUSE: An attempt to write
all data to the network failed because the network had no room for
the amount of data specified. ACTION: Determine if the network, terminal
server, and device are running correctly and draining data regularly
and correct the situation as necessary. |
WARNING: Unable to
write <number_of_bytes> bytes of urgent data to network | CAUSE: An attempt to write
all data to the network failed because the network had no room for
the amount of data specified. ACTION: Determine if the network, terminal
server, and device are running correctly and draining data regularly
and correct the situation as necessary. |
WARNING: Unable to
obtain information concerning existence of pseudonym <pseudonym_name>:
system error <system_error>: <system_message> | CAUSE: There was no information
available for the pseudonym specified due to the system error given. ACTION: Look up what the stat(2) man
page states about the system error given and make the correction
as appropriate. |
WARNING: Unable to
delete pseudonym <pseudonym_name> when terminating daemon:
system error <system_error>: <system_message> | CAUSE: The pseudonym was
not deleted due to the system error given. ACTION: Delete the pseudonym. |
WARNING: Unknown
logging level | CAUSE: A log message with
an unknown logging level was encountered. ACTION: No action is necessary. |
Message(s) that Accompany Some Warning Messages | |
WARNING: Using default
port configuration values | CAUSE: The hard-coded default
port configuration values were invoked for use as the port configuration
file could not be used due to the warning given in the accompanying
message (either message (301) or message (313)). ACTION: No action is necessary. |
|
