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

3rd Party Applications
43

getting this weird error. Maybe I need to be running two instances of zcashd? One for accepting blocks and the other for processing payments?

znomp payment issue.PNG1607×164 15 KB

44

No, you shouldn’t have to run separate network nodes just to process payments, although I haven’t looked at it at all. You can get on rocketchat and ask one of the pool ops or devs.

45

ok. asking on the zclassic slack now. I’m also going to see what NOMP FAQ’s has to say about it.

46

woo, I’m slow today! I finally did this part and it worked. I put it in the zclassic.json config instead though, because at some point I am going to use this pool server for mining more than zclassic

1 Like
47

So, I am really liking this mining pool way of going about things. Ran it for a few days and found some blocks. Tried to upgrade code and broke it. Nothing. Now it’s working again.

Learned a lot in the last week, feel like I am catching up to everyone else. The more I look at zcash the more I am impressed by how much better it is than anything else out there. I like the zclassic community also.

1 Like
48

I wish I could understand. But I don’t, anyhow when you guys build your pools can you see how close you are getting to solving a block? Like Bitcoin you can see your best share?

49

Not that I’m aware of. In fact, I haven’t seen either an ETH or ZEC/ZCL pool that reports that number. To be honest though, what difference does it make? You either solve it or you don’t, it’s not like horseshoes. :slight_smile:

50

As far as I can tell it’s entirely random. Last night I found 5 blocks. All day today nothing. I need to set monitoring up so I can check and make sure things are running properly without checking the found blocks…because when I find nothing for a while I start to worry.

51

There are Bitcoin pools that show that stat. As well as the miner software ( cgminer in particular cause that’s what was running the miner I had). To each there own it’s just something I want to see.

52

That’s because it is (pseudo) random. Mining is nothing but probability and variance (aka “luck”). With Zcash, you have a 150 second average block time. Now, look at the network hash rate. On average, it takes 150 times the network hash rate to find a block. You’ll notice, however, that the inter-block times are all over the place, from a couple seconds to many, many minutes. In that context, consider your own hash rate. It all makes hitting the Power Ball lottery look easy, except we miners get a lot more tickets.

53

ok, just found another block. Everything is working :grin:

I know what can increase the odds, though, more power! Just placed a parts order for 6 more 6-GPU rigs.

54

If it makes you feel any better, I have 54K sols/s. In a day I’ve had a low of 8 blocks and a high of 34, over the last 4 weeks. :slight_smile: As far as more rigs go, all I can say is: remember everything could change tomorrow.

55

yes, I agree with that. Only playing with money I can afford to lose.

It’s why I am also mining Bitcoin, X11 for Dash, Scrypt for Gulden and litecoin.

I had written off Ethereum as very overpriced. Nice price action, though. I might have to look back into it.

56

My Nanos are so efficient with the Equihash algo, it doesn’t make any sense for me to go back to ETH, which I mined exclusively for almost a year.

1 Like
57

I’ve been running Z-NOMP for solo mining. I’ve seen a number of cases where the private pool is submitting the same solution to the node for a block from 2 different miners. So, this is probably happening at the share level, as well. Anyone else notice this? It happens almost every day, and sometimes twice. I only see it at the block level, since the share data is meaningless to me, but if it’s happening at the block level, it may be happening much more frequently at the share level.

58

Perhaps I can be helped here, I have the server going redis crashes every like 20 minutes and I also cannot connect a miner to the server, here is the crash log in redis

2017-02-27 10:18:27 [Pool] [zcash] (Thread 5) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 4) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 1) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 7) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 6) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 2) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 3) Connection to redis database has been ended
2017-02-27 10:18:27 [Pool] [zcash] (Thread 8) Connection to redis database has been ended
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
2017-02-27 10:18:28 [Pool] [zcash] (Thread 7) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
2017-02-27 10:18:28 [Pool] [zcash] (Thread 5) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
2017-02-27 10:18:28 [Pool] [zcash] (Thread 4) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
2017-02-27 10:18:28 [Pool] [zcash] (Thread 1) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
2017-02-27 10:18:28 [Pool] [zcash] (Thread 6) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
2017-02-27 10:18:28 [Pool] [zcash] (Thread 2) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
2017-02-27 10:18:28 [Pool] [zcash] (Thread 3) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
2017-02-27 10:18:28 [Pool] [zcash] (Thread 8) Redis client had an error: {“code”:“ECONNREFUSED”,“errno”:“ECONNREFUSED”,“syscall”:“connect”,“address”:“127.0.0.1”,“port”:6379}
events.js:161
throw er; // Unhandled ‘error’ event
^

Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
at Object.exports._errnoException (util.js:1028:11)
at exports._exceptionWithHostPort (util.js:1051:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
2017-02-27 10:18:28 [Master] [Website] Website process died, spawning replacement…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 4 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 3 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 0 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 6 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 5 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 2 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 1 died, spawning replacement worker…
2017-02-27 10:18:28 [Master] [PoolSpawner] Fork 7 died, spawning replacement worker…
2017-02-27 10:18:30 [Website] [Server] Website started on 0.0.0.0:8080
2017-02-27 10:18:30 [Switching] [Setup] (Thread 5) Loading last proxy state from redis

59

do yo know ho to fix this ?

/home/pool/z-nomp/node_modules/bs58check/index.js:48 if (!payload) throw new Error(‘Invalid checksum’) ^

thanks

60

incredibly late response, but duplicate shares happen all the time since nonce ranges are limited. Duplicate blocks do happen but rarely

61

Can you share what your daemon node version is as well your nodejs version?

62

zcashd 1.0.8
nodejs-6.10.1-2.el7.x86_64

i also tried Centos 7 (Ubuntu before) and the same error. This si some stupid error in config i think

thanks for ideas