On AIX servers that are running DUAS v6, uxtrace fails to be launched. The procedure remains stuck while launching the "top -bud3" command. On some systems, this opens a screen that auto-refreshes instead of providing a single snapshot. This causes the uxtrace to get stuck.
In the universe.log, the following error appear: |ERROR|X|IO |pid=66651162.7477| k_trt_req_utils | UTILS [k_utils_trt_req_uxt] error code: [1] error msg: [uxtrace procedure in error [256]] |ERROR|X|IO |pid=66651162.6977| k_trt_req_utils | UTILS subrequest [t] returns error [-1]
Environment
AIX with command top available
Cause
On some AIX systems, the command "top -bud3" opens a screen that auto-refreshes instead of providing a single snapshot, this causes the uxtrace procedure to "hang".
Resolution
Edit the file $UNI_DIR_EXEC/uxtrace/uxtrace from line 1062:
TOP_CMD=`which top 2>&1|cut -d" " -f1` if [ ! -z "${TOP_CMD}" ] && [ -x ${TOP_CMD} ]; then UX_CMD "${TOP_CMD} -bud3" ${UXTRACESYSFOLDER}/top_bud3_${loc_output_number}.txt else UX_CMD "ps aux | sort -rn +4" ${UXTRACESYSFOLDER}/ps_aux_SZ${loc_output_number}.txt UX_CMD "ps aux | sort -rn +2" ${UXTRACESYSFOLDER}/ps_aux_CPU${loc_output_number}.txt fi
Replace by:
#TOP_CMD=`which top 2>&1|cut -d" " -f1` # if [ ! -z "${TOP_CMD}" ] && [ -x ${TOP_CMD} ]; then # UX_CMD "${TOP_CMD} -bud3" ${UXTRACESYSFOLDER}/top_bud3_${loc_output_number}.txt # else UX_CMD "ps aux | sort -rn +4" ${UXTRACESYSFOLDER}/ps_aux_SZ${loc_output_number}.txt UX_CMD "ps aux | sort -rn +2" ${UXTRACESYSFOLDER}/ps_aux_CPU${loc_output_number}.txt # fi
After saving the modifications, relaunch the uxtrace procedure, this time the command "top -bud3" will no longer be launched.