Referring to the above picture, can someone please tell my why my NPM script would continually fail saying that node is not recognized.
nodejs is clearly in my $PATH and it correctly identifies where it is on my computer outside of an npm script.
I am using Git Bash inside ConEMU on Windows Version 10.0.17134 Build 17134.
I wouldn't be surprised if the issue is with Windows, as the problem seems to have popped up since the latest OS update, installed just over a week ago (I've been having this issue for around that same amount of time)
I have finally got it working! It is, unsurprisingly, a Windows issue.. Because I had a few entries in my $PATH, and the nodejs one was at the end, Windows would silently fail when reading the entire path, and not get as far as the nodejs entry. The fix was to move the nodejs in the Environment Variables control panel to the very top
Perhaps this problem is specific to upgrading an Ubuntu 12.04 that is using tftp-hpa as part of a standard LTSP installation. After upgrading to 14.04 using do-release-upgrade the tftp-hpa daemon failed to start in a confusing way.
Using either systemV or the upstart method it pretended to start (it would complain if I tried to start it again without first "stopping" it) but no daemon appeared in the ps listing AND any attempt to download something via
tftp localhost generated a time out.
(Posted as an answer on behalf of the OP).
I traced the problem to the --address flag by attempting to start the daemon by hand. It worked if I left out the --address flag altogether but refused to start with any of the standard "0:0:0:0:69" like constructions.
Since "--address TFTP_ADDRESS" is baked into the the upstart script,
it did not work to remove TFTP_ADDRESS entirely from /etc/default/tftp-hpa. However setting
TFTP_ADDRESS :69
in /etc/default/tftp-hpa seems to have solved the problem.
Also, the upgrade from 12.04 to 14.04 left /var/lib/tftpboot owned by root, which generated the complaint
in.tftpd[3084]: cannot set groups for user nobody
in syslog.
I am using a fresh Linux install. I am trying to install Meteor. Using Ubuntu 12.04, Centos and Ubuntu 13.04. I installed Node.js, Meteor and Meteorite.
Error:
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Can't start mongod
MongoDB had an unspecified uncaught exception.
This can be caused by MongoDB being unable to write to a local database.
Check that you have permissions to write to .meteor/local. MongoDB does
not support filesystems like NFS that do not allow file locking.
I've tried:
Deleting .meteor/local/db/mongod.lock
Also I tried to change the permissions for the whole project with chmod.
Do you recommend any Ubuntu distribution?
Thanks in advance.
I have run in this problem before (after meteor update or abnormal meteor termination) and these solutions worked for me before.
Restart your machine.
Delete the file .meteor/local/db/mongod.lock and run meteor again.
Execute meteor reset and start again, but this command will erase your database.
Hope it helps.
It some time depends on your locale settings.
Meteor reset and delete mongod.lock didn't help in my case.
I've fixed it by running
export LC_ALL=C
you can add this line to
sudo vim /usr/local/bin/meteor
All I had to do was run "killall mongod" in the terminal. After that it worked again. I believe it may have cleared parts of the database though.
For me a combination of the suggestions worked out. The answer that has gotten 2 down votes! and this one from another page.
sudo vim /usr/local/bin/meteor
export LC_ALL="en_US.UTF-8"
then make sure which port your mongodb is running at by issuing the following:
meteor mongo
You will get a response like this:
connecting to: 127.0.0.1:3001/meteor
now that you know the port on which the mongo is configured, add the following to the same file we have been editing:
export MONGO_URL=mongodb://127.0.0.1:3001/meteor
Now you are good to go. Of course "meteor reset" works but if you dont want to loose your data, stick with those two export lines.
I have found that setting MONGO_URL helps avoid issue
export MONGO_URL=mongodb://localhost:27017/your_db
If you're having this issue running Ubuntu inside Vagrant/VirtualBox, then the problem come from working in the synced vagrant folder.
The workaround is to initialize the .meteor directory in the home directory and to mount it in the synced folder. Assuming your meteor app is called MyApp and the /vagrant is the synced folder, here's how to do it:
cd ~
meteor create MyApp
cd MyApp
meteor
cd /vagrant/MyApp
sudo mount --bind ~/MyApp/.meteor/ .meteor
meteor
I had a similar issue. It was due to the fact that my project directory was part of my Dropbox and there was some conflicted files in the .meteor/local/db directory. Removing these solved the problem.
I encounter the same issue when my disk space ran low.
Freeing up some space in the disk fixed the problem for me.
I encountered this problem when I ran meteor in VMWare, ubuntu 14.04 guest on a Windows 7 host. The problem was that I was running meteor/mongo in a shared directory. When I used a non-shared directory (~/meteor/project) the problem disappeared.
Following the steps that #Oscar mentions further up should sort you out.
However in my case meteor reset wouldn't work, telling me this:
reset: Meteor is running.
This command does not work while Meteor is running your application. Exit the running Meteor development server.
For which I tracked the process down, like this:
$ ps aux | grep meteor --color=auto
which gave me this info:
$ myUser 71981 0.5 0.0 2849208 3644 ?? S Mon02pm 4:25.27 /Users/myUser/.meteor/packages/meteor-tool/.1.1.10.1b51q9m++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod --bind_ip 127.0.0.1 --smallfiles --port 2001 --dbpath /Users/jgt/Documents/Projects/todos/.meteor/local/db --oplogSize 8 --replSet meteor
As you can see I'm on Mac, but this works fine on any Unix based OS.
So then you only need to kill the process by it's id, like this:
$ kill -9 71981
And finally run again meteor reset
That's it, got it working now. Hope it helps.
One option is to wait until you have your app on a staging or production server, and then test it on an Android emulator provided by Android Studio or BlueStacks.
I am having this issue on WSL for Ubuntu on Windows. The only solution that worked for me was creating a remote mongodb with mLabs and ran the following
export MONGO_URL=mongodb://username:password#randomurl.mlab.com:port#/project
Recently I got the same case, which I run meteor on WSL for Ubuntu on windows 10. I resolved this case by updating WSL to version 2.
Note :
Make sure your Windows build is higher than the minimum WSL 2 requirements. And don't forget to set version 2 as WSL default version after updating.
wsl --set-version [linux_dist] 2
For windows 10, I moved all my Meteor projects in drive C. So far working.
For the better part of a day now I've been trying to get node.js to work on my computer.
Even though I get no errors during installation, whenever i try to run node or npm from the command line I only get the error "Evented I/O for V8 JavaScript has stopped working" and then nothing happens.
I really have no clue why it isn't working and what I have to do to get it to work! Has anyone else ever had the same problem and were you able to fix it somehow?
It seems the problem was with ansicon which I installed together with cucumber.
I was able to fix the problem by running "ansicon -u" in my x64 folder
I am just trying out Meteor on my Windows 7 enterprise 64 bit box. I installed it via MSI from http://win.meteor.com, rebooted the machine and in command prompt (administrator), did the following:
cd /d c:\var
meteor create testapp
(absolutely no response on console)
Then I insured that node.exe is working. I created a test.js with basic hello world example and it worked (I browsed to the localhost:xxx and was greeted).
node test.js
Then I went right into the meteor.js code, and upon encountering process.stderr.write inside fiber(...), I decided to call the same at the beginning of the file outside fiber.
process.stderr.write("outside fiber");
(this message got printed
; confirmed that there is a problem with fibers)
Now upon research, I stumble upon
npm test fibers
(output: Error: Test already-running.js failed.
code: -1073741819 ....)
Then I did
npm remove fibers
npm install fibers
However, the error with test fiber continues so does the absolute no-output from meteor command.
could anybody help? I'm out of options and this is my first attempt at meteor/nodejs.
I have discovered an issue with node fibers (on windows) and have a tentative fix - at least it fixed the problem for me, and I would be interested to see if that also fixes it for others.
Ultimately the problem was apparently sudden death due stack overflow and access violation. The root cause however was that the thread locals were not correctly being switched on a fiber switch.
Please see https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for details.
See related Stack Overflow question: Meteor on Windows: meteor command outputs nothing
You need to know that, by now, meteor dont officially support windows.
I can recommend you to try using virtualbox and a linux distro in a virtual machine.