sudo node inito.js ERROR running Dashcoin

[hiroshi2701]

Hi guys,

Can you guys help me please? I'm having a problem when I starting my mining pool for dashcoin. Here's the error I'm getting:

[2016-09-20 11:27:48.124] [DEBUG] [default] - Pool dash Thread 2 Share processing setup with redis (127.0.0.1:6379) [2016-09-20 11:27:57.046] [DEBUG] [default] - Master CLI CLI listening on port 17117 [2016-09-20 11:27:57.645] [INFO] [default] - New Relic [2016-09-20 11:27:57.649] [INFO] [default] - POSIX Not Installed [2016-09-20 11:27:57.649] [INFO] [default] - Run Workers [2016-09-20 11:27:57.659] [INFO] [default] - New Relic [2016-09-20 11:27:57.662] [INFO] [default] - POSIX Not Installed [2016-09-20 11:27:57.662] [INFO] [default] - Run Workers

[2016-09-20 11:27:57.677] [ERROR] [default] - Payments dash Error with payment processing daemon {"type":"offline","message":"connect ECONNREFUSED"} [2016-09-20 11:27:57.713] [DEBUG] [default] - Website Server Website started on 45.32.51.56:80 [2016-09-20 11:27:57.780] [ERROR] [default] - Website dash Could not dumpprivkey for dash {"type":"offline","message":"connect ECONNREFUSED"}

Any help will be appreciated! Thank you!

Best Regards, Mark Sigway Higgs

[WebWeave]

is your node up?

[oelke]

Is redis ok? and this is NOMP ou uNOMP?

[hiroshi2701]

Hi guys,

I'm so sorry for the late reply and thank you for your response. This is on uNOMP.

I'm very newbie on this. What do you mean by node up? and redis? my website mining pool is running perfectly fine. But when I started miner to mine, I didn't get any blocks being reported found/pending/orphand. Maybe there is something wrong with my dash.json maybe?

{ "enabled": true, "coin": "dash.json",

"auxes": [], "address": "[dash wallet address where]",

"rewardRecipients": { "n37vuNFkXfk15uFnGoVyHZ6PYQxppD3QqK": 1.5, "22851477d63a085dbc2398c8430af1c09e7343f6": 0.1 },

"paymentProcessing": { "enabled": true, "paymentInterval": 30, "minimumPayment": 0.01, "daemon": { "host": "127.0.0.1", "port": 9998, "user": "username", "password": "password" } },

"ports": { "3008": { "diff": 8 }, "3032": { "diff": 32, "varDiff": { "minDiff": 8, "maxDiff": 512, "targetTime": 15, "retargetTime": 90, "variancePercent": 30 } }, "3256": { "diff": 256 } },

"daemons": [ { "host": "127.0.0.1", "port": 9998, "user": "username", "password": "password" } ],

"p2p": { "enabled": false, "host": "127.0.0.1", "port": 9999, "disableTransactions": false },

"mposMode": { "enabled": false, "host": "127.0.0.1", "port": 3306, "user": "me", "password": "mypass", "database": "ltc", "checkPassword": false, "autoCreateWorker": false }

}

or could be something else? Thanks guys! I really appreciate the help. You guys are awesome!

[oelke]

For Dashcoin mining you will need some badass hashrate to find a block (10+Gh), difficulty is VERY high already on the network. Do you see shares being accepted with this setup?

[hiroshi2701]

Got that oelke. Yes. so far the mining pool has 1303 valid shares but no pending/confirmed/orphaned

so if miners don't get blocks, there will be no coins will be paid to the miners. Is that correct? BLOCK = COINS

And also I'm confused about the DASH WALLET Address, do I need to put the DASH WALLET Address to dash.json??

Thanks so much!!

[hiroshi2701]

now I redirected all my miners to the pool running at 4.5GH

Here's my unomp/coins/dash.json: { "name": "Dash", "symbol": "DASH", "algorithm": "x11", "mposDiffMultiplier": 256 }

Here's my dash.conf: rpcuser=username rpcpassword=password alertnotify=echo %s | mail -s "Dash Alert" mark.gallego@gmail.com rpcport=9998 server=1 daemon=1

Stratum ports and diff:

should my miner need to connect to Port: 3256, Diff: 256??

[oelke]

With that hashrate, try diff 16384, with dash I personally would not use anything less than 1024. And yes, you only get $$ finding a block and it don't get orphaned.

On the pool config file, the line: "address": "[dash wallet address where]", is where you put the address of the wallet that will receive the Reward when a block is found.

These Lines: "rewardRecipients": { "n37vuNFkXfk15uFnGoVyHZ6PYQxppD3QqK": 1.5, "22851477d63a085dbc2398c8430af1c09e7343f6": 0.1 }, Are used to collect fees and such.

[hiroshi2701]

On the dash.json, should I change "3256": { "diff": 256 } },

to

"3256": { "diff": 16384 } },

for example, I owned the mining pool, can I just remove the addresses on "rewardRecipients", oelke?

Thank you so much! Mark

[oelke]

I really don't know what would happen if you remove it totally.But try this: "rewardRecipients": { "Same Address of the field "address" ": 1 },

