In RHEL 8.0, Server Shutdown Strategy can not be changed from “Switch Over Resources” to “Do Not Switch Over Resources”
# openjdkdir=/opt/LifeKeeper/lib64/java # mkdir -p $openjdkdir # tar xzf /mnt/java/openjdk-12.0.2_linux-x64_bin.tar.gz -C $openjdkdir
Remove the OpenJDK path that is included with the OS from /etc/default/LifeKeeper PATH and add “/opt/LifeKeeper/lib64/java/jdk-12.0.2/bin” to the beginning of the path. Restart the LifeKeeper GUI server and the GUI client.
How to change /etc/default/LifeKeeper PATH.
GUI login prompt may not re-appear when reconnecting via a web browser after exiting the GUI
When you exit or disconnect from the GUI applet and then try to reconnect from the same web browser session, the login prompt may not appear.
Workaround: Close the web browser, re-open the browser and then connect to the server. When using the Firefox browser, close all Firefox windows and re-open.
GUI does not immediately update IP resource state after network is disconnected and then reconnected
When the primary network between servers in a cluster is disconnected and then reconnected, the IP resource state on a remote GUI client may take as long as 1 minute and 25 seconds to be updated due to a problem in the RMI/TCP layer.
Java Mixed Signed/Unsigned Code Warning – When loading the LifeKeeper Java GUI client applet from a remote system, the following security warning may be displayed:
Recommended Actions: To reduce the number of security warnings, you have two options:
steeleye-lighttpd process fails to start if Port 778 and 779 are in use
If a process is using Port 778 and 779 when steeleye-lighttpd starts up, steeleye-lighttpd fails which can cause GUI connect failiures and resource hierarchy extend issues.
Solution: Set the following tunables on all nodes in the cluster and then restart LifeKeeper on all the nodes:
where port_number is the new port to use.