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

Error: spawn java ENOENT thrown #32

Open
doug-wade opened this issue Oct 4, 2015 · 1 comment
Open

Error: spawn java ENOENT thrown #32

doug-wade opened this issue Oct 4, 2015 · 1 comment

Comments

@doug-wade
Copy link

I'm trying to start local-dynamo in a gulp task, and I'm getting this error:

Error: spawn java ENOENT
  at exports._errnoException (util.js:837:11)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
  at onErrorNT (internal/child_process.js:344:16)
  at doNTCallback2 (node.js:429:9)
  at process._tickCallback (node.js:343:17)
  at Function.Module.runMain (module.js:477:11)
  at startup (node.js:117:18)
  at node.js:951:3

The gulp task looks like:

gulp.task('launch-dev-db', function() {
  var localDynamo = require('local-dynamo');
  localDynamo.launch(paths.db, 3456);
});

I logged out the PATH that was being supplied to child_process.spawn, and it has /usr/bin/ included, which is where java is:

» file $(which java)
/usr/bin/java: symbolic link to `/etc/alternatives/java'

I'm on node 4.0.0 and Ubuntu 14.04.

@gswalden
Copy link

This happened to me, but once I created the data directory (/database/dir in the docs) the error went away.

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

2 participants