I installed Meteor for windows from here :
http://win.meteor.com
The server crashes almost every time I try to make live code push.
I would then have to end the mongod.exe process and run 'meteor reset' and 'meteor' to start it up back again.
Here are the logs:
=> Meteor server restarted
events.js:71
throw arguments[1]; // Unhandled 'error' event
^
Error: This socket is closed.
at Socket._write (net.js:519:19)
at Socket.write (net.js:511:15)
at Socket.HttpProxy.proxyWebSocketRequest.reverseProxy.incoming.socket.on.listeners.onOutgoing (C:\Program Files\Meteor\lib\node_modules\http-proxy\lib\node-http-proxy\http-proxy.js:515:35)
at Socket.EventEmitter.emit (events.js:96:17)
at TCP.onread (net.js:397:14)
Anyone on the same boat? I read from here https://github.com/meteor/meteor/issues/513 that this has been an open issue for over 6 months.
Someone's got any workaround? Help appreciated.
The EADDRINUSE issue was fixed in 0.6.3.1-rev4, but please update to version 0.6.4 as this problem seems to have resolved the other issue by the update to the http-proxy package.
For MSI downloads see https://github.com/sdarnell/meteor/wiki/Windows
Should also appear on http://win.meteor.com soon
This is a known issue with windows for meteor : https://github.com/sdarnell/meteor/issues/7. The one on meteor's github repo might also be related. I have it too! Hopefully they sort it out soon!. Just ctrl+c to stop your server before you edit code and get it back up after you're done.
Even if you start it after this sometimes you could also get an ADDRINUSE error, which is quite frustrating.
Related
Hi this problem just currently started happening and have never had this issue before. Every time I start up my express server it runs fine the first time. When I close the server in my git bash with control C it shuts down but when I try to start up the server again I get the EADDRINUSE error. This makes no sense at all and I have tried to use killall -9 node command without any success does anyone have any suggestions as to what might be going on.
EADDRINUSE error means that the port that your server is trying to use is already being used by something else. My suggestion would be to close all terminal windows first. Then start a completely new terminal window, and then try running the server. If that does not work, restart your laptop(I know this is tedious, but this usually works), and follow the above steps.
When I try to start a meteor project I always get this error message (on my machine only, the project is working fine on my colleague's machines):
=> Started proxy.
=> Started MongoDB.
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EOF
at exports._errnoException (util.js:907:11)
at WriteWrap.afterWrite (net.js:785:14)
Sometimes the error already shows up before mongo is stared.
In fact, I cannot start any project anymore ... :-(
It seems that I have a serious problem with my meteor installation.
I tried re-installing meteor, but no effect.
meteor reset --> no effect
Could it be a problem with a downloaded package? Where does meteor store the packages?
I really would appreaiate any hint what I can try to make it work again.
I'm using meteor on windows.
I would like to know why am I getting the following error when I try to debug node app using node inspector.
Debugger listening on port 5858
events.js:154
throw er; //unhandled 'error' event
Error: spawn C:\Users\Dell\AppData\Local\Google\Chrome\Application\Chrome.exe ENOENT
at exports._errnoException (util.js:890:11)
at Process.ChildProcess._handle.inexit(internal/child_process.js:182:32)
at onErrorNT (internal/child_process.js:348:16)
at _combinedTickCallback (node.js:383:13)
at process._tickCallback (node.js:407:11)
I believe this error was similar to the error reported at https://github.com/node-inspector/node-inspector/issues/732. But however I didn't get as new_chrome.exe.
Any help is appreciated
node version is 5.9.1
node debug version is 0.12.7
EDIT: Actually the problem is chrome.exe file is inside "Program Files(86)" , but while running node-debug it is searching in user folder. So it is something to do with node-module browser-launcher When I run detect.js, in browser-launcher2/examples , its returning me the correct chrome.exe path, but when I run launch.js, it is returning me the above error, since it was trying to find chrome.exe inside user folder. Any thoughts on this?
UPDATE: Added the temporary solution. It worked for me.
NOTE: This is a temporary solution. I am keeping this question open, so as to get a permanent solution for this error. Happy coding :)
I solved the above issue temporarily using James-Browser-Launcher module. Just install the module and run examples/launch.js in the terminal. Once launched, your default browser would open. Now run
node-debug
it launched the browser without error for me. Thats it. It would work now. Hope it works for you too
This works for me:
Go to C:\Users\youruser\ .config\browser-launcher2
open config.json
If there are more than two instances of Chrome, uninstall the error instance first and delete the error entry at file and his associated folder in this path. In my case, the error was Chrome Canary :
Example
And then, node-inspector works with Standar Chrome!!!
I'm trying to transfer my application to a new machine. It works on the old machine perfectly, and I have been trying to copy the settings as closely as possible, but there is something missing. This is the error I'm getting:
Unhandled rejection SequelizeConnectionError: Handshake inactivity timeout
at Handshake._callback (/Applications/MAMP/htdocs/dashboard-server/node_modules/sequelize/lib/dialects/mysql/connection-manager.js:63:20)
at Handshake.Sequence.end (/Applications/MAMP/htdocs/dashboard-server/node_modules/mysql/lib/protocol/sequences/Sequence.js:96:24)
at /Applications/MAMP/htdocs/dashboard-server/node_modules/mysql/lib/protocol/Protocol.js:393:18
at Array.forEach (native)
at /Applications/MAMP/htdocs/dashboard-server/node_modules/mysql/lib/protocol/Protocol.js:392:13
at doNTCallback0 (node.js:417:9)
at process._tickCallback (node.js:346:13)
Thoughts?
Just confirmed the problem is either Sequelize / mysql in conjunction with Node 4.2.0 after manually re-installing 4.1.1 my problems went away.
Downgrade to Node 4.1.x or wait for a patch/fix/etc to solve your issues.
Additional Information
The bug has been reported here on the node-mysql repository issue tracker. Seems someone regressed something in Node 4.2.0 and it wasn't caught. Here's the pull request to fix it which was merged in and is in the candidate for 4.2.1.
Update Oct 13th, 2015
Node 4.2.1 was just released (Changelog) containing the aforementioned fix. Upgrading to 4.2.1 should also fix your problems.
I'm having some troubles with statsD from etsy, and seeing that i'm not really experienced with javascript I thought I should ask a question maybe somebody has encountered this error before, because sadly this time google hasn't been that helpful.
The troubles have started a couple of days ago when I decided to restart the node process that was keeping statsD up, when after the restart it just wouldn't start. It gives me the following output:
2 Jul 03:02:08 - reading config file: /opt/statsd/statsd/psrkConfig.js
2 Jul 03:02:08 - server is up
2 Jul 03:02:08 - Loading backend: ./backends/graphite
events.js:72
throw er; // Unhandled 'error' event
^
Error: bind Unknown system errno 92
at errnoException (dgram.js:440:11)
at dgram.js:207:28
at dns.js:72:18
at process._tickCallback (node.js:415:13)
First of all I think I should have described a little my environment. I'm using gentoo as an OS, I have net-libs/nodejs-0.10.10 installed on the system(was actually 0.10.8 but I upgraded in my search for the problem resolution) and I have cloned the latest etsy/statsD repo from git. I have also tried with the npm version of statsD but got the same behaviour.
I tried following the program with strace and got to the error, but I have no idea how to procede forward. The syscall that fails from what I'm guessing is the following one:
setsockopt(11, SOL_SOCKET, 0xf /* SO_??? */, [1], 4) = -1 ENOPROTOOPT (Protocol not available) <0.000009>
but it has to be called from somewhere inside statsD (making it easier to debug), and I could not find it.
I would appreciate any kind of little help or pointers, because I'm guessing the error comes form the node.js libraries and I'm pretty clueless about them. Thank you.
similar to #user1135, had trouble with binding to UDP sockets on a recent build of debian/testing. we commented out the #ifdef sections in udp.c and recompiled to fix the problem.
I had a similar problem recently, also on Gentoo Linux. It so happened I had the 3.9 linux headers installed but was still running an older kernel. This caused SO_REUSEPORT to be defined when building node.js (specifically uv). Going back to the proper header version or doing #undef SO_REUSEPORT inside of deps/uv/src/unix/udp.c should fix it. Also upgrading to a 3.9+ kernel would do it.