Develop Reference

Node js WebSocket (NPM ws) not returning ping response when windows application in minimize mode

I am using NPM ws in my backend project. and i have added ping-pong logic if not getting response of ping in 45 seconds then i'm terminating the web socket connection.
Above logic is working when I'm minimizing the chrome tab I'm still getting the response of ping.
But the same code When I'm minimizing the windows application i can see the logs, not getting the response of ping. also i can see the webSocket connection active but not getting the response for ping

Can't deploy todos; Failed to remove container (todos-frontend)

First time with linux and meteor up, so sorry if there's a stupid mistake. I try to deploy the meteor example app todos with mupx, and followed the instructions from the readme, but I'm getting the following mistake. (I'm using Ubuntu 14.04 LTS Server ). Thanks for help.
Configuration file : mup.json
Settings file : settings.json
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Meteor app path : /home/jan/todos
Using buildOptions : {}
Currently, it is only possible to build iOS apps on an OS X system.
Started TaskList: Deploy app 'todos' (linux)
[h2544161.stratoserver.net] - Uploading bundle
[h2544161.stratoserver.net] - Uploading bundle: SUCCESS
[h2544161.stratoserver.net] - Sending environment variables
[h2544161.stratoserver.net] - Sending environment variables: SUCCESS
[h2544161.stratoserver.net] - Initializing start script
[h2544161.stratoserver.net] - Initializing start script: SUCCESS
[h2544161.stratoserver.net] - Invoking deployment process
Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
Failed to remove container (todos-frontend): Error response from daemon: No such container: todos-frontend
docker: Error response from daemon: failed to create endpoint todos on network bridge: Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.
-----------------------------------STDOUT-----------------------------------
todos
base: Pulling from meteorhacks/meteord
518dc1482465: Already exists
a3ed95caeb02: Already exists
a3ed95caeb02: Already exists
a3ed95caeb02: Already exists
537c534356b6: Already exists
b65a0e1e554b: Already exists
a3ed95caeb02: Already exists
a3ed95caeb02: Already exists
Digest: sha256:b5a4f6efa98e4070792ed36d33b14385a28e6ceda691a492ee5b9f2431b1515a
Status: Image is up to date for meteorhacks/meteord:base
d6d192579495851d5817288ff89abb69512562d7c2a7075f965484e64583c61b

Failed to remove container (todos-frontend): Error response from daemon: No such container: todos-frontend
docker: Error response from daemon: failed to create endpoint todos on network bridge: Bind for 0.0.0.0:80 failed: port is already allocated.
Just had the same issue,
finally deployed after changing file port number to an unused port in my-deployment mup.json somehow docker service could release ports automatically when it wants. I've used 80, 8000, 8001 so far but I haven't successfully deployed to the same port twice, but reading
credit to this
It seems that different deployments may conflict each other pretty easily. I have no resolution for this.

Write EIO error after client disconnects from console

I have Node.js application with Express.js web framework. This application run on linux server. One of modules writes to console through console.log command. When client disconnects from console, application crashes with error message "write EIO". Please can anyone help me with this problem? Can i fix this problem in application settings or in server settings?

nodejs mobwrite on windows

I'm trying to setup nodejs mobwrite. I have node working & python installed, and I followed the simple setup steps, but I keep getting this console error in the browser.
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
http://localhost:8000/mobwrite/sync
https://github.com/mjpizz/node-mobwrite
I'm a bit of a newb when it comes to nodejs.

Fixed it.
Copy mobwrite_daemon.py from node_modules/mobwrite/ext/google-mobwrite/daemon, and put it in the directory above it. Dbl click on that to start it in python.
Then start up mobwrite in nodejs. woila!

How I can run this script in node.js?

I have install all modules need to run this script using CMD. When I am run this script in node.js through webmatrix:
var http = require('http');
var everyauth = require('everyauth');
var app = require('express').createServer();
app.get('/', function(request, response) {
response.send('Hello Express!!');
});
app.listen(2455);
It's not working. The error is:
iisnode encountered an error when processing the request.
HRESULT: 0x2
HTTP status: 500
HTTP reason: Internal Server Error
You are receiving this HTTP 200 response because system.webServer/iisnode/#devErrorsEnabled configuration setting is 'true'.
In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.
The node.exe process has not written any information to the stdout or stderr.
I have tried with different different script from blog but they do not work. I tried Steven Sanderson's template in webmatrix and that does work.

To use your application with iisnode, you have to use port/socket supplied by iisnode (as in this case you're using IIS as a webserver instead of the one bundled in node).
Replace the last line with app.listen(process.env.port || 2455);, so that it will both work well with iisnode and be available on port 2455 when run with node.exe app.js.

Use
app.listen(process.env.port || 2455);
instead of `
app.listen(portno);
cause it's iisnode web server.