| 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:
Enter “Run” and the following dialog will be displayed:
Block? Enter “No” and the LifeKeeper GUI will be allowed to operate.
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:
Add the following lines to /etc/default/LifeKeeper:
where port_number is the new port to use.
Thanks for your feedback.