The only answer on this question I saw - go start another copy on the different port. Switching from one Meteor workspace to another Okay, I see that I can run another one o
An edit to John Devor's (accepted) answer: if you're editing your code with Atom, his command may kill the editor instances:
$ ps ax | grep node | grep meteor
19312 pts/2 Sl+ 0:16 /home/teo/.meteor/packages/meteor-tool/.1.1.4.e4elpj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node /home/teo/.meteor/packages/meteor-tool/.1.1.4.e4elpj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/tools/main.js
19541 pts/2 Sl+ 0:02 /home/teo/.meteor/packages/meteor-tool/.1.1.4.e4elpj++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node /home/teo/meteor/beari/dist/.meteor/local/build/main.js
24438 ? Sl 0:00 /usr/share/atom/atom --no-deprecation /home/teo/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --reporter /home/teo/.atom/packages/linter-jshint/node_modules/jshint-json/json.js --filename /home/teo/meteor/beari/beari.js -
Better to use a command like:
kill -9 `ps ax | grep node | grep meteor | grep -v atom | awk '{print $1}'`