New Relic for Node.js was unable to start due to an error: Error: EISDIR, illegal operation on a directory

[maumercado]

Hello, Im having the following error initializing new relics config and monitoring
--> /home_dir/.npm/package.json

New Relic for Node.js was unable to start due to an error:
Error: EISDIR, illegal operation on a directory
at Object.fs.readSync (fs.js:476:19)
at Object.fs.readFileSync (fs.js:310:28)
at /home_dir/node_modules/newrelic/lib/environment.js:86:37
at Array.map (native)
at listPackages (/home_dir/node_modules/newrelic/lib/environment.js:83:8)
at getPackages (/home_dir/node_modules/newrelic/lib/environment.js:160:16)
at /home_dir/node_modules/newrelic/lib/environment.js:273:21
at Array.forEach (native)
at findPackages (/home_dir/node_modules/newrelic/lib/environment.js:271:11)
at Object. (/home_dir/node_modules/newrelic/lib/environment.js:350:1)

[groundwater]

Hey @maumercado, sorry to see you had trouble deploying the agent.

Do you mind if I ask what version of the agent you're using? We had a bug in an older version which choked in a very similar fashion to what you're seeing now. If you've got an older version, can you try upgrading to the latest and see if that fixes the problem?

If you already have the latest, I may ask for some additional details about your deployment. In the mean time, I'll double-check that section of the code, just in case.

Thanks for the stack trace! I hope can fix your issue soon.

[maumercado]

Hey @groundwater Im using the latest new relic 1.3.2

[groundwater]

Is there a chance that /opt/selfietest/.npm/package.json is a directory, or a symlink pointing to a directory?

It seems to be throwing here which would definitely throw if it cannot read package.json.

At the very least, this should not crash your app. I think in this case it should not impair the agent from starting either.

[maumercado]

yes its a directory!

[groundwater]

So the short term fix is to either delete that, or change it to a file. This is definitely a bug however, so I'll get a fix into the next release.

Thanks for the excellent sleuthing!

I'm going to leave this issue open until the fix is out.

[maumercado]

Awesome @groundwater thanks for your help!

[groundwater]

@maumercado not a problem, thanks for using the node agent!

[groundwater]

This should be fixed in v1.5.2