On Solars, stopping UNIX OS Agent might return "failed to stop" error message.

When the "itmcmd agent stop ux" command is issued, the following messages are displayed:

Processing. Please wait...
Stopping Watchdog process...
CandleAgent failure: Watchdog for OS Agent failed to stop, review logs for more info.

In this example, the file /usr/xpg4/bin/awk, which should normally exist on a Solaris system, is missing on the system. The file is included in the POSIX standard utilities packages (SUNWxcu4 on Solaris10, system/xopen/xcu4 on Solaris11).

Starting in 623 FP1, the scripts to start and stop Watchdog (which is part of the OS agent), were enhanced to address some specific issues on Solaris. The enhancements included more robust use of the "awk" command, so it uses the awk in the /usr/xpg4/bin directory.

As documented by Sun (http://docs.oracle.com/cd/E26502_01/html/E29030/awk-1.html#scrolltoc), the awk under /usr/bin is not following standards: it provides less functionality then the /usr/bin/awk of other platforms. They also stated that /usr/xpg4/bin/awk is committed for "Interface stability", meaning that they guarantee it, also for future releases.

Solaris

In the <hostname>_ux_<nnnnnnnnnn>.log file the following message can be seen:
/opt/IBM/ITM/sol296/ux/bin/statusWatchdog.sh[34]: /usr/xpg4/bin/awk: not found

In the kcawd_disarmWatchdog.log file, the folllowing messages will be seen:
getFullCommandPid: No process found with executable name: kuxagent and CANDLEHOME: <value
for CANDLEHOME>
OSAGT_PID got from cinfo =<9999>
getCommandPath: getProcessList returned: 127. Returning path: for process with pid: <9999>

Ensure the /usr/xpg4/bin/awk is installed on the system, or copy one from another system at the same version.