Messages can appear in various places:
- Before the server code has been downloaded to the Netstation,
the boot screen displays messages.
- After the server code has been loaded,
the log screen records any messages generated by the X server
or the Netstation's hardware.
- You can use syslog message classes to filter messages in the log screen
and send them to one or more hosts.
For more information, see Filtering Log Messages.
Note that some messages are generated from ROM and cannot be forwarded.
To view the Log Screen once the server has started:
- Press and hold
[F12]
to access the configuration screens.
- Select
[Diagnostic]
, then [Log]
.
The Log screen appears.
- To view the syslog message classes, enable
[Classtag]
.
Note:
X Window System and operating system error messages also appear
on the boot screen
and the Log Screen.
These messages are documented elsewhere.
Refer to the following sections for a list of
important messages, organized by syslog message class.
Where appropriate, additional information for the message is provided.
Bad font path:
path- The font path is not accessible. Action: check path
and server for correct path and access permissions.
Cannot open file
'filename' because of too many open log files.
- Action: restart
the Netstation.
- 'device
' port read error in rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
device is
/dev/serial1
,
/dev/parallel
, or
/dev/serial2
.
- 'device
' port write error in rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
device is
/dev/serial1
,
/dev/parallel
, or
/dev/serial2
.
Failed to get main panel label text from catalog
- Localized message catalog not
available. Switching to English. Action: None required.
Failed to get sub panel label text from catalog
- Localized message catalog not
available. Switching to English. Action: None required.
Failed to get value of variable
'variable'
- Variable does not exist
in the Netstation database. Action: check to see if the extension or local client for
this variable is loaded.
Failed to open file
'filename'
- Unable to access file. Action:
check for existence and permissions on the host.
Failed to open
device driver for rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
device is
/dev/serial1
,
/dev/parallel
, or
/dev/serial2
.
Failed to open message catalog file
'filename'
- Unable to open the specific
message catalog. Defaulting to English only. Action: none required.
Host communications error in rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
Host connection attempt failed for rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
Network initialization failed for rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
No memory available for rp910
x printer task read/write buffer.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
Not enough memory.
- Not enough Netstation memory for all tasks. Action:
shut down some local clients to free up memory.
Peripheral device control error in rp910
x printer task.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
SLIP initialization error (
description).
- Action: attempt to restart
the SLIP session.
SLIP serial port I/O error (
description).
- Data error on SLIP session. Action:
restart the SLIP session.
syslogd: Error reading log device
'device'
- Action: restart syslogd.
syslogd initialization error.
- Action: restart syslogd.
Bad file path specified:
path- File path specified was incorrect. Action:
specify correct path.
-
DHCP: Couldn't contact DHCP server (on
interface). Broadcasting
renewal request.
-
No computer responded to the Netstation's boot request.
The Netstation sends DHCP requests every minute until successful or
until you press a key.
-
Error(s) Occurred while making gadget for screen
screen
- An internal
error occurred within the configuration utility. Action: restart the configuration
utility.
-
Log file
filename id already opened
- The log file is opened due to
a previous invocation of the logtofile extension.