Specifications

Unable to Connect to X Window Server:
5. Try setting the hostname property to be used by the GUI client. This will need to be changed
for each administrator.
To do this from a browser with the Plugin, open the Java Plug-In Control Panel and set the
hostname for the client by adding the following to "Java Run Time Parameters":
-Djava.rmi.server.hostname=<MY_HOST>
To do this from the HotJava browser, append the following to the hotjava command line:
-Djava.rmi.server.hostname=<MY_HOST>
For Example:
-Djava.rmi.server.hostname=153.66.140.1
-Djava.rmi.server.hostname= homer.somecompany.com
Unable to Connect to X Window Server:
When running the LifeKeeper GUI application from a telnet session, you need to ensure that the GUI
client is allowed to access the X Window Server on the LifeKeeper server. The LifeKeeper server
must also be able to resolve the hostname or network address of the GUI client.
When you telnet into the LifeKeeper server to run the LifeKeeper GUI application, the DISPLAY
environment variable should contain the client's host name and display number. For example, if you
telnet into a server named Server1 from a client named Client1, the DISPLAY environment variable
should be set to Client1:0. When you run the LifeKeeper GUI application, it will try to send the output
to the DISPLAY name for Client1. If Client1 is not allowed access to the X Window Server, the
LifeKeeper GUI application will fail with an exception.
When starting the LifeKeeper GUI as an application, if an error occurs indicating that you cannot
connect to the X Window Server or that you cannot open the client DISPLAY name, try the following:
1. Set the display variable using the host name or IP address. For example:
DISPLAY=Client1.somecompany.com:0
DISPLAY=172.17.5.74:0
2. Use the xhost or xauth command to verify that the client may connect to the X Window
Server on the LifeKeeper server.
3. Add a DNS entry for the client or add an entry for the client to the local hosts file on the
LifeKeeper server. Verify communication with the client by pinging the client from the
LifeKeeper server using its hostname or IP address.
Adjusting the System Date and Time
Changing the system date/time backwards while in multi-user mode can cause trouble with
LifeKeeper. The SCSI ha_xref_tbl is used during resource management. If the date or time is
changed to an earlier time value, management of resources with timestamps later than the new time
can be frozen until the new time catches up to the point where it was when the ha_xref_tbl was built.
SteelEye Protection Suite for Linux247