search

meteorhacks / npm

Complete NPM integration for Meteor
http://meteorhacks.com/complete-npm-integration-for-meteor.html
MIT License
509 stars 43 forks source link

can't run meteor get enomem error #114

Open dredgerman opened 8 years ago

dredgerman commented 8 years ago

Hi,

Did clean install of centos 7 minimal, virtual min and only changes to configuration of server are editing iptables and setting up firewall wanted fresh start to install meteor,

installed perfect and as sudo, who has root privileges,

created new myapp as per tutorial for beginners,

when I run myapp it crashes in local folder and produces enomem error not got first clue about what could be wrong followed instructions to letter and this is supposed to be simple to use!

thanks for any help given....path to myapp folder is /home/tomsudo/myapp

[tomsudo@server myapp]$ ls -alsh total 24K 4.0K drwxr-xr-x 3 tomsudo tomsudo 4.0K Nov 25 09:10 . 4.0K drwx------ 6 tomsudo tomsudo 4.0K Nov 25 09:10 .. 4.0K drwxr-xr-x 3 tomsudo tomsudo 4.0K Nov 25 09:10 .meteor 4.0K -rw-rw-r-- 1 tomsudo tomsudo 31 Nov 25 09:10 myapp.css 4.0K -rw-rw-r-- 1 tomsudo tomsudo 218 Nov 25 09:10 myapp.html 4.0K -rw-rw-r-- 1 tomsudo tomsudo 478 Nov 25 09:10 myapp.js [tomsudo@server myapp]$ meteor [[[[[ ~/myapp ]]]]]

=> Started proxy. => Started MongoDB.

/home/tomsudo/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:245 throw(ex); ^ Error: spawn ENOMEM at errnoException (child_process.js:1011:11) at ChildProcess.spawn (child_process.js:958:11) at Object.exports.spawn (childprocess.js:746:9) at [object Object]..extend.spawn (/tools/runners/run-app.js:255:31) at [object Object]..extend.start (/tools/runners/run-app.js:85:22) at [object Object]._.extend.runOnce (/tools/runners/run-app.js:716:16) at [object Object]..extend._fiber (/tools/runners/run-app.js:858:28) at /tools/runners/run-app.js:396:12 [tomsudo@server myapp]$

CraneArmy commented 8 years ago

enomom means "error no memory"

I'm no expert, but the only resolution I know of may be to run on a larger instance.

node and especially node + meteor is no lightweight, I've run into similar problems with other node frameworks. you may be better off going to a dedicated node / meteor host or creating a bigger instance.