zone117x / node-open-mining-portal Goto Github PK

ReferenceError: t is not defined
at /root/NOMP/node-stratum-portal/libs/paymentProcessor.js:124:140
at Array.filter (native)
at /root/NOMP/node-stratum-portal/libs/paymentProcessor.js:122:43
at /root/NOMP/node-stratum-portal/node_modules/stratum-pool/lib/daemon.js:134:13
at IncomingMessage. (/root/NOMP/node-stratum-portal/node_modules/stratum-pool/lib/daemon.js:91:21)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:920:16
at process._tickCallback (node.js:415:13)

Coinswitch listener has incoming connection
2014-04-10 08:10:02 [Master] [Coinswitch] Coinswitch listener received switch request

/node-open-mining-portal/libs/poolWorker.js:55

            var oldCoin = proxySwitch[algo].currentPool;
   /node-open-mining-portal/libs/poolWorker.js:55
                                    ^
            var oldCoin = proxySwitch[algo].currentPool;
                                 TypeError: Cannot read property 'currentPool' of undefined
at process.<anonymous> (/node-open-mining-portal/libs/poolWorker.js:55:48)
at process.EventEmitter.emit (events.js:117:20)
at handleMessage (child_process.js:318:10)
at Pipe.channel.onread (child_process.js:345:11)
      ^

/node-open-mining-portal/libs/poolWorker.js:55
var oldCoin = proxySwitch[algo].currentPool;
/node-open-mining-portal/libs/poolWorker.js:55
^
TypeError: Cannot read property 'currentPool' of undefined
at process. (/node-open-mining-portal/libs/poolWorker.js:55:48)
at process.EventEmitter.emit (events.js:117:20)
at handleMessage (child_process.js:318:10)
at Pipe.channel.onread (child_process.js:345:11)
var oldCoin = proxySwitch[algo].currentPool;
^
TypeError: Cannot read property 'currentPool' of undefined
at process. (/node-open-mining-portal/libs/poolWorker.js:55:48)
at process.EventEmitter.emit (events.js:117:20)
at handleMessage (child_process.js:318:10)
at Pipe.channel.onread (child_process.js:345:11)
TypeError: Cannot read property 'currentPool' of undefined
at process. (/node-open-mining-portal/libs/poolWorker.js:55:48)
at process.EventEmitter.emit (events.js:117:20)
at handleMessage (child_process.js:318:10)
at Pipe.channel.onread (child_process.js:345:11)

undefined:2
[pool].workers).length)+' '+(it.stats.pools[pool].poolStats.validShar
Help ?

Can we set log level in config ?
when I have X GHs login every share is waste of time for CPU ;)

2014-03-27 03:57:59 [Payments] [Litecoin] error with requesting transaction from block daemon: {"result":null,"error":{"code":-5,"message":"Invalid or non-wallet transaction id"},"id":1395878279590}
2014-03-27 03:57:59 [Payments] [Litecoin] daemon did not give us back a transaction that we asked for: 04ad8b679e42c4af7817dc0456e32544d978fba7c1dc19667c60a0a363feeaa6

Also I can see that wallet balance somehow became smaller so it looks like blocks were "dropped" (?). Any idea why is this happening and shouldn't we clean _blocksPending in redis too?

:)

I restarted my SQL server real quick with MPOS compatibility mode. Mining was still working but shares were not being credited and NOMP made no attemp to reconnect to SQL

it should save a lot of work once identified and put in coin definitions

How exactly do you message the application to switch coins?

http://pastebin.com/R9dcRdBp

also, i have been seeing quite a few of these errors messages:
2014-03-30 21:27:55 [Pool] [Megacoin](Fork 0) Invalid share submitted, share data: {"job":"103","ip":"miner.miner.miner.miner","worker":"15563823969922115034","difficulty":64,"error":"low difficulty share"}

As I am running NOMP with mpos compatibility mode on Amazon RDS,
I could find that NOMP does not recover automatically from DB disconnect.

