HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

6. Re-apply the configuration
7. Re-start the package
• Another solution is to add a new package with a service name matching that
originally deleted and then halt the service with cmhaltserv. This would allow
the problem to be resolved without halting either the package, node or cluster.
• Alternatively, if the cluster/node were halted and re-started the problem would
go away. This resolution requires cluster/node downtime, however, and that is
not always possible in 24x7 environments.
JAGaf79389(SR8606419559): Package not started on adoptive node after cmhaltnode
-f
What was the problem? A package was not started on an adoptive node after cmhaltnode
-f.
This happens when a node is shut down and a halt script for a package with
node_fail_fast_enabled set to yes exceeds its halt_script_timeout. Serviceguard kills the
halt script’s process, and the node performs a system reset. The package is not restarted
on an adoptive node.
What is the workaround? There is no workaround.
JAGag31490 (SR8606477006): Modular package fails with the error: ‘Unable to
retrieve package attribute’.
What is the problem? In clusters with over 100 packages configured, when the cluster
and packages start simultaneously, some packages may fail to start. Errors may appear
in the log files of modular package log files, saying Unable to retrieve package
attributes, and that the package failed to start.Messages such as the following
appear in the package log file:
Feb 7 09:00:50 [e-mail]
master_control_script.sh
[11121]: ERROR: Unable to retrieve package attributes.
Feb 7 09:00:50 [e-mail]
master_control_script.sh
[11121]: ERROR: Function sg_source_pkg_env
The messages indicate that the cmgetpkgenv command had difficulty obtaining
information about the package that is required for the package scripts to run. This does
not mean that the package cannot be started after the other packages are stable.
What is the workaround? If you see this problem, you can issue a cmrunpkg on the
packages that have not started.
JAGag32406 (SR8606478077): 11.18 cmclconfd is using a deprecated SCSI ioctl
What is the problem? When a lock LUN is used on SLES 10 systems the following message
will be displayed in the syslog file:
Known Problems and Workarounds 83