Z-NOMP(Node Open Mining Portal) (READY FOR TESTING)

What were your readings on the lines before this line? I had the same and fixed it. But I can’t remember what it was. Post the other lines.

1 Like

2017-01-07 14:06:20 [POSIX] [Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2017-01-07 14:06:20 [Master] [CLI] CLI listening on port 17117
2017-01-07 14:06:21 [Master] [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
2017-01-07 14:06:23 [Website] [Server] Website started on 0.0.0.0:8080
2017-01-07 14:06:23 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2017-01-07 14:06:23 [Pool] [zcash] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
2017-01-07 14:06:23 [Payments] [zcash] Payment processing setup to run every 20 second(s) with daemon (zclassicrpc@127.0.0.1:19332) and redis (127.0.0.1:6379)
2017-01-07 14:06:24 [Payments] [zcash] Finished interval - time spent: 87ms total, 2ms redis, 82ms daemon RPC
/home/pool/z-nomp/node_modules/bs58check/index.js:48
if (!payload) throw new Error(‘Invalid checksum’)
^

Error: Invalid checksum
at Object.decode (/home/pool/z-nomp/node_modules/bs58check/index.js:48:23)
at Object.fromBase58Check (/home/pool/z-nomp/node_modules/bitcoinjs-lib-zcash/src/address.js:8:27)
at Object.exports.createGeneration (/home/pool/z-nomp/node_modules/stratum-pool/lib/transactions.js:83:46)
at new BlockTemplate (/home/pool/z-nomp/node_modules/stratum-pool/lib/blockTemplate.js:35:35)
at JobManager.processTemplate (/home/pool/z-nomp/node_modules/stratum-pool/lib/jobManager.js:123:32)
at /home/pool/z-nomp/node_modules/stratum-pool/lib/pool.js:578:66
at itemFinished (/home/pool/z-nomp/node_modules/stratum-pool/lib/daemon.js:155:36)
at /home/pool/z-nomp/node_modules/stratum-pool/lib/daemon.js:169:17
at parseJson (/home/pool/z-nomp/node_modules/stratum-pool/lib/daemon.js:85:17)
at IncomingMessage. (/home/pool/z-nomp/node_modules/stratum-pool/lib/daemon.js:95:17)

running zcash or zclassic? looks like rpc port & password error. need to set the rpc port, user & password the same in the 3 places. 1 in the ./daemon file, 2 in the pool_configs → coin.json file for daemon and daemons.

using the zclassic daemon with zcash?

I am using zcash thanks for the help

Tested on Ubuntu 16.04.1 LTS & Ubuntu 14.04.5 LTS
Zcash Daemon version v1.0.4-06ffa21
NodeJs v7.4.0
Running ZCASH

Zcash daemon on port 8232 started and open
Redis on port 6379 started and open
Z-Nomp Website on port 8888 started and open
Z-Nomp CLI on port 17117 started and open
Z-Nomp Master on port 3032 NOT started

I’m cheched RPC port (8232), rpc user and rpc passwords! (in the daemon and pool_configs/zcash.json files).

korn@Z:/z/z-nomp$ npm start

> z-nomp@0.0.4 start /z/z-nomp
> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PWD/node_modules/stratum-pool/node_modules/equihashverify/build/Release/:$PWD/node_modules/equihashverify/build/Release/ node init.js

2017-01-10 05:02:25 [POSIX]     [Connection Limit] (Safe to ignore) POSIX module not installed and resource (connection) limit was not raised
2017-01-10 05:02:25 [Master]    [CLI] CLI listening on port 17117
2017-01-10 05:02:25 [Master]    [PoolSpawner] Spawned 1 pool(s) on 1 thread(s)
2017-01-10 05:02:27 [Website]   [Server] Website started on 0.0.0.0:8888
2017-01-10 05:02:27 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2017-01-10 05:02:27 [Pool]      [zcash] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
/z/z-nomp/node_modules/bs58check/index.js:48
  if (!payload) throw new Error('Invalid checksum')
                ^

Error: Invalid checksum
    at Object.decode (/z/z-nomp/node_modules/bs58check/index.js:48:23)
    at Object.fromBase58Check (/z/z-nomp/node_modules/bitcoinjs-lib-zcash/src/address.js:8:27)
    at Object.exports.createGeneration (/z/z-nomp/node_modules/stratum-pool/lib/transactions.js:83:46)
    at new BlockTemplate (/z/z-nomp/node_modules/stratum-pool/lib/blockTemplate.js:35:35)
    at JobManager.processTemplate (/z/z-nomp/node_modules/stratum-pool/lib/jobManager.js:123:32)
    at /z/z-nomp/node_modules/stratum-pool/lib/pool.js:578:66
    at itemFinished (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:155:36)
    at /z/z-nomp/node_modules/stratum-pool/lib/daemon.js:169:17
    at parseJson (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:85:17)
    at IncomingMessage.<anonymous> (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:95:17)
2017-01-10 05:02:28 [Master]    [PoolSpawner] Fork 0 died, spawning replacement worker...
2017-01-10 05:02:31 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2017-01-10 05:02:31 [Pool]      [zcash] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
/z/z-nomp/node_modules/bs58check/index.js:48
  if (!payload) throw new Error('Invalid checksum')
                ^

Error: Invalid checksum
    at Object.decode (/z/z-nomp/node_modules/bs58check/index.js:48:23)
    at Object.fromBase58Check (/z/z-nomp/node_modules/bitcoinjs-lib-zcash/src/address.js:8:27)
    at Object.exports.createGeneration (/z/z-nomp/node_modules/stratum-pool/lib/transactions.js:83:46)
    at new BlockTemplate (/z/z-nomp/node_modules/stratum-pool/lib/blockTemplate.js:35:35)
    at JobManager.processTemplate (/z/z-nomp/node_modules/stratum-pool/lib/jobManager.js:123:32)
    at /z/z-nomp/node_modules/stratum-pool/lib/pool.js:578:66
    at itemFinished (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:155:36)
    at /z/z-nomp/node_modules/stratum-pool/lib/daemon.js:169:17
    at parseJson (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:85:17)
    at IncomingMessage.<anonymous> (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:95:17)
2017-01-10 05:02:31 [Master]    [PoolSpawner] Fork 0 died, spawning replacement worker...
2017-01-10 05:02:34 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2017-01-10 05:02:34 [Pool]      [zcash] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
/z/z-nomp/node_modules/bs58check/index.js:48
  if (!payload) throw new Error('Invalid checksum')
1 Like

The problem remains the same

Exactly same for me:!!!

Tested on Debian 8 64x
Zcash Daemon version v1.0.4-06ffa21
NodeJs v7.4.0
Running ZCASH

Zcash daemon on port 8232 started and open
Redis on port 6379 started and open
Z-Nomp Website on port 8888 started and open
Z-Nomp CLI on port 17117 started and open
Z-Nomp Master on port 3032 NOT started
Rpc conection succefull:
Same Error:

Error: Invalid checksum
    at Object.decode (/z/z-nomp/node_modules/bs58check/index.js:48:23)
    at Object.fromBase58Check (/z/z-nomp/node_modules/bitcoinjs-lib-zcash/src/address.js:8:27)
    at Object.exports.createGeneration (/z/z-nomp/node_modules/stratum-pool/lib/transactions.js:83:46)
    at new BlockTemplate (/z/z-nomp/node_modules/stratum-pool/lib/blockTemplate.js:35:35)
    at JobManager.processTemplate (/z/z-nomp/node_modules/stratum-pool/lib/jobManager.js:123:32)
    at /z/z-nomp/node_modules/stratum-pool/lib/pool.js:578:66
    at itemFinished (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:155:36)
    at /z/z-nomp/node_modules/stratum-pool/lib/daemon.js:169:17
    at parseJson (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:85:17)
    at IncomingMessage.<anonymous> (/z/z-nomp/node_modules/stratum-pool/lib/daemon.js:95:17)
2017-01-10 05:02:28 [Master]    [PoolSpawner] Fork 0 died, spawning replacement worker...
2017-01-10 05:02:31 [Switching] [Setup] (Thread 1) Loading last proxy state from redis
2017-01-10 05:02:31 [Pool]      [zcash] (Thread 1) Share processing setup with redis (127.0.0.1:6379)
/z/z-nomp/node_modules/bs58check/index.js:48
  if (!payload) throw new Error('Invalid checksum')

I installed Z-NOMP a couple of days ago, and it’s working great! I’m using it for solo mining; I turned off just about every pool feature I could in the config files. I highly recommend using the “blocknotify” option to eliminate the polling overhead checking for new blocks. If you do, remember to set “blockRefreshInterval=0” in config.json, otherwise you will continue to issue rpc poll calls to the node, checking for new blocks, even though the blocknotify function is also getting the new block (and much faster, too).

question for you - I installed the pool and got it working. But only 5 workers can connect. When I try to connect the sixth worker it won’t connect.

Any recommendations?

tried the 6th worker with a different t address. worked then. Maybe a 5 worker limit using a single address?

Nope, my whole farm is on one address. I have over a hundred connections and 23 worker names.

yeah, figured it out. I was not initially adding worker names appended to the t address. after I did that, everything started working great.

If you are running your GPU’s under separate processes, then you may want to make sure the 6th GPU in your rig connects if it is using the same name as the other 5 GPU’s.

Now I just need to figure out how to pipe the 8080 website into something frontended by apache or nginx with an SSL certificate. And how to set up to accept stratum tls connections.

Further, I am going to see if the Z-NOMP build works for other coins than just zcash and zclassic

Well, NOMP is what Z-NOMP is based on, and it works for lots of coins. Since I’m solo, I turned off payment processing, ip address banning, profit switching, the webserver, an just about anything else I could set “enabled=false” :slight_smile: I’m planning to continue to prune this thing down for solo - so share processing and the stats module are my next targets. For solo, there’s only two things I need to know: are my rigs up and receiving new work, and how many blocks am I finding. Everything else is superfluous :slight_smile:

I’m going to try to get the payment process working. I’ll let it run for a little while and see what happens. I have zclassic for 3 blocks sitting in the wallet, but the pool application won’t send it out. It might be becuase I was mining with the identification of the pool and the payment address…maybe it’s in a loop or something.

also, I tried to do this, but I could not find a place to set this in the config.json file. So I just turned it on with the zcashd and set it to zero in the config.json.

I think it is working that way…but not sure yet.

[Optional, recommended] Setting up blocknotify

In config.json set the port and password for blockNotifyListener

So I guess you’re trying to send your wallet balance to an exchange? I have the payment processor disabled and the payment address NULL. Block rewards just go into my default wallet address. I can always send it manually to an exchange, although I’ll be holding zclassic for a good while, I think :slight_smile:

For blocknotify:

o go to z-nomp/scripts and look at blocknotify.c - it tells you how to compile it (trivial).

o in .zclassic/zclassic.json add:

blocknotify=/home/joe/z-nomp/scripts/blocknotify 127.0.0.1:17117 zclassic %s

o in z-nomp/config.json add:

  "blockNotifyListener": {
    "enabled": true,
    "port": 17117
},

Note: the port number needs to match the port set above in config.json: "cliPort": 17117,

o also in config.json, set: “blockRefreshInterval”: 0,

Otherwise you’ll continue to poll for new blocks, even though blocknotify is active.

HTH

Edit: When blocknotify is working, the log will indicate that. You should also see a drop in CPU utilization for both zcashd and znomp.

1 Like

thanks - I did not think of opening the blocknotify.c file and looking at it for instructions!

I think you meant .zclassic/zclassic.conf above

Sorry, yes zclassic.conf. The z-nomp github instructions have you setting a password, but blocknotify.c does not expect/accept one.

Yes, I do want to send it to an exchange. But I also think I want to run a mining pool for profit. Perhaps I could charge a 0.5% fee so others can use it.

There is something to be said for connecting to a pool that is geographically close to you. I put mine on a VPS in Atlanta, so my servers should be accessing it much faster than pools in other geographies. There might be more people in the southeast US that have that same desire.

But I agree on holding zclassic for awhile. I think that’s the best way to go about it. Find a newer coin that has a strong reason for existence, a good developer team, and make bank early.

I think the next one I am going to try is to set up a Gulden mining pool so I can buy some scrypt miners and point them to it.

By the way - found four used AMD R9 Nano’s on ebay at a good price, and was able to buy three of them so far. Thanks for the advice!

1 Like