cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AppDynamics kubernetes cluster agent instrumentation

Sitikantha.Mishra
New Member

We are using java instrumentation for our applications running on the Kubernetes cluster.

The applications are running with a normal user "appuser" , where appd agent is showing an error.

 

MultiTenantAgent Dynamic Service error - could not open Dynamic Service Log /opt/appdynamics-java/ver22.4.0.33722/logs/fixeddeposit-service-cb865796d-jp29w/argentoDynamicService_05-09-2022-05.10.44.log

     Running as user appuser

     Cannot write to parent folder /opt/appdynamics-java/ver22.4.0.33722/logs/fixeddeposit-service-cb865796d-jp29w

     Could NOT get owner for MultiTenantAgent Dynamic Services Folder

     Likely due to fact that owner (null) is not same user as the runtime user (appuser)

     which means you will need to give group write access using this command:  find external-services/argentoDynamicService  -type d -exec chmod g+w {}

     Possibly due to lack of permissions or file access to folder: Exists: false, CanRead: false, CanWrite: false

     Possibly due to lack of permissions or file access to log: Exists: false, CanRead: false, CanWrite: false

     Possibly due to java.security.Manager set - null

     Possibly due to missed agent-runtime-dir in Controller-XML and will need the property set to correct this...

     Call Stack: java.io.FileNotFoundException: /opt/appdynamics-java/ver22.4.0.33722/logs/fixeddeposit-service-cb865796d-jp29w/argentoDynamicService_05-09-2022-05.10.44.log (No such file or directory)

 

can anyone help me here?

1 REPLY 1

Mario.Morelli
Architect

Hi Sitakantha

 

How have you added the java agent into the pods? Are you using the Cluster Agent Auto Deployment, or are you using a sidecar method or adding the agent in via the Dockerfile etc?

 

From the error it is clear the user that is running the java app process, does not have sufficient permissions to read/write to the Java Agent directory.

 

Please ensure to set the permissions to allow the user that the java app process runs as has the necessary rights to the java agent directories.

 

This should then resolve the problem.

 

Ciao



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

Learn more about me in the Community Member Spotlight Q & A