Agent failed to start. From the error code it looks like due to missing callback

[Blazar]

Here's the error message. I just cloned Node from githut, made and installed yesterday.

The New Relic Node.js agent was unable to start due to an error:
TypeError: callbacks argument must be an object
    at createAsyncListener (node.js:536:15)
    at process.addAsyncListener (node.js:548:21)
    at Object.create [as createNamespace] (/home/****/node_modules/newrelic/node_modules/continuation-local-storage/context.js:151:26)
    at Object.<anonymous> (/home/****/node_modules/newrelic/lib/transaction/tracer.js:22:33)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:349:32)
    at Function.Module._load (module.js:305:12)
    at Module.require (module.js:357:17)
    at require (module.js:373:17)

[othiym23]

You wouldn't happen to be running node master or 0.11.11, would you? There's some work to be done on node-continuation-local-storage to sync it up with @trevnorris's changes to the asyncListener interface. It's probably always safe to assume that things may be iffy on unstable versions of Node, though we do try to keep up to date.

[Blazar]

I'm likely are. How do i check?
On Jan 31, 2014 5:53 PM, "Forrest L Norvell" [email protected]
wrote:

You wouldn't happen to be running node master or 0.11.11, would you?
There's some work to be done on node-continuation-local-storage to sync
it up with @trevnorris https://github.com/trevnorris's changes to the
asyncListener interface. It's probably always safe to assume that things
may be iffy on unstable versions of Node, though we do try to keep up to
date.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/112#issuecomment-33859974
.

[othiym23]

node --version will say something like v0.11.11 or v0.11.12-pre if you're running on master. Going back to v0.11.10 or v0.10.25 will likely work better for you, especially if you're going to be deploying to production.

[muniraj65]

how to remove node and it is package completly from ubuntu 13.10 - thanks

[Blazar]

sudo make uninstall
On Feb 11, 2014 9:19 PM, "Muniraj Selvam" [email protected] wrote:

how to remove node and it is package completly from ubuntu 13.10 - thanks

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/112#issuecomment-34839882
.

[txase]

Hi @Blazar,

We believe your issue may have been resolved in updates to the Node.js agent. Please update to the latest agent to confirm.

I'm going to close this issue, but if you continue to see issues, please feel free to reopen.

Thanks!

[fastfrwrd]

I was having this issue when attempting to use the winston-newrelic project. It seems to likely be related to using two different newrelic scopes of some kind. When I pass in newrelic as required by my application as an option here, it works great. But, if I let it default to just requiring newrelic itself, then that error pops up.