HP Matrix Operating Environment Software - Manual (Page 61)

Workaround
Undeploy the SRD using the --force option with the gwlm undeploy command, and restart
gwlmagent
on the managed node.
SRD deployment times out and displays a blank screen
If you attempt to deploy an SRD, but:
•
gWLM times out and displays a blank screen
•
There are events from each managed node similar to the following event:
gWLM Agent MySystem.MyDomain.com
Information Unable to manage the following hosts:
Associated Exception Unable to manage the following hosts: MySystem.MyDomain.com: The gWLM agent
process on the host is not running -- start the agent and retry.
You need to configure gWLM to work with hosts on multiple LANs.
Workaround
See
Using gWLM with Hosts on Multiple LANs for information on configuring gWLM to work with
hosts on multiple LANs.
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.
Documentation or minor issues 61