To upgrade a server that is running the dcm-agent you must have root level shell access to the VM (this is typically achieved with ssh). Once you are logged into the server as root perform the following steps:
-
Preserve configuration and customized files. Copy the current configuration to a temporary location:
cp /dcm/etc/agent.conf /tmp/agent.conf
If you have made customizations to any of the files in
/dcm/bin
or to/dcm/etc/logging.yaml
please back these up. Note this is not typical, most customers will not need to do this. -
Stop the DCM agent if it is running:
/etc/init.d/dcm-agent stop
-
Fetch the DCM installer:
wget http://es-pyagent.s3.amazonaws.com/installer.sh
-
If on an rpm based machine (RHEL or CentOS) remove the existing package:
rpm -e dcm-agent
-
Run the installer:
If your DCM server has a trusted cert (one signed by a well known CA like VeriSign) then run:
bash ./installer.sh -r /tmp/agent.conf
If you are using a self signed cert or otherwise unknown cert run:
bash ./installer.sh -r /tmp/agent.conf -Z
-
Verify that the correct agent was installed:
/opt/dcm-agent/agentve/bin/dcm-agent --version Version 0.11.2-c9177e8824261d9f0837d09be74f822130c446f6
The output should be
Version 0.11.2-c9177e8824261d9f0837d09be74f822130c446f6
as shown above. -
Merge in customizations. In the rare case where in step 1 files from
/dcm/bin
or/dcm/etc/logging.yaml
were preserved you will have to manually merge in whatever changes or customizations were made. -
Set secure ownership and restart the agent
chown dcm:dcm /dcm/secure/* /etc/init.d/dcm-agent start