Specifications

From Linux:
l Try editing the hosts file to include entries for the local host and the LifeKeeper
servers that it will be connected to.
On Windows 95/98 systems the hosts file is:
%windir%\HOSTS (for example, C:\WINDOWS\HOSTS).
Note: On Windows 95/98, if the last entry in the hosts file is not
concluded with a carriage-return/line-feed then the hosts file will not be
read at all.
On Windows NT systems the hosts file is:
%windir%\System32\DRIVERS\ETC\HOSTS
(for example,
C:\WINNT\System32\DRIVERS\ETC\HOSTS).
For example, if my system is called HOSTCLIENT.MYDOMAIN.COM
and uses IP address 153.66.140.1, add the following entry to the hosts
file:
153.66.140.1 HOSTCLIENT.MYDOMAIN.COM HOSTCLIENT
3. Try setting the hostname property to be used by the GUI client. To do this from a browser with
the Plugin, open the Java Plug-In Control Panel, and set the host name for the client by
adding the following to "Java Run Time Parameters":
Djava.rmi.server.hostname=<MY_HOST>
4. Check for Microsoft network-related patches at www.microsoft.com.
From Linux:
1. Verify communication with other servers by pinging the target server from Linux using its
hostname or IP address:
ping <TARGET_NAME>
For example:
ping homer
A reply listing the target's qualified hostname should be seen.
2. Verify that localhost is resolvable by each server in the cluster using ping with its hostname or
IP address. If DNS is not implemented, edit the /etc/hosts file and add an entry for the
localhost name. This entry can list either the IP address for the local server, or it can list the
default entry (127.0.0.1).
3. Check that DNS is specified before NIS. DNS should be put before NIS in the hosts line of
/etc/nsswitch.conf, and /etc/resolv.conf should point to a properly configured DNS server(s).
4. If DNS is not to be implemented or no other method works, edit the /etc/hosts file, and add an
entry for the hostname.
246Troubleshooting