Serviceguard Manager Version A.05.00 Release Notes, October 2005

Serviceguard Manager Version A.05.00 Release Notes
Patches and Fixes in this Version
Chapter 1 53
JAGaf13947 NPE while trying to save after gui was up for 24
hours (java problem)
• What is the problem? After Serviceguard Manager had been running
for 24 hours, Java gave a Null Pointer Exception when user tried to
Save.
• What is the workaround? There is no workaround. Restart
Serviceguard Manager
JAGaf12970 Service commands that contain quotes are not
passed to control script.
• What is the problem? This happens when you are using Guided Mode
and letting Serviceguard Manager create your control script
automatically. If you enter a service command with quotes in it, such
as /usr/bin/X11/xclock -title "My Xclock", your quotes will be
ignored when they are transferred.
After the script is Applied, the target control script in
/etc/cmcluster/<pkgName>/<pkgName>.sdf.sh contains
something like this: SERVICE_CMD[0]="/usr/bin/X11/xclock
-title My Xclock"
• What is the workaround? Do not use quotes in service commands if
you are creating the control script through Guided Mode.
JAGaf11256 Serviceguard Manager won't discover nodes if
another cluster has the same name.
• What is the problem? Once Serviceguard Manager discovers a
cluster, it will ignore any others that have the same name. For
example, imagine that one subnet has a cluster clus1, whose
members are node1 and node2. Now imagine that another subnet
has a cluster named clus1, whose members are nodeX and nodeY.
The situation is not common because Serviceguard insists that the
cluster name must be unique in its environment. Because the
Session Server may have different subnet access than either cluster
does, it may be able to see clusters that cannot see each other. If it
does, it will display the first clus1 that it encounters during
discovery, and ignore the other.
• What is the workaround? There is no workaround.