Hi,
Am trying to get my trial of appdynamics going and have encountered some problems.
1. When running npm install appdynamics@4.1.7
npm install appdynamics@4.1.7
npm ERR! Linux 2.6.32-573.3.1.el6.x86_64
npm ERR! argv "/export/home/hms/.nvm/versions/node/v4.3.2/bin/node" "/export/home/hms/.nvm/versions/node/v4.3.2/bin/npm" "install" "appdynamics@4.1.7"
npm ERR! node v4.3.2
npm ERR! npm v2.14.12
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.12","node":"4.3.2"}However, running npm install appdynamics@next works. However, when running the app with the require config, I get
appdynamics v4.2.1.0 (12-03-2016 17:40:44.272): agent.tmpDir = "/tmp/appd/e6f6445998aaf02e82aafdbee8ecfb53" appdynamics v4.2.1.0 (12-03-2016 17:40:44.277): agent.proxyCtrlDir = "/tmp/appd/e6f6445998aaf02e82aafdbee8ecfb53/proxy/c" appdynamics v4.2.1.0 (12-03-2016 17:40:44.279): Loaded native extention. appdynamics v4.2.1.0 (12-03-2016 17:40:44.282): launching proxy from master node 0 appdynamics v4.2.1.0 (12-03-2016 17:40:44.303): ProcessScanner - maxSnapshotsPerPeriod: 2 appdynamics v4.2.1.0 (12-03-2016 17:40:44.303): ProcessScanner - snapshotCountResetPeriodMS: 60000 appdynamics v4.2.1.0 (12-03-2016 17:40:44.303): ProcessScanner - autoSnapshotDurationSeconds: 10 appdynamics v4.2.1.0 (12-03-2016 17:40:44.322): found cluster module appdynamics v4.2.1.0 (12-03-2016 17:40:44.323): found fs module appdynamics v4.2.1.0 (12-03-2016 17:40:44.324): found http module appdynamics v4.2.1.0 (12-03-2016 17:40:44.333): found https module appdynamics v4.2.1.0 (12-03-2016 17:40:44.335): found net module appdynamics v4.2.1.0 (12-03-2016 17:40:44.362): found pg module appdynamics v4.2.1.0 (12-03-2016 17:40:44.399): found redis module appdynamics appdynamics v4.2.1.0 (12-03-2016 17:40:44.428): proxyArgs = [ "-d", "/opt/cqm_onramp/server/node_modules/appdynamics/node_modules/appdynamics-proxy/proxy", "-r", "/tmp/appd/e6f6445998aaf02e82aafdbee8ecfb53/proxy/r", "-j", "/opt/cqm_onramp/server/node_modules/appdynamics/node_modules/appdynamics-jre/jre", "--", "/tmp/appd/e6f6445998aaf02e82aafdbee8ecfb53/proxy/c", "/tmp/appd/e6f6445998aaf02e82aafdbee8ecfb53/proxy/l", "-Dregister=false" ]
However, further down in the logs I get:
[Tue Apr 12 2016 17:41:23] [LOG] appdynamics v4.2.1.0 (12-03-2016 17:41:23.957): { currentVersion: '1460454066535',
agentState: 'UNREGISTERED',
timestampSkew: '0' }
The agent is never registered.
Looking at the proxy logs, I see this message:
[AD Thread Pool-Global1] 12 Apr 2016 17:44:13,383 INFO com.singularity.CONFIG.ConfigurationChannel - Sending Registration request with: Application Name [xxxxxx], Tier Name [Tier1], Node Name [process-1], Host Name [172.17.103.75] Node Unique Local ID [process-1], Version [Proxy v4.2.1.0 GA SHA-1:.9cd8a13bed4e08c4b99513222de4506d6e00bd4d #8496 55-4.2.1.next-build] [AD Thread Pool-Global1] 12 Apr 2016 17:44:13,638 WARN com.singularity.CONFIG.ConfigurationChannel - ResponseReadException creating Response Wrapper [qb], : com.singularity.ee.rest.b: Error in controller in processing binary request AppAgent Config Data - Failed to register as agent version 4.2.1.0 on node process-1 is incompatible with controller version 4.1.7 [AD Thread Pool-Global1] 12 Apr 2016 17:44:13,639 WARN com.singularity.CONFIG.ConfigurationChannel - Unable to get AppAgentConfigurationResponse from controller
How can I get my trial working?