search

zone117x / node-open-mining-portal

A scalable all-in-one easy to setup cryptocurrency mining pool and portal written entirely in Node.js.
GNU General Public License v2.0
1.02k stars 1.03k forks source link

Fork´s dying #292

Open deathsonic18 opened 10 years ago

deathsonic18 commented 10 years ago

For some reason Fork's 0 and 1 are dying every 3-5 seconds

I updated it to the latest version and this is my 2nd install of it; everything is running smoothly except this

events.js:72 throw er; // Unhandled 'error' event ^ Error: bind EADDRINUSE at errnoException (net.js:901:11) at net.js:1081:30 at Object.135:1 (cluster.js:592:5) at handleResponse (cluster.js:171:41) at respond (cluster.js:192:5) at handleMessage (cluster.js:202:5) at process.EventEmitter.emit (events.js:117:20) at handleMessage (child_process.js:318:10) at child_process.js:392:7 at process.handleConversion.net.Native.got (child_process.js:91:7) 2014-06-16 07:11:13 [Master] [PoolSpawner] Fork 0 died, spawning replacement worker... 2014-06-16 07:11:15 [Switching] [Setup](Thread 2) Loading last proxy state from redis 2014-06-16 07:11:15 [Pool] [bitcoin](Thread 2) Share processing setup with redis (127.0.0.1:6379)

events.js:72 throw er; // Unhandled 'error' event ^ Error: bind EADDRINUSE at errnoException (net.js:901:11) at net.js:1081:30 at Object.136:1 (cluster.js:592:5) at handleResponse (cluster.js:171:41) at respond (cluster.js:192:5) at handleMessage (cluster.js:202:5) at process.EventEmitter.emit (events.js:117:20) at handleMessage (child_process.js:318:10) at child_process.js:392:7 at process.handleConversion.net.Native.got (child_process.js:91:7) 2014-06-16 07:11:15 [Master] [PoolSpawner] Fork 1 died, spawning replacement worker... 2014-06-16 07:11:15 [Switching] [Setup](Thread 1) Loading last proxy state from redis 2014-06-16 07:11:15 [Pool] [bitcoin](Thread 1) Share processing setup with redis (127.0.0.1:6379)

events.js:72 throw er; // Unhandled 'error' event ^ Error: bind EADDRINUSE at errnoException (net.js:901:11) at net.js:1081:30 at Object.137:1 (cluster.js:592:5) at handleResponse (cluster.js:171:41) at respond (cluster.js:192:5) at handleMessage (cluster.js:202:5) at process.EventEmitter.emit (events.js:117:20) at handleMessage (child_process.js:318:10) at child_process.js:392:7 at process.handleConversion.net.Native.got (child_process.js:91:7) 2014-06-16 07:11:15 [Master] [PoolSpawner] Fork 0 died, spawning replacement worker...

nicoschtein commented 10 years ago

Something is already bound to that port, check if you have other services or another instance running.

On Jun 16, 2014, at 2:13 AM, deathsonic18 notifications@github.com wrote:

For some reason Fork's 0 and 1 are dying every 3-5 seconds

I updated it to the latest version and this is my 2nd install of it; everything is running smoothly except this

events.js:72 throw er; // Unhandled 'error' event ^ Error: bind EADDRINUSE at errnoException (net.js:901:11) at net.js:1081:30 at Object.135:1 (cluster.js:592:5) at handleResponse (cluster.js:171:41) at respond (cluster.js:192:5) at handleMessage (cluster.js:202:5) at process.EventEmitter.emit (events.js:117:20) at handleMessage (child_process.js:318:10) at child_process.js:392:7 at process.handleConversion.net.Native.got (child_process.js:91:7) 2014-06-16 07:11:13 [Master] [PoolSpawner] Fork 0 died, spawning replacement worker... 2014-06-16 07:11:15 [Switching] Setup Loading last proxy state from redis 2014-06-16 07:11:15 [Pool] bitcoin Share processing setup with redis (127.0.0.1:6379)

events.js:72 throw er; // Unhandled 'error' event ^ Error: bind EADDRINUSE at errnoException (net.js:901:11) at net.js:1081:30 at Object.136:1 (cluster.js:592:5) at handleResponse (cluster.js:171:41) at respond (cluster.js:192:5) at handleMessage (cluster.js:202:5) at process.EventEmitter.emit (events.js:117:20) at handleMessage (child_process.js:318:10) at child_process.js:392:7 at process.handleConversion.net.Native.got (child_process.js:91:7) 2014-06-16 07:11:15 [Master] [PoolSpawner] Fork 1 died, spawning replacement worker... 2014-06-16 07:11:15 [Switching] Setup Loading last proxy state from redis 2014-06-16 07:11:15 [Pool] bitcoin Share processing setup with redis (127.0.0.1:6379)

events.js:72 throw er; // Unhandled 'error' event ^ Error: bind EADDRINUSE at errnoException (net.js:901:11) at net.js:1081:30 at Object.137:1 (cluster.js:592:5) at handleResponse (cluster.js:171:41) at respond (cluster.js:192:5) at handleMessage (cluster.js:202:5) at process.EventEmitter.emit (events.js:117:20) at handleMessage (child_process.js:318:10) at child_process.js:392:7 at process.handleConversion.net.Native.got (child_process.js:91:7) 2014-06-16 07:11:15 [Master] [PoolSpawner] Fork 0 died, spawning replacement worker...

— Reply to this email directly or view it on GitHub.

jacobnollette commented 10 years ago

I'm having this issue when I quickly relaunch nomp... If what @nicoschtein says is true, nomp services aren't closing out entirely when I ctrl-c to close down the node. Waiting about 45 seconds usually clears the issue for me.

sigwo commented 10 years ago

I push ctrl+c and restart NOMP in about 2-3 seconds. I've not had to wait that long before.

On Sunday, August 31, 2014, Jacob Nollette notifications@github.com wrote:

I'm having this issue when I quickly relaunch nomp... If what @nicoschtein https://github.com/nicoschtein says is true, nomp services aren't closing out entirely when I ctrl-c to close down the node. Waiting about 45 seconds usually clears the issue for me.

— Reply to this email directly or view it on GitHub https://github.com/zone117x/node-open-mining-portal/issues/292#issuecomment-53980222 .