Running a totally fresh instance of Ubuntu 13.10 x64 on DigitalOcean. Every time I try and build Knockout.js using npm/grunt I get the following error:
Running "clean" task
Running "checktrailingspaces:main" (checktrailingspaces) task
Running "build:debug" (build) task
Running "build:min" (build) task
Compiling...Fatal error: spawn ENOENT
The strange part is, the Fatal error is seemingly random. It is always one of these three:
Fatal error: spawn ENOENT
Fatal error: spawn EPIPE
Fatal error: spawn ECONNRESET
I can build everything successfully on Mac OS X as well as an instance of Ubuntu 13.10 x64 at Linode, as well as Ubuntu 13.10 x64 on my home machine. I spun up several instances of Ubuntu 13.10 on different hosts and could only reproduce it on DigitalOcean.
I'm thinking something is funky with DigitalOcean's Ubuntu images, but do not know enough to say for sure. I could be missing some prerequisite packages, but I read all the docs and made sure I met all the requirements for Node/npm/grunt.
I have contacted DigitalOcean and got some great support. An employee managed to reproduce my errors but did not find a solution.
Any help is appreciated greatly.
Edit: My issue was solved below, and had absolutely nothing to do with DigitalOcean's images.
Fatal error: spawn ENOENT means child_process.spawn in node.js cannot find the binary you're attempting to spawn.
So likely you have some dependency the library requires installed on your OSX machine but not on the Ubuntu machine.
Look into your build task to see where and what it is trying to spawn. Running grunt with grunt --stack should help.
Related
steps
I followed the started instruction ,but the errors were threw after I run the kourou commonad app:scaffold playground
Error
with Creating network "playground_default" with the default driver
(sorry for this short message,my host cannot log in.I will complete error message later)
I'm not sure it is related with that I install the kourou before docker-compose. (any permission problem had been solved)
enviroment
Ubuntu Server 20.04 LTS 64bit
Nodejs 14.17.1
Oops, I solved this problem just recently.
I ran the command in the REMOTE SSH of VSCODE before, and then an error occurred. But I just ran it again in ELECTERM(a cross-platform remote ssh terminal) and found that this time it passed when installing dependencies
I still wonder what happened, plz tell me what might be causing the error
so I have deployed my node.js application on heroku but my application uses the help of .exe files to run which were generated on windows. Since heroku runs on a Linux server I am unable to run my executables on the deployed application, but it does run locally. I tried to use wine to run the executables, using the wine build pack but it didn't help as it returned an enoent error.
It would return with an error message of spawn sync path/to/executable ENOENT
I also tried deploying using a docker file but the wine docker file doesn't seem to generate https://hub.docker.com/r/suchja/wine
Is there any workaround for this problem? Any help would be appreciated
Everything happens with Meteor 1.1.0.2
I've been developing a meteor app for quite some time now and with the 1.1 release of meteor I switched my dev environment from linux VM to Windows 8.1 (my everyday working machine). Everything has been working great so far, no issues being present at all, until today.
After deploying my app today, everything seems to work fine for 10-15 seconds and then the app crashes and console starts to throw the following error, which is thrown continuously, every second:
W20150504-14:21:21.355(2)? (STDERR) wmic spawn error: Error: spawn ENOENT
What's important to note is that I did not touch any core files prior to this thing happening and that the problem occurs only on my machine (my co-worker uses Windows 7 and everything works fine) and it is bound only to this particular project.
Here is a list of packages I use, maybe it will give you a hint as to what it might be:
meteor-platform
iron:router
ddp
accounts-password
jquery
meteorhacks:fast-render
meteorhacks:subs-manager
meteorhacks:npm
accounts-ui-bootstrap-3
twbs:bootstrap
upload-jquery
reactive-var
fortawesome:fontawesome
mizzao:jquery-ui
edgee:slingshot
check
tracker
fourseven:scss
npm-container
sacha:spin
meteorhacks:cluster
aldeed:autoform
ovcharik:alertify
mjn:famous
gadicohen:famous-views
meteorhacks:kadira
I've managed to resolve this issue by removing Kadira from my project. I still have no idea why did it make my Windows 8.1 throw ENOENTs so if anyone knows, I would really appreciate your input.
Hi for responsive images i downloaded project from
https://github.com/andismith/grunt-responsive-images
i installed all those things what they have mentioned...
whenever i say grunt it saying fallowing error:
Running "jshint:all" (jshint) task
>> 3 files lint free.
Running "clean:tests" (clean) task
Cleaning "tmp"...OK
Running "responsive_images:default_options" (responsive_images) task
Fatal error: spawn ENOENT
why i am getting this error pla tellme...
Thnk you.
It is likely because you don't have imagemagick installed: http://www.imagemagick.org/script/index.php
See the FAQ on that plugin: https://github.com/andismith/grunt-responsive-images#faq
I experienced exactly the same error as you yesterday, and I found that I had installed wrong version of node.js eventually.
I'm using 64-bit Windows,but I had installed 32bit version Node.js.
I could install it and it seems working normally, but when I tried to compile existing project, the error message had been shown.
But after I re-install 64-bit version of Node.js, all error had been solved.
If you are using 64bit OS, better to check the version is correct or not.
I'm trying to build a Haskell program (Hets) with Fedora 18. The program compiles fine and it has two options at startup: with GUI or with CLI. If I start it with the CLI then it works fine. If I try to start it with the GUI, I get a white sqaure on screen and then it crashes with this error in the console:
hets: fd:10: hFlush: resource vanished (Broken pipe)
I've built and run the same program on Ubuntu 13.04 so I don't think it's the source code but possibly a library issue on Fedora 18.
Could someone suggest why this might happen?
TIA,
Keith
Update: I've copied the binary over from Ubuntu (where it works) to Fedora and I get the same error message.