HP Matrix Operating Environment Software - Manual (Page 66)

Application hangs in fss group
On HP-UX 11i v2 (B.11.23), an application inside an fss group might hang when running in a
single-processor virtual partition, nPartition, or system.
Workaround
Install patch PHKL_33052.
Scripts not placed in correct workloads
With compartments based on psets or fss groups, gWLM allows you to place scripts in the
compartments using application records with alternate names. This works only if the shell or
interpreter being used is listed in the file /etc/shells. Typically, perl is not in this file. So, perl
scripts (and any other scripts based on shells or interpreters not listed in /etc/shells) are not
properly placed.
Executables are not affected by this issue.
Workaround
Add /opt/perl/bin/perl, and any other needed shells or interpreters, to the file /etc/
shells
. Global Workload Manager will recognize the added shells or interpreters within 30
seconds.
NOTE: Because the full pathname is not required for the script, a rogue user could get access to
compartments based on psets or fss groups — that would otherwise not be accessible — by using
the name of the script for new scripts or wrappers.
Processes moved to default pset or default fss group
All process placement with the gwlmplace command on a managed node is lost if:
•
The managed node is rebooted.
•
The local gwlmagent daemon is restarted.
•
You undeploy the current SRD.
In these cases, processes are placed according to any application records or user records that
apply. If no records exist, nonroot processes are placed in the default pset or default fss group;
root processes are left where they are.
Workaround
To maintain the process placements across redeploys, use gWLM's application records or user
records when creating or editing your workload definitions in gWLM.
Sizes/allocations less than policy minimums for Virtual Machines
The sizes or allocations for virtual machines in a deployed SRD can appear to be less than their
policy minimums.
Workaround
Wait a few minutes, since it can take several minutes for gWLM to recognize a virtual machine
transition between the states of off and on.
Changes in sizes in Discovery
When a VSP with vPars is added to an SRD, the total size that is displayed during discovery might
differ from the sum of sizes of the compartments. This is because of the free cores in the guest pool
of the VSP that do not belong to any vPar.
Workaround
Wait for the SRD to be deployed. The sizes will be proper after deployment.
66 Global Workload Manager known issues