Messages can appear in various places:
- Before the server code has been downloaded to the X station,
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 X station'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.
- Some messages appear on the TELNET screen.
To view the Log Screen once the server has started:
- Press and hold
[F12]
to access the configuration screens.
- Click on
[Diagnostics]
, then click on [Log Screen]
.
The Log Screen appears.
- Click on the
[Report]
button to select the desired reporting level for the
Log Screen.
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.
Messages with a message class less than
NOTICE
have been omitted.
Duplicate IP Address.
- The configured network address is being used
by another host.
Hardware failure --- Cannot access link address
- An EEPROM failure
-
The terminal's IP address is not in valid dotted decimal format.
-
Check the Network screen.
In fact, the address is in valid format, but has not been changed from its
factory default value of
0.0.0.0
.
-
Trying BOOTP....failed.
-
No computer responded to the X station's boot request.
The X station sends bootp requests every minute until successful or
until you press a key.
Bad file path specified:
path-
Bad font path:
path-
Boot failed.
-
Can't open
'filename':
-
Cannot resolve host name
'hostname'-
Config File Error:
-
Default cursor font failed:
font-
Default font failed:
font-
EEPROM error:
error- The EEPROM is defective.
Returning to factory defaults.
Action: type in configuration data.
EEPROM overflow: configuration not saved
- Too much configuration data
was specified to save in EEPROM.
Failed to load X Server:
hostname-
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 directory:
directory-
File server
'hostname' down or unreachable.
-
Font not found:
'font'-
Font path failed:
'path'-
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.
Invalid File Server.
-
Invalid File Server:
'hostname'-
Invalid or missing disk detected.
- A floppy disk was not found.
- taskname
: malloc(
num) failed
- Too little memory is available.
name server down or unreachable.
- A name server cannot be contacted with ping.
Name server not responding.
- A name server does not answer a name query.
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 Domain Name specified. Cannot configure name server.
-
No File Servers Specified.
-
No memory available for rp910
x printer task read buffer.
- 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 write buffer.
- x
is 0 for the first serial port, 1 for the parallel port, or 2 for the second serial
port.
- filename
: Not an extension file.
-
Not enough memory to start local client.
-
Not enough memory.
-
- extension
: Not found in database.
- No extension with the specified name exists.
Out of memory: local client terminated.
-
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.
- '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
.
PPP extension not loaded.
-
PPP initialization error (
description).
-
PPP option negotiation failed.
- Local and remote PPP
could not agree on a set of communication parameters.
- 'task
' routing task spawn failed.
-
SLIP initialization error (
description).
-
-
TELNET: No connection.
- TELNET could not open a connection to the
TELNET host. The TELNET host name/IP address is correct,
but the computer does not respond.
TELNET: Resolving host address ... unknown host.
- Check the Server and Network screens. This message
appears briefly if the TELNET host name cannot be resolved.
Likely causes are that the TELNET host does not appear in the
name server database, that the wrong IP address appears in the
Name Server field, or
that the wrong Domain Name appears in the Domain
Name field.
- extension
: Unable to load.
-
XDM: Declaring Session dead
-
Autodetected monitor/cable unsupported. Using default.
-
Cleared Alternate
var Link Level Address: 000000000000
- var
is
Ethernet
or Option
.
Default configuration used
- EEPROM has been cleared.
Invalid Alternate
var:
'altlla'- var is
either Ethernet or Option.
altlla is the alternate link-level address.
Less than
numKB of free memory.
-
Link level addresses writable!
-
Network cable fault detected.
- If the X station continues
to boot, this is not a serious problem.
Confirm the following:
- All X stations are connected to the LAN through a T-connector
- Each segment of the LAN ends with a 50-ohm terminator
- No section of a ThinLAN cable has a length that is a multiple of
5 meters
- The LAN cable does not have severe bends or kinks
- No segment of ThinLAN is longer than 185 m (600 ft.)
or shorter than 1 m (3 ft.).
Network cable not connected
var-
Network hardware fault: run selftests.
- To run self tests,
press
[F12]
and click on [Diagnostics]
, then
[Selftests]
.
No devices on HP-HIL, KEYBOARD or MOUSE ports
-
No EtherTwist hub detected.
-
Server ROM not installed.
- Check the Server screen.
The X station is configured
to get its X server from ROM, but there is no ROM server installed.
Unable to load log screen font: switching to English.
Some messages in log may be unreadable
- The
$LANG
variable
indicates that you are using a Japanese system, but the required Japanese font
could not be loaded.
English messages will be used instead of Japanese messages.
DHCP: Couldn't contact DHCP server while renewing address for
interface.
Broadcasting renewal request.
-
-
HIL Device detected: Unknown device
-
You have an unsupported keyboard or mouse plugged into the HP-HIL port.
Less than
numKB of free memory in largest fragment.
-
-
Mouse reset FAILED!
-
You have something other than a mouse plugged into the mouse port.
-
Name servers not responding.
-
Check the
General Network screen. The Name Servers specified are not responding.
X Server grabbed, can't start configuration
- Local configuration
could not start.
X Server Reset:
-
XDM: Too many retransmissions
-