Known issues and problems

Share difficulties when a host is blocked

When two or more consumers are set to share resources and one of those shared resources is added to the blocked host list for one consumer, the other consumer also cannot use it.

To avoid or fix this problem, frequently monitor the blocked hosts list and unblock the hosts regularly. To unblock a host, you must fix the problem on the host that caused it to become blocked.

Cannot shutdown EGO if the master does not recognize the compute host

If the master host does not recognize the compute host for any reason, you cannot shutdown EGO (run egosh ego shutdown). You receive the following message:

Shut down LIM on <host_name> ...... ls_limcontrol: Operation permission denied by LIM.

Debug always turned on for Web Services Gateway

In $EGO_CONFDIR/kernel/conf/wsg.conf, the parameter WSG_DEBUG_DETAIL is currently set to a value of 1 by default and means debug is turned on. When set to 0, debug is still turned on. The correct behavior is for the default to be set to 0, meaning the debug is turned off.

Grace period defaults if left blank or set to 0

In the Platform Management Console, when the grace period is left blank or is set to 0, the default grace period of 120 seconds is actually used.

Core or thread detection: supported operating systems

Solaris on multicore hardware should be Solaris 10 update 2 or later.

Core or thread detection on Linux/PPC and IRIX/MIPS is not supported.

Registered client name recovery fails—character limitations

Ensure that you do not use the pipe character (“|”) in the client name.

Command does not work as expected—character limitations

Be careful of extra/unwanted spaces used when entering commands. A space is considered an extra character. If you use extra spaces in a command, it will not run.

Allocation not fulfilled although the resource allocation is still satisfied because of a combination of potential borrowed resources

When creating an allocation with slot per host configured to be greater than 1 through either the API (“tile” in vem_allocreq_t structure) or CLI (egosh alloc new -s ... ), and the value is greater than resource distribution policy's planned value, then the allocation may not get the requested slots even if the request could be satisfied with combination of potential borrowed resources.

Further information on setting workload slots can be found in Administering and Using Platform EGO, in the section “Understanding Resource Groups: Notes on Setting Workload Slots”.

Service will not start on consumer after adding a new child consumer

Do not create a new leaf-consumer if the parent consumer already has a service registered to it. Services can only run on leaf-consumers (consumers without any children).

Web service gateway started but client can’t connect to it

On certain Windows platforms, the web service gateway is allowed to start despite the assigned port being in use. In such a case, the web service client will not be able to connect to the web service gateway (wsgserver daemon). To avoid this, ensure that no other services are using the assigned port before starting the web service gateway.

EGO installed but all services fail

Do not install EGO under a directory name that includes non-English characters (for example, a Japanese directory name). Directory names that use non-English characters will cause the services installed under them to fail.

EGO fails to recognize cluster node IP address changes

Due to deep, persistent caching within the lim daemon, EGO does not function correctly in an environment where compute node IP addresses change while the EGO cluster is running.

To ensure proper performance, use statically assigned IP addresses for compute nodes. If a compute node’s IP address must be changed, the best practice is to follow the procedure for removing and re-adding the compute node to the cluster.

Information about removing compute hosts from a cluster can be found in Administering and Using Platform EGO, in the section “Control hosts”. Information on adding hosts to the cluster can be found in both Planning and Installing Your Cluster on Windows and Planning and Installing Your Platform EGO Cluster on Linux.

IPv6 on Windows

There are some bugs in Windows XP for IPv6 that prevent EGO from running properly. Also, IPv6 and IPv4 cannot work concurrently.

To work around this problem, disable IPv6 in ego.conf.