Specifications
Samba Recovery Kit
Description
MD resource instances can be adversely impacted by udev processing during restore
During udev processing, device nodes are removed and recreated. Occasionally during a restore,
LifeKeeper will try to access a node before it has been recreated causing the restore to fail.
Solution: Perform the LifeKeeper restore action again.
Samba Recovery Kit
Description
The Samba Recovery Kit is currently not supported with SLES 11 SP2.
GUI Troubleshooting
If you are having problems configuring the LifeKeeper GUI from a remote system, see one of the
following topics:
Java Plug-In Troubleshooting
Applet Troubleshooting
Network-Related Troubleshooting (GUI)
Network-Related Troubleshooting (GUI)
LifeKeeper uses Java RMI (Remote Method Invocation) for communications between GUI clients
and servers. Some potential problems may be related to RMI, and others are general network
configuration problems.
Long Connection Delays on Windows Platforms
From Sun FAQ:
Most likely, your host's networking setup is incorrect. RMI uses the Java API networking classes, in
particular java.net.InetAddress, which will cause TCP/IP host name lookups for both host to address
mapping and address to hostname. On Windows, the lookup functions are performed by the native
Windows socket library, so the delays are not happening in RMI but in the Windows libraries. If your
host is set up to use DNS, then this could be a problem with the DNS server not knowing about the
hosts involved in communication, and what you are experiencing are DNS lookup timeouts. If this is
the case, try specifying all the hostnames/addresses involved in the file
\windows\system32\drivers\etc\hosts. The format of a typical host file is:
IPAddress Server Name
SteelEye Protection Suite for Linux243