Amazon RDS may fail over to Multi-AZ sometimes and it takes about 2 minutes of disconnection.

There is connect() code for failure.
https://github.com/zone117x/node-open-mining-portal/blob/master/libs/mposCompatibility.js#L31

But when it fails to connect at that moment, it doesn't try to reconnect any more.
I think setTimeout() function needs to be placed.

Hi again. An idea came to my mind as i work with nomp.

Wouldn't be a good idea to make a ghaph for earch scrypt (or at least split sha from scrypt?)

I am Telling this because sha gives ghashes and scypt khashes. so everytime someone changes the page he has to remouve all the sha coins to see the scypt hashrates..

that only. Have a nice kai peacefull morning

Having an error when launching NOMP for the first time. Have been extra careful trying to be excat with all instructions. Any insight all other pages on google with error 348 were not helpful. Thanks

buffer.js:348
ret = this.parent.hexWrite(string, this.offset + offset, length);
^
TypeError: Invalid hex string
at Buffer.write (buffer.js:348:25)
at new Buffer (buffer.js:215:28)
at new module.exports (/home/crypto/nomp/node_modules/stratum-pool/lib/peer.js:49:17)
at SetupPeer (/home/crypto/nomp/node_modules/stratum-pool/lib/pool.js:201:22)
at /home/crypto/nomp/node_modules/stratum-pool/lib/pool.js:67:25
at /home/crypto/nomp/node_modules/stratum-pool/lib/pool.js:103:13
at /home/crypto/nomp/node_modules/stratum-pool/lib/pool.js:664:21
at itemFinished (/home/crypto/nomp/node_modules/stratum-pool/lib/daemon.js:156:36)
at /home/crypto/nomp/node_modules/stratum-pool/lib/daemon.js:169:17
at IncomingMessage. (/home/crypto/nomp/node_modules/stratum-pool/lib/daemon.js:91:21)
2014-04-18 14:54:08 [Master] [PoolSpanwer] Fork 0 died, spawning replacement worker...
Litecoin ffff00000000000000000000000000000000000000000000000000000000

Doesn't seem to properly catch Invalid Authentication

# node init.js
2014-03-08 01:03:57 [system]:   [blocknotify] Blocknotify listener disabled
2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] Starting pool for Dogecoin [DOGE]
2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] Connecting to daemon(s)
2014-03-08 01:03:57 [mysql]:    [Dogecoin (Fork 0)] Successful connection to MySQL database
2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] could not parse rpc data from method: getinfo on instance 0 data: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>Error</TITLE>
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=ISO-8859-1'>
</HEAD>
<BODY><H1>401 Unauthorized.</H1></BODY>
</HTML>

2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] could not parse rpc data from method: validateaddress on instance 0 data: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>Error</TITLE>
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=ISO-8859-1'>
</HEAD>
<BODY><H1>401 Unauthorized.</H1></BODY>
</HTML>

2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] validateaddress rpc error on daemon instance 0, error +{}
2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] Could not start pool, "not all addresses are valid"
2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] could not parse rpc data from method: getmininginfo on instance 0 data: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>Error</TITLE>
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=ISO-8859-1'>
</HEAD>
<BODY><H1>401 Unauthorized.</H1></BODY>
</HTML>

2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] getmininginfo on init failed with daemon instance 0, error {}
2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] could not parse rpc data from method: submitblock on instance 0 data: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>Error</TITLE>
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=ISO-8859-1'>
</HEAD>
<BODY><H1>401 Unauthorized.</H1></BODY>
</HTML>

2014-03-08 01:03:57 [system]:   [Dogecoin (Fork 0)] Could not detect block submission RPC method

I noticed you intended on developing an upstream pool connection capability. I wanted to bring to your attention ProxyPool. It was developed specifically for p2pool, but works with most other pools as well when properly implemented. You may have seen it, the issue is that it is not in node.js. However, it tracks shares with redis. I would work on this myself, but I've not spent enough time with the your code yet to figure out how easy this would be and I'm by no means an expert with node.js but I thought I'd share it with you.

