Error: Couldn't run ps ax: {} #2158
Comments
We still want JSON.stringify too because that includes stuff like the exit code. See #2158
OK, first off we have an error handling problem: we should get more information than It's pretty surprising to me that this doesn't work for you. ps is a basic Unix command that should ship with all Macs. Can you show the terminal output from these commands? ps ax
which ps
type -a ps
echo $PATH
ls -l /bin/ps What version of Mac OS X are you running |
Hi, thanks for the help! Sure, the output is as follows: ps ax
which ps:
type -a ps:
echo $PATH
ls -l
I also applied your fix to my location installation, and I got a better, but still very weird, error message:
This might be something, but I'm not sure if it applies to Meteor also: gmarty/grunt-closure-compiler#12 |
Btw, I'm running 10.9.2 of MacOSX |
I found it, thanks for adding the patch! The problem is that there's an 'exec' of the ps ax, and it's exceeding the limit of 'exec'. There seem to be 2 solutions: increase the maxBuffer, which is what I did by adding {maxBuffer: 1024*1024}, or spawn the process instead, which seems to be the better solution. If you want, I can try to write a fix using the spawn? |
spawn is actually subtle enough (properly piping, using the right events, etc... we've messed this up before) that I'd rather just boost the maxBuffer. 10MB should be enough, riiiiiiight? Thanks for tracking this down. |
I was experiencing this with Meteor 0.8.1.3, and I solved the issue by closing several of my many open applications. |
This was fixed in Meteor 0.8.2 last June, for the record. |
Hi all,
I just downloaded the newest version of Meteor, and when I try to start a simple application on my Mac, I get the following error: Error: Couldn't run ps ax: {}
The text was updated successfully, but these errors were encountered: