APM connection is getting killed in nodejs


(Ronak Patel) #1

Kibana version: 6.6.0

Elasticsearch version: 6.6.0

APM Server version: 6.6.1

APM Agent language and version: nodejs

Original install method (e.g. download page, yum, deb, from source, etc.) and version: Client and server both running in kubernetes cluster

Fresh install or upgraded from other version? Fresh. Using Azure template for ELK stake.

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

Steps to reproduce:

  1. Get ELK stack on Azure by official template.
  2. Run APM server in kubernetes cluster.
  3. Run nodejs application with APM client within the same kubernetes cluster.
  4. Try to connect it using kubernetes internal DNS (apm-server.default.svc.cluster.local:8200)

Provide logs and/or server output (if relevant):
adding hook to Node.js module loader
shimming finalhandler@1.1.1 module
shimming http@10.0.0 module
shimming http.Server.prototype.emit function
shimming http.request function
shimming http.ServerResponse.prototype.writeHead function
shimming express@4.16.4 module
shimming express.Router.process_params function
shimming express.Router.use function
shimming express.static function
copying property mime from express.static
shimming bluebird@3.5.3 module
shimming bluebird.prototype functions: [ '_then', '_addCallbacks' ]
shimming bluebird.config
shimming generic-pool@3.6.1 module
shimming generic-pool.PriorityQueue.prototype.enqueue
shimming mysql2@1.6.5 module
shimming https@10.0.0 module
shimming https.Server.prototype.emit function
shimming https.request function
shimming graphql@14.1.1 module
shimming express-graphql@0.6.12 module
shimming layer.handle_request function (layer: )
shimming layer.handle_request function (layer: )
skip shimming layer.handle_request (layer: urlencodedParser, path: /)
skip shimming layer.handle_request (layer: jsonParser, path: /)
skip shimming layer.handle_request (layer: helmet, path: /)
skip shimming layer.handle_request (layer: cookieParser, path: /)
skip shimming layer.handle_request (layer: corsMiddleware, path: /)
skip shimming layer.handle_request (layer: serveStatic, path: /)
shimming layer.handle_request function (layer: csrf)
shimming layer.handle_request function (layer: router)
shimming layer.handle_request function (layer: router)
shimming layer.handle_request function (layer: auth)
shimming layer.handle_request function (layer: router)
shimming layer.handle_request function (layer: )
shimming layer.handle_request function (layer: router)
shimming layer.handle_request function (layer: router)
skip shimming layer.handle_request (layer: , path: /)
no active transaction found - cannot build new span
intercepted call to http.request { id: null }
no active transaction found - cannot build new span
no active transaction found - cannot build new span
intercepted call to generic-pool.PriorityQueue.prototype.enqueue { id: null }
no active transaction found - cannot build new span
no active transaction found - cannot build new span
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! my-api@0.0.0 staging: NODE_ENV=staging node src/loader.js
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the my-api@0.0.0 staging script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/node/.npm/_logs/2019-02-21T20_20_57_725Z-debug.log


(Stephen Belanger) #2

I don't see anything in that log indicating that this is caused by the Node.js APM agent. Do you have more context you could provide? Do you know what exactly the code is doing when it stops?


(system) closed #3

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.