Admin: Created page with "Killing Processes on ZEB & PCR servers --------------------------------------- Login to server Check for service called magento with below command • ps –aux | grep m..."

2021-06-30T11:46:53Z

Created page with "Killing Processes on ZEB & PCR servers --------------------------------------- Login to server Check for service called magento with below command • ps –aux | grep m..."

New page

Killing Processes on ZEB & PCR servers
---------------------------------------

Login to server

Check for service called magento with below command

• ps –aux | grep magento

Check for any java services with below command

• ps –aux | grep java

Once we run above commands, will get running services with Some ID’s

So, using that ID’s we can kill that processes, as below

• Kill ID e.g. kill 9423

After confirming that all db agent and machine agent are stopped, we need to manually start them, for that run below commands

PCR:

• cd /opt/appdynamics/db-agent/
nohup java -Ddbagent.name=live-pcr -jar db-agent.jar &

• cd /opt/appdynamics/machine_agent
nohup java -Dappdynamics.agent.maxMetrics=5000 -jar machineagent.jar &

Zeb:

• cd /opt/appdynamics/db-agent/
nohup java -jar db-agent.jar &

• cd /opt/appdynamics/machine_agent
nohup java -Dappdynamics.agent.maxMetrics=5000 -jar machineagent.jar &

• cd /usr/local/bin/
nohup webm_encode.sh "/var/www/html/migration/pub/media/product_videos/live" &
...

additional instances to be started if other paths need to be watched.

Killing CPU 'hungry' processes on Zeb/PCR servers - Revision history

Admin: Created page with "Killing Processes on ZEB & PCR servers --------------------------------------- Login to server Check for service called magento with below command • ps –aux | grep m..."