Either by my own incompetence or some weird error, my redis database was wiped after i re initiated nomp. but, un like last time -- all the stats initiated at 0 !

It should be data.difficulty at the line 126

logger.debug(logSystem, logComponent, logSubCat, 'Valid share diff of ' + data.difficultiy + ' submitted by worker ' + data.worker + ' [ ' + data.ip + ']' );

The problem is that my diff is set to 0.005, vardiff at 0.005-0.100
I have potcoin and darkcoin on one stratum using NOMP, withouth telling NOMP, he spawned 2 threads for dark and 2 for potcoin, but when the time to change the diff on x11(darkcoin), one thread goes to 0.01, other stays on 0.005, both accepting and writing shares from same worker..

Hi
I try to change minDiff and poolDiff but always my miner start at 16 diff
evenretarget time don't do antyhing :/

EDIT:
hmm..

 pool difficulty was set higher than network difficulty of 0.80280034
lowering pool diff from 64 to 16

lol ?

/prod/nomp-mining-portal/libs/poolWorker.js:171
pools[proxyStuff.curActivePool].getStratumServer().handleNewCl
^
TypeError: Cannot call method 'getStratumServer' of undefined

/root/node-open-mining-portal/node_modules/posix/lib/posix/index.js:21
throw "unable to load the node-posix extension module";
^
unable to load the node-posix extension module

Hey,
I am really lame at using GitHub, so I can't provide pull request.

I'm trying your pool with one keccak coin (CryptoMETH), and it's doing great.
But hashrate in the website is waaay of.

The way to fix it, is editing node_modules/stratum-pool/lib/algoProperties.js and setting in keccak section: multiplier: Math.pow(2, 24)

Then the hashrates seem to be fine.

Thanks for amazing work with this pool!

is it possible to modify the proxy to support mining multiple coins simultaneously?
Use something to keep track of which worker is going to which daemon and then route the traffic appropriately?
With perhaps options in the config.json for the how to distribute the traffic? (ie, 50/50 for two coins or 25/25/50 between three coins for example)

Perhaps this should be related to the other feature request for pulling pool profitability data automatically.

/root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/node_modules/bindings/bindings.js:91
throw err
^
Error: Could not locate the bindings file. Tried:
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/build/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/build/Debug/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/build/Release/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/out/Debug/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/Debug/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/out/Release/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/Release/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/build/default/scrypthash.node
→ /root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/compiled/0.10.24/linux/x64/scrypthash.node
at bindings (/root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/node_modules/bindings/bindings.js:88:9)
at Object. (/root/nomp/node_modules/stratum-pool/node_modules/scrypt256-hash/index.js:1:99)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/root/nomp/node_modules/stratum-pool/lib/algoProperties.js:1:76)
at Module._compile (module.js:456:26)

help me

Hello! with quark, MPOS has reported my last found blocks, the only one's I have found, with shares of 1, and shares of 0, even though tons more have been submitted!

This is at least a minor inconvenience, but should be fixed!

The coin has a hard fork.I didn't update.
when on the the hard fork block ,a lot of connections make the server error and cpu reach 100%.

Hi, love your work! You have a feature planned:

"To reduce variance for pools just starting out which have little to no hashing power a feature is planned which will allow your own pool to connect upstream to a larger pool server. It will request work from the larger pool then redistribute the work to our own connected miners."

Any idea on when this will happen ? Happy to donate towards this!

after the new update the nomp doen't pays out at all doen't even shows the blocks.

