Cloud proxy not creating PID files when starting service.
search cancel

Cloud proxy not creating PID files when starting service.

book

Article ID: 397882

calendar_today

Updated On:

Products

DX Operational Observability CA Application Performance Management (APM / Wily / Introscope) CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management SaaS

Issue/Introduction

When starting the cloud proxy service on a few servers, the PID files are not being created. Receiving the following error on the non-working ones:

 

[<UNIX PROMPT>]$ ./apmservices.cloudproxy.sh start
apmservices.cloudproxy waiting to be up: PID <Pid_Number>
./apmservices.cloudproxy.sh: line 134: /<directory_path>: No such file or directory
apmservices.cloudproxy start failed. Please check the logs.

The service starts and the agent comes up but no PID file is created. Checked both the working and non-working servers for the "jcmd" file and it's not present on either server. But on some servers it works.

Resolution

Change this line in apmservices.cloudproxy.sh.

 

< PID_PATH=".apmservices.cloudproxy.pid"

TO

> PID_PATH="${BASE_PATH}/apmservices.cloudproxy.pid"

 

Additional Information

Impact was unable to stop the service or see its status. This is NOT being added to the product at this time