This way the fee goes into the same wallet, and you avoid breaking things up.

And according the first post, the payment processor isn't working there: [2016-09-20 11:27:57.677] [ERROR] [default] - Payments dash Error with payment processing daemon {"type":"offline","message":"connect ECONNREFUSED"}

on NOMP this is regarded REDIS not being available. That is ok If you don't want anyone else mining at your pool, but if someone does, they will never get paid.

[hiroshi2701]

Thanks so much! Got that Oelke.

But I want tell you this first. On the "Address", what I put here before is the address I got when I first set up the DASHCOIN WALLET using ./dashcoin-cli getnewaddress when I first setup my unomp mining pool.

on the other hand, Is this fine Oelke? dash.json:

You the man!

[oelke]

Yeap that is fine and way more suitable to your mining speed. Don't forget to check on some of the miners if they actually are at that diff.

[oelke]

Gave UP?

[hiroshi2701]

Never Oelke! :) I'm having a problem with my miners. When I redirected and switched my miners to port "3256", diff "16384, it went 0Khz.

And also, how do I check if the miners are at that diff, Oelke? Thanks for your help. You the man Oelke!!!

[oelke]

Double check your firewall, trouble is probably there (if the script had no trouble using that port). I dunno which miner do you got, but on the status screen on them, that will be displayd.

[hiroshi2701]

okay Oelke. So the higher the hash rate, the higher the diff? Is that correct?

for hash rate 600mz (1 miner), what would be the appropriate diff?

All is running perfectly fine on the stratum server. The only thing I noticed is the "no new block"

and the POSIX not installed

here's the mining pool http://45.32.51.56/

I really appreciate your help Oelke. Your the man!

[oelke]

Try enabling P2P: Add into: unomp/coins/dash.json: { "name": "Dash", "symbol": "DASH", "algorithm": "x11", "mposDiffMultiplier": 256, "peerMagic": "bf0c6bbd" }

And enable it on the pool config file:

"p2p": { "enabled": true, "host": "127.0.0.1", "port": 9999, "disableTransactions": true },

for some reason it's (may) not being detected through RPC.

And yes again, bigger the hashrate bigger the diff, for 600mh/s try 8192.

[oelke]

still trying?

[wuhuaping]

/nomp# node init.js /var/www/html/nomp/node_modules/stratum-pool/node_modules/multi-hashing/node_modules/bindings/bindings.js:83 throw e ^

Error: Module did not self-register. at Error (native) at Object.Module._extensions..node (module.js:568:18) at Module.load (module.js:458:32) at tryModuleLoad (module.js:417:12) at Function.Module._load (module.js:409:3) at Module.require (module.js:468:17) at require (internal/module.js:20:19) at bindings (/var/www/html/nomp/node_modules/stratum-pool/node_modules/multi-hashing/node_modules/bindings/bindings.js:76:44) at Object. (/var/www/html/nomp/node_modules/stratum-pool/node_modules/multi-hashing/index.js:1:99) at Module._compile (module.js:541:32) Who can tell me how to solve it, thank you angel77758@163.com

[oelke]

Did npm update finished without error?

[wuhuaping]

"peerMagic": "bf0c6bbd" Where can I find it

[wuhuaping]

达世币钱包的

[oelke]

You need to insert it into file: coins/darkcoin.json (or wherever filename you are using, I'm using dash.json): { "name": "DASH", "symbol": "DASH", "algorithm": "x11", "mposDiffMultiplier": 256, "peerMagic": "bf0c6bbd" }

[wuhuaping]

Thank you for your answer. I started it but dug dash did not dig a block The address is correct. Is not the problem of algorithm ah I've been digging all night. 1G

[wuhuaping]

Start without any erro

[oelke]

mining with how much hashrate?

[wuhuaping]

| Pool | Algo | Workers | Valid Shares | Invalid Shares | Total Blocks | Pending | Confirmed | Orphaned | Hashrate | | dash | x11 | 0 | 2968 | 3 | 0 | 0 | 0 | 0 | 0.00 KH |

At 2017-01-05 00:01:15, "oelke" notifications@github.com wrote:

mining with how much hashrate?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[oelke]

big 0 there, try lowering the difficulty on pool config file.

[wuhuaping]

"ports": { "5555": { "diff": 0.08 }, "6666": { "diff": 0.08, "varDiff": { "minDiff": 0.01, "maxDiff": 0.1, "targetTime": 15, "retargetTime": 90, "variancePercent": 30 } }, "8888": { "diff": 0.08 I set this but is not even if I can not find the block is heightening useless I don't know where I was wrong. Thank you for answering

At 2017-01-06 05:58:52, "oelke" notifications@github.com wrote:

big 0 there, try lowering the difficulty on pool config file.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[oelke]

that diff for DASH is kinda low, but it should appear at the hashrate field. what miner are u using?

[wuhuaping]

I use the wallet address
I use him to dig fedoracoin algorithm is scypt can be dug into the block but DASH can not dig a block

At 2017-01-06 09:28:29, "oelke" notifications@github.com wrote:

that diff for DASH is kinda low, but it should appear at the hashrate field. what miner are u using?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.