HP-UX Workload Manager A.03.02.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

HP-UX Workload Manager Release Notes

Known problems and workarounds

wlmcomd -k failed: Resource temporarily unavailable

These messages are misleading in that they imply that the shutdown

request had failed when it might not have. These messages have been

replaced by the more accurate messages reported above.

Workaround If a shutdown request has been delayed for 30 seconds, WLM issues the

“Waiting for shutdown confirmation” message. WLM is likely delaying

the shutdown request while waiting for partition modifications to complete.

If after a total of 120 seconds the shutdown has still not completed, WLM

issues the “Shutdown initiated” message. This most likely means that the

partition modifications have not yet completed. They can take longer than

120 seconds. When the modifications have been made, WLM will honor the

shutdown request. You can verify the shutdown has succeeded by using the

ps command (if necessary, issue your shutdown command again). In

addition, check the messages in /var/opt/wlm/msglog.

Unable to get CPU allocation due to number of processes

Issue WLM provides a workload group its allocation on a system by granting the

group its allocation on each core. If the group does not have at least one

process for each core, WLM increases the allocations for the processes to

compensate. For example, for a workload group with a single-threaded

process, 10% of four cores is allocated as 40% of one core.

Assume this same group were allocated 50% of the four cores. WLM would

allocate 100% of two cores to the workload group. However, because the

group has only the one thread, it can use only one core, resulting in an

allocation of 25%.

Workaround There is no workaround. However, be aware of how your applications run so

that you do not give them resource allocations they cannot use.

Collectors abort when updated while running

Issue If you update (overwrite) a data collector executable (be it a binary or a

script) while it is providing data to WLM, the collector may abort.

Workaround There are two workarounds to this issue:

• Update the data collector in place

1. Stop WLM (wlmd -k)

2. Update the data collector