ra/SAPHana HANA_CALL - inner timeout prevents proper logging in hdbnsutil trace file

[PeterPitterling]

ra/SAPHanaTopology is properly traced

CommandUtil.cpp(00065) : command: hdbnsutil -sr_stateConfiguration --sapcontrol=1
CommandUtil.cpp(00098) : called by user 'tqladm' with UID: 1001 (parent process command line '-sh -c (: [8792]; hdbnsutil -sr_stateConfiguration --sapcontrol=1 > /run/SAPHanaSR_tql/HANA_CALL_CMD_TOP_OUT_1710875260638426633_tqladm) >& /run/SAPHanaSR_tql/HANA_CALL_CMD_TOP_1710875260638426633_tqladm ' with PID: 8882) (parent process executable /bin/bash')

while ra/SAPHana not; hdbnsutil is containing the full cmdline from the parent process, which is "timeout" in this case

CommandUtil.cpp(00065) : command: hdbnsutil -sr_stateConfiguration --sapcontrol=1
CommandUtil.cpp(00098) : called by user 'tqladm' with UID: 1001 (parent process command line 'timeout -s 9 60 hdbnsutil -sr_stateConfiguration --sapcontrol=1 ' with PID: 8108) (parent process executable /usr/bin/timeout')

all important information like PID and filenames are missing.

The inner timeout has anyway no meaning as it has the same timeout value as the outer timeout, which will be trigger earlier

[PeterPitterling]

this problem is now affecting ANGI as well. Cause ANGI is using the "old" ra/SAPHana HANA_CALL implementation with the inner timeout .. no PID nor filenames are logged in the nameserver.00000.trc file !