"zadd" "statHistory" "1397836894" "{"time":1397836894,"global":{"workers":1,"hashrate":0},"algos":{"scrypt":{"workers":0,"hashrate":0,"hashrateString":"0.00 KH"},"scrypt-n":{"workers":0,"hashrate":0,"hashrateString":"0.00 KH"},"x11":{"workers":0,"hashrate":0,"hashrateString":"0.00 KH"},"sha256":{"workers":1,"hashrate":400863614,"hashrateString":"382.29 MH"}},"pools":{"Casinocoin":{"name":"Casinocoin","symbol":"CSC","algorithm":"scrypt","poolStats":{"validShares":"115"},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"Eoncoin":{"name":"Eoncoin","symbol":"EON","algorithm":"scrypt","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"ExeCoin":{"name":"ExeCoin","symbol":"EXE","algorithm":"scrypt-n","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"GhostCoin":{"name":"GhostCoin","symbol":"GHC","algorithm":"scrypt","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"Hirocoin":{"name":"Hirocoin","symbol":"HIC","algorithm":"x11","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"Limecoin":{"name":"Limecoin","symbol":"LIM","algorithm":"x11","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"Muniti":{"name":"Muniti","symbol":"MUN","algorithm":"x11","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"NyanCoin":{"name":"NyanCoin","symbol":"NYC","algorithm":"scrypt","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"Octocoin":{"name":"Octocoin","symbol":"888","algorithm":"scrypt","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"Reddcoin":{"name":"Reddcoin","symbol":"REDD","algorithm":"scrypt","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"SpeedCoin":{"name":"SpeedCoin","symbol":"SPC","algorithm":"sha256","poolStats":{"validShares":"2622","invalidShares":"52"},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{"STtkoQ4rFkDgnA9wKDQFT6M8gfs37rw8JD":60928},"hashrate":400863614,"workerCount":1,"hashrateString":"382.29 MH"},"Whitecoin":{"name":"Whitecoin","symbol":"WC","algorithm":"scrypt","poolStats":{"validShares":0,"validBlocks":0,"invalidShares":0},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"},"CoinoCoin":{"name":"CoinoCoin","symbol":"COC","algorithm":"scrypt","poolStats":{"validShares":"568","invalidShares":"8"},"blocks":{"pending":0,"confirmed":0,"orphaned":0},"workers":{},"hashrate":0,"workerCount":0,"hashrateString":"0.00 KH"}}}"

First off, thank you for sharing your wonderful work! I plan to contribute back as I gain a better understanding of the project. I was wondering, is it possible to have a cluster of NOMPs? What would be the best way to do it? Should they share the same Redis/MySQL or is it better to set everything up as a separate pool?

Please set the right difficuty 0.004 with darkcoin and hirocoin.
redisCommands.push(['hincrby', coin + '_shares:roundCurrent', shareData.worker, shareData.difficulty]);

is error。
Make
redisCommands.push(['hincrbyfloat', coin + '_shares:roundCurrent', shareData.worker, shareData.difficulty]);

And still have other bug like stat

Ok so not sure what's going on here, bit i am having a major hard time running a blockerrupter cube on my pool here.

i have the cube pointed at a bfgminer proxy running on port 8332 thats redirected to the pool.

bfgminer seems to be accepting lots of shares from the pool, but when i look at my blockerrupter, its not actually doing anything ? of 471 jobs it accepted 2 and rejected 442 ? and none of the chips are working on anything ?

i switch over to a commercial pool such as bfgguild and it runs fine no problem.

i switch over to solo mining directly on the same box, using bfgminer connected directly to bitcoind and the block errupter cube fills up...

let me kmow what i can do to help debug here ?

1. Please add a line to the config.json that will enable or disable the deleting of the previous completed rounds histories in redis (in the _rounds keys. Personally I just have commented out those lines, but for compatibility it would be nice to be able to have a easy way to stop it from doing that.

Add an IRC Bot Module and integrate with statistics

Hi
Can I add pool on the fly?

When I need to add coin, the codes seems like whole stratum node needs to be restarted.
Affecting all other coins looks like problem to real productions.

Anyway.. what a awesome works!!! Really Great!!!

Hello, I'm loving the application so far here's mine (work in progress): http://blackcoinminer.com:8080/ ... however I'm a bit lost of the purpose of the block notify script? What purpose does it serve? I'm a node developer but still trying to wrap my head around this application :-)

Thanks!

for some reason I am getting a negative hash rate in my stats ?

npm ERR! Error: failed to fetch from registry: stratum-pool/0.1.5
npm ERR! at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
npm ERR! at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
npm ERR! at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18)
npm ERR! at Request.callback (/usr/lib/nodejs/request/main.js:119:22)
npm ERR! at Request. (/usr/lib/nodejs/request/main.js:212:58)
npm ERR! at Request.emit (events.js:88:20)
npm ERR! at ClientRequest. (/usr/lib/nodejs/request/main.js:412:12)
npm ERR! at ClientRequest.emit (events.js:67:17)
npm ERR! at HTTPParser.onIncoming (http.js:1261:11)
npm ERR! at HTTPParser.onHeadersComplete (http.js:102:31)
npm ERR! You may report this log at:
npm ERR! http://bugs.debian.org/npm
npm ERR! or use
npm ERR! reportbug --attach /var/www/nomp/npm-debug.log npm
npm ERR!
npm ERR! System Linux 3.11.0-18-generic
npm ERR! command "node" "/usr/bin/npm" "update"
npm ERR! cwd /var/www/nomp
npm ERR! node -v v0.6.12
npm ERR! npm -v 1.1.4
npm ERR! message failed to fetch from registry: stratum-pool/0.1.5
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /var/www/nomp/npm-debug.log
npm not ok

1)Also please modify it so that when it is writing the values to to the blocksPending table include :: - this will make generating good pool statistics possible.

2. And lastly - can the new stats object please also start recording users invalid shares submitted please? Also essential for stats that are on par with MPOS.

Is it Possible For Users To Hav The Coins They Mined Printed Somewhere On The Screen???

As discussed in another issue, When coin switching is enabled using the proxy ports, The coins switch properly however, once a miner switches to the correct pool they no longer send any shares.

I keep getting the following error, and then the fork crashes... not i am setting up a private (internal only) bitcoin mining pool to manage all my mining gear!)

(Fork 0) Client 'xxxxxxxxxxxxxxxxxxxxxx' has sent us an unknown stratum method: mining.get_transaction

then crashes with

/home/osaware/nomp/node_modules/stratum-pool/lib/algoProperties.js:12
return util.doublesha.apply(this, arguments);
^
ReferenceError: util is not defined
at global.algos.sha256.hash (/home/osaware/nomp/node_modules/stratum-pool/lib/algoProperties.js:12:20)
at JobManager.processShare (/home/osaware/nomp/node_modules/stratum-pool/lib/jobManager.js:176:28)
at null. (/home/osaware/nomp/node_modules/stratum-pool/lib/pool.js:554:46)
at EventEmitter.emit (events.js:98:17)
at handleSubmit (/home/osaware/nomp/node_modules/stratum-pool/lib/stratum.js:156:15)
at handleMessage (/home/osaware/nomp/node_modules/stratum-pool/lib/stratum.js:68:17)
at /home/osaware/nomp/node_modules/stratum-pool/lib/stratum.js:211:25
at Array.forEach (native)
at Socket. (/home/osaware/nomp/node_modules/stratum-pool/lib/stratum.js:198:26)
at Socket.EventEmitter.emit (events.js:95:17)

I found this thread online... it may help ? unless i am doing something wrong in my configs...

luke-jr/bfgminer#225

i think we need add https support for nomp !

hey, whenever my blocknotify.js runs I get this coming up on the console:

events.js:72
throw er; // Unhandled 'error' event
^
Error: getaddrinfo ENOTFOUND
at errnoException (dns.js:37:11)
at Object.onanswer as oncomplete

here is npm update output..

[email protected] node_modules/request/node_modules/hawk
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]
npm http GET https://registry.npmjs.org/base58-native
npm http 304 https://registry.npmjs.org/base58-native
npm http GET https://registry.npmjs.org/bindings
[email protected] node_modules/mysql/node_modules/bignumber.js
npm http 304 https://registry.npmjs.org/bindings

[email protected] install /root/node-open-mining-portal-master/node_modules/stratum-pool/node_modules/multi-hashing
node-gyp rebuild

Traceback (most recent call last):
File "/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 18, in
sys.exit(gyp.script_main())
AttributeError: 'module' object has no attribute 'script_main'
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:337:16)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.11.0-19-generic
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/node-open-mining-portal-master/node_modules/stratum-pool/node_modules/multi-hashing
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the multi-hashing package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls multi-hashing
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.11.0-19-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "update"
npm ERR! cwd /root/node-open-mining-portal-master
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/node-open-mining-portal-master/npm-debug.log
npm ERR! not ok code 0

http://pastebin.com/C1UnbFH7 http://i.imgur.com/EwAE8Hw.png

2014-04-10 15:48:03 [Payments] [Jennycoin] Payments stopped because of the critical error - failed commands saved in Jennycoin_finalRedisCommands redis set:
[["smove","Jennycoin_blocksPending","Jennycoin_blocksConfirmed","9d1b6944db0d82523f88d517cf3a2dfe3ed0dc73dcdfca603e34ac06a67ea505:5541bbc951cc88a24ec96aff3174dacce17f054e7104995557f8c03431afd3c4:6709:86753090000"],["hincrbyfloat","Jennycoin_payouts","JcPRZScB5Hx16t7ZkoU5EggFLFZWjVJMa4","867.53090000"],["del","Jennycoin_shares:round6709"],["hincrbyfloat","Jennycoin_stats","totalPaid","867.53090000"],["del","Jennycoin_finalRedisCommands"],["bgsave"]]

There is some problems with NOMP when there is a coin with x11 algorythm..
Everything is good, before I start the client - there are no shares accepted on the client and on the stratum side.
With scrypt - everything's good!

Yesterday I tested node-stratum-portal on production (abour 3ghs scrypt).
and after one hour all processes take more tan 1GB in RSS memory.
Something is not cleaning properly :/

copied from:
slush0/stratum-mining-proxy#66

1. Create a mining proxy on ubuntu
   https://github.com/slush0/stratum-mining-proxy
2. Change difficulty on mine/mining_libs/client_service.py , edit like;
   elif method == 'mining.set_difficulty':
   difficulty = 0.0001
3. Start proxy, connect any cpu miner.

It also works on this pool software in combination with x11(darkcoin, limecoin, h5c)

hey, I am seeing tons (hundreds, like over 1000) of these connections between my local host and my coin daemons:
tcp 0 0 127.0.0.1:60131 127.0.0.1:7950 TIME_WAIT -
tcp 0 0 127.0.0.1:58612 127.0.0.1:7950 TIME_WAIT -
tcp 0 0 127.0.0.1:41226 127.0.0.1:9327 TIME_WAIT -
tcp 0 0 127.0.0.1:40559 127.0.0.1:9327 TIME_WAIT -
tcp 0 0 127.0.0.1:59283 127.0.0.1:7950 TIME_WAIT -
tcp 0 0 127.0.0.1:60095 127.0.0.1:7950 TIME_WAIT -
tcp 0 0 127.0.0.1:41034 127.0.0.1:9327 TIME_WAIT -
tcp 0 0 127.0.0.1:59012 127.0.0.1:7950 TIME_WAIT -
tcp 0 0 127.0.0.1:57760 127.0.0.1:9337 TIME_WAIT -
tcp 0 0 127.0.0.1:39601 127.0.0.1:9327 TIME_WAIT -
tcp 0 0 127.0.0.1:39621 127.0.0.1:9327 TIME_WAIT -
tcp 0 0 127.0.0.1:58534 127.0.0.1:7950 TIME_WAIT -

Any idea why the pool must be doing this? it happens for all the coin daemons I am running...