We're facing challenges monitoring cloudproxy where we are not getting status of Cloudproxy with below command
[,account>@<host>]$ ./apmservices.cloudproxy.sh status
apmservices.cloudproxy not running
[,account>@<host>y]$
But when we do ps -ef then cloudproxy is running
The code depends on finding a hidden pid file . (See additional information.)
The file disappears if you have an unsupported setup of TWO cloud proxies on the same server
Solution:
Change this line in apmservices.cloudproxy.sh.
FROM
< PID_PATH=".apmservices.cloudproxy.pid"
TO
> PID_PATH="${BASE_PATH}/apmservices.cloudproxy.pid"
This is not supported and will not be added to product.
Debugging steps:
Cloud proxy version 25.1.1.25
The status section of the apmservices.cloudproxy.sh looks the same as the 25.2.1.25:
status() {
if [ -f ${PID_PATH} ];then
PID=`cat ${PID_PATH}`;
echo "apmservices.cloudproxy running: PID ${PID}";
return 0
else
echo "apmservices.cloudproxy not running";
return 0
fi
}
Added set -x to the status function and it produces the following output:
./apmservices.cloudproxy.sh status
+ '[' -f .apmservices.cloudproxy.pid ']'
+ echo 'apmservices.cloudproxy not running'
apmservices.cloudproxy not running
+ return 0
+ exit 0