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.

Dynamic Languages (Node.JS, Python, PHP, C/C++, Webserver Agent)

Cannot install nodejs agent because missing package.json file

herman_internet
New Member

Cannot install nodejs agent because missing package.json file

Following instructions from https://docs.appdynamics.com/display/PRO43/Install+the+Node.js+Agent I did npm install appdynamics@4.3.2 (my controller version is 4.3.2.1)

The download looks fine until the following warning or error messages:

 

npm WARN enoent ENOENT: no such file or directory, open '/root/package.json'

npm WARN root No description

npm WARN root No repository field.

npm WARN root No README data

npm WARN root No license field.

 

Then npm start causes the following error message (several times):

 

npm ERR! enoent ENOENT: no such file or directory, open '/root/package.json'

 

By the way, other try I did before gave a different error mesage (perhaps with other appdynamics nodejs agent version):

 

npm ERR! enoent ENOENT: no such file or directory, open '/opt/appdynamics/controller/package.json'

 

My node version is 6.10.3

npm is 3.10.10

 

Any idea?

By replying you agree to the Terms and Conditions of the AppDynamics Community.
Cannot install nodejs agent because missing package.json file
2 REPLIES 2
Kyle.Furlong
AppDynamics Team

Hi Herman,

 

Could you provide your ~/.npmrc file? Could you also try doing npm cache clear and then the install?

 

Regards,

Kyle

Thanks,
Kyle Furlong, Technical Lead (C++ and Dynamic Languages)




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

Taper la comande suivante:

En root

# npm init puis faire entrer à chaque question. Ceci devra corrigé l'erreur. Après tu relance l'installation. Ceci devra corrigé l'erreur.