SIOS TECHNOLOGY CORP.

GUI – Known Issues / Restrictions

Description
Resource Hierarchy Creation menu may show uninstalled resource types

Symptom: Resource types may continue to appear as choices in the LifeKeeper Java GUI “Create Resource Hierarchy” operation after the corresponding recovery kit has been uninstalled.

Solution: Close the LifeKeeper Java GUI, restart the Java GUI server (/opt/LifeKeeper/bin/lkGUIserver restart) in order to update the list of available resource types, then reopen the Java GUI.
Using source address routing with IP resources can impact the GUI

Using source address routing with IP resources can impact the GUI’s ability to properly display the resource status when performing a switchover. The resource status can end up being displayed as failed or unknown when in fact the switchover completed without a problem.

Solution:

To resolve the issue, exit the GUI and restart it.
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:
  1. Check the “Always trust content from this publisher” box and select “Run”. The next time the LifeKeeper GUI Java client is loaded, the warning message will not be displayed.

    or

  2. Add the following entry to your Java “deployment.properties” file to eliminate the second dialog about blocking. The security warning will still be displayed when you load the Java client, however, the applet will not be blocked and the Block “Yes” or “No” dialog will not be displayed. Please note this setting will apply to all of your Java applets.
    deployment.security.mixcode=HIDE_RUN

    To bypass both messages, implement 1 and 2.
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:

API_SSL_PORT=port_number
LKAPI_WEB_PORT=port_number

where port_number is the new port to use.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment