Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js version v6.10.3 is not supported. Agent disabled #64

Closed
plentz opened this issue Jul 27, 2017 · 4 comments
Closed

Node.js version v6.10.3 is not supported. Agent disabled #64

plentz opened this issue Jul 27, 2017 · 4 comments

Comments

@plentz
Copy link

plentz commented Jul 27, 2017

JSON::ParserError: 743: unexpected token at 'Node.js version v6.10.3 is not supported. Agent disabled.
["ok"]'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/external_runtime.rb:68:in `extract_result'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/external_runtime.rb:39:in `exec'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/external_runtime.rb:14:in `initialize'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/runtime.rb:57:in `new'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/runtime.rb:57:in `compile'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/runtime.rb:44:in `eval'
/var/www/app/shared/bundle/ruby/2.4.0/gems/execjs-2.7.0/lib/execjs/module.rb:23:in `eval'

related: npm/npm#17953

@plentz
Copy link
Author

plentz commented Jul 27, 2017

The cause of this problem is:

[root@ip-172-31-33-207 centos]# node -v
v6.10.3
[root@ip-172-31-33-207 centos]# npm -v
Node.js version v6.10.3 is not supported. Agent disabled.
3.10.10

@MichaelSp
Copy link

MichaelSp commented Feb 21, 2019

still an issue here... is there any workaround?

JSON::ParserError: 767: unexpected token at 'Node.js version v10.15.1 is not supported. Agent disabled.["ok"]'

@thomas-profitt
Copy link

This error message isn't printed by execjs, or even node.
It's printed by the agent daemon for a service called DynaTrace, which hooks into node's execution, and misbehaves by printing warnings, breaking things like parsing JSON output from tools written in node.

We could've been spared the confusion of debugging this, had DynaTrace wrote a warning message that made it clear it was coming from the agent daemon, not from the software you thought you were running.

Update the DynaTrace agent, or remove it.

@byroot
Copy link
Member

byroot commented May 7, 2021

Third party issue. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants