After installing an EndPoint Operations agent on Linux OS using RPM, there are two commands that can be used to start the agent. Choose once of the below options to start the agent:
The first time the agent is started it creates new files and folders in various locations. The owner of the new files and folders depends on the method used (i.e. #1 or #2).
As a result the service or shell script will only work using the method that was chosen in the initial phase.
For example, if the agent was started using the ep-agent.sh script, the user would not be able to control the agent using service commands.
To resolve the issue, stop the epops-agent and then perform one of these alternatives:
Note: EPOPS_AGENT_HOME is the full path to the EndPoint Operations agent installation directory.
This example script can be used to perform the fix if the EndPoint Operations agent has been started using the ep-agent.sh and you want to switch to service mode:
Sample script#!/bin/sh
# The full path to the EP Ops agent installation directory
EPOPS_AGENT_HOME=
/opt/vmware/epops-agent/
RUN_AS_USER=epops
RUN_AS_USER_GROUP=epops
chown
-R $RUN_AS_USER:$RUN_AS_USER_GROUP $EPOPS_AGENT_HOME
chown
-R $RUN_AS_USER:$RUN_AS_USER_GROUP
/etc/default/epops-agent
chown
-R $RUN_AS_USER:$RUN_AS_USER_GROUP
/etc/epops/
echo
"Done"