cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Java (Java Agent, Installation, JVM, and Controller Installation)

Machine Agent Can't start "Invalid argument"

SOLVED
Junaid.Wahab
Builder

Machine Agent Can't start "Invalid argument"

I am trying to enable machine agent in Solaris server. JAVA verison 11.0. Machine Agent version 20.9. 

I am getting following error. I checked JAVA path is correct. everything is according to the doc. But not able to start agent. any thoughts  

 
./machine-agent -d -p /opt/appdynamics/machineagent/pidfile
Using java executable at /opt/appdynamics/machineagent/jre/bin/java
#nohup: /opt/appdynamics/machineagent/jre/bin/java: Invalid argument
 

 

Tags (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
Machine Agent Can't start "Invalid argument"
3 REPLIES 3
Mario.Morelli
Architect

Hi there

 

Firstly did you use the correct Solaris machine Agent, X86 or SPARC?

 

Can you do the following

Run the following command and provide the output

 

java -version

 

Also try and start it manually the following way

 

navigate to the root <agent installation directory>

and run the following command

nohup java -jar ./machineagent.jar &

 

Check if the agent starts

 

 



Learn more about me in the Community Member Spotlight Q & A
Okik.Setianto
Producer

Hi Bro,

 

Have you defined the account-name, access-key, application-name, tier-name, and node-name in the controller_info.xml? If yes, can you attach the machine-agent.log?

 

 

Junaid.Wahab
Builder

Thanks for your help. Problem has been solved. The problem with some AppDynamics agent folder permission issues that's why not all the files were loaded. Now I have another problem with App Agent. creating new discussion. Thanks