AppD Archive

Node.js agent installing on Linux - status 403

CommunityUser
Splunk Employee
Splunk Employee

Hello,

On a Linux (ubuntu 15) environment

using npm version 3.6.0

using npm install appdynamics@4.1.7

or

npm install appdynamics@latest

ends up with "fetch failed" status code 403.

How to install the agent? Thanks.

yuri@yuri-Z68AP-D3:~/parrot/cuba/parrot-cuba-stage-api$ npm install appdynamics@4.1.7
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-native.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-protobuf.tgz
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.7.0/appdynamics-zmq.tgz
npm ERR! Linux 4.2.0-25-generic
npm ERR! argv "/home/yuri/.nvm/versions/node/v5.6.0/bin/node" "/home/yuri/.nvm/versions/node/v5.6.0/bin/npm" "install" "appdynamics@4.1.7"
npm ERR! node v5.6.0
npm ERR! npm  v3.6.0

npm ERR! fetch failed with status code 403


yuri@yuri-Z68AP-D3:~/parrot/cuba/parrot-cuba-stage-api$ npm install appdynamics@latest
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-zmq.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-native.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403
npm ERR! fetch failed http://packages.appdynamics.com/npm/4.1.8.0/appdynamics-protobuf.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403




Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I am having same problem, My node install is 4.4.0

-bash-4.1$ npm install appdynamics@4.1.7
npm ERR! Linux 2.6.32-573.3.1.el6.x86_64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "appdynamics@4.1.7"
npm ERR! node v4.4.0
npm ERR! npm v2.14.20
npm ERR! code ENOTSUP

npm ERR! notsup Unsupported
npm ERR! notsup Not compatible with your version of node/npm: appdynamics@4.1.7
npm ERR! notsup Required: {"node":">=0.8.0 <=0.12.7"}
npm ERR! notsup Actual: {"npm":"2.14.20","node":"4.4.0"}

How do I fix this?

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Appdynamics Node agent does not support node version 4.4.0 yet.

Click on the Arrow icon next to 4.2.1 and 4.2.0 to see the list of all supported Node.js versions per major and minor release.

https://docs.appdynamics.com/display/PRO42/Node.js+Supported+Environments

You might want to upgrade your node version to 5.0.0 and then try installing 4.2.1

npm install appdynamics@4.2.1
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Looks like the problem is that it doens't support node 5.x.x

Checked  

npm view appdynamics

Got:

...
 engines: { node: '>=0.8.0 <=0.12.9' },
...

Rolled back on 

node v0.12.7 and npm 2.11.3

installed ok

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Same problem here. Node 5 is out for a long time now...

0 Karma

John_Briere
Explorer
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thank you but this doesn't solve the issue : 

npm install --save appdynamics@next

 

npm WARN engine appdynamics@4.2.0: wanted: {"node":">=0.8.0 <=5.3.0"} (current: {"node":"5.5.0","npm":"3.3.12"})

npm WARN engine appdynamics@4.2.0: wanted: {"node":">=0.8.0 <=5.3.0"} (current: {"node":"5.5.0","npm":"3.3.12"})

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.0.0/appdynamics-protobuf.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.0.0/appdynamics-zmq.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.0.0/appdynamics-native.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.0.0/appdynamics-native.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.0.0/appdynamics-zmq.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

npm ERR! fetch failed http://packages.appdynamics.com/npm/4.2.0.0/appdynamics-protobuf.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 403

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Your CDN response : 

<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>DCD115AA3BD77EE4</RequestId>
<HostId>
RzFET3TJHuzDTd6AqkpCxTVaCLOr62iF+vBk4BF0xsiJ48GoouhPR6g55R9HMY92fDnZNwSaxM8=
</HostId>
</Error>
0 Karma

John_Briere
Explorer

Right now we only support 5.x up to 5.3. Check: 

https://docs.appdynamics.com/display/PRO42/Node.js+Supported+Environments

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...