Set up your own private stratum pool


#201

Playing with my pool today.Have a 1800 Sos/s rig with Claymore v9 on it. Every time I get a new job, I get a rejected share right before the new job. Then after about 3 min of running I will get a string of rejected & stale shares until I reset the miner. Latency is 16ms to 30ms. Anybody know how to stop this? hold on, there is a update v9.1, may be a fix...

Nope, not a fix. If anything v9.1 made it worse....

Anyone else having this problem?


#202

did you change the port to 19999 ? by default the pool's port is 3357

also check zogpool.org for exact claymore connection string ... i myself am on linux so have never tried it


#203

Anybody know what the zcashd.pid(has the number 1402 in it) is?


#204

oh thanks. by looking at the config file for the pool I thought it listens on 19999. so used that port.
3357 was the right one. But this is what I get when running claymore:
Any way to food claymore's this is a real pool? Also it disconnects often.

Miner detected that you use local pool or local proxy.
This mode is not currently supported and will cause less performance.
ZEC: 12/10/16-08:16:28 - SHARE FOUND - (GPU 0)
Miner detected that you use local pool or local proxy.
This mode is not currently supported and will cause less performance.
ZEC: 12/10/16-08:16:31 - SHARE FOUND - (GPU 1)
Miner detected that you use local pool or local proxy.
This mode is not currently supported and will cause less performance.
ZEC: Stratum - socket send failed 10053, disconnect
ZEC: Stratum - connecting to '192.168.1.65' <192.168.1.65> port 3357
ZEC: Stratum - Connected (192.168.1.65:3357)
ZEC: Authorized
Pool sets new share target: 0x00800000 (diff: 511H)
ZEC: 12/10/16-08:16:33 - SHARE FOUND - (GPU 1)
Miner detected that you use local pool or local proxy.
This mode is not currently supported and will cause less performance.


#205

what is in your claymore config file? is -allpool set to 1? I have my pool on my local network with settings in firewall that allows the miners to it normal as if it was off network. claymore does not see it as a local. but I think if you set the allpool to 1 it will see it fine.


#206

-zpool 192.168.1.65:3357
-zwal t1.........................testrig
-zpsw z
-tt 75
-dbg -1
-allpools 1

makes no difference if i set allpools 1 or not. I think it does not like localhost or lan addresses.
What address do you use ? external ip with port forwarding?


#207

set it back to -dbg 0, run it, then see what is in the log file
my miners are behind a firewall, I could not connect to the pool until I did the following. I have setting in it so the miners can mine on it. But I also have a domain name pointing to a static address of the firewall and ports forward. Did you forward the 3357 at your firewall?


#208

My internet is a business account with static IPs. So I can change a lot. Is yours a residential account? Can you do port forward on your modem and your router if it is separate? my miners and pool are on local address.


#209

set your -tt to 60, cards will overheat with the 75.


#210

I normally set it at 69.. 60 seems a bit low (too loud) for non stop mining.


#211

My fans run at 35 to 55 percent on zec, now that it's cooler with the 480s stay at 65 degrees & 38%. My rigs have their own room so noise doesn't bother anyone when they spool up in the summer. Did you figure out your network mining?


#212

Yes, currently testing in virtual box. I change the NIC in vbox to bridge mode, and forwarded ports 80 and 3357 on the router to the 192.168.1.y ip, and then used the external address in claymore to connect. No more errors about local proxy detected. Shares are accepted. But there are no stats shown on the pool page.. and no stats for the miner address connected to it. Looks like rather immature code that needs lot of tweaking to work. I would be willing to contribute to a small crowd funding for someone to make a ready to use pool with this code.
Also the OP's guide could use some info about how to make/get your t/z addressed, I have no idea how to do that. only did pool mining so far.


#213

@megacrypto

do i need to run make or after patch zcash ?
or after
I edit the makefile ?


#214

patch, edit makefile, then run make again to recompile zcashd :slight_smile:

here you go :slight_smile: https://github.com/zcash/zcash/wiki/1.0-User-Guide#using-zcash

and there is a lot of useful info in that wiki!


#215

How to fix??
root@pool-10:~/pool/poolcore/x86_64-Linux# poolrpccmd/poolrpccmd p2p://127.0.0.1:12201 getInfo
Error: connecting error
root@pool-10:~/pool/poolcore/x86_64-Linux# poolrpccmd/poolrpccmd p2p://127.0.0.1:12201 getBlockTemplate
Error: connecting error


#216

it could be many things ... but double check that the pool is running and also the restapi!

from the paths you have, it seems that you have modified the location of things ... did you make sure that all paths are adjusted accordingly?


#217

How to know the Sols/s on pool??


#218

how to fix??
error : get BlockTemplate call failed
error : can't check balance, no connection to wallet

Claymore connect to pool
POOL version
GPU #0 intensity 4
Total cards: 1
ZEC: Stratum - connecting to '172.16.1.176' <172.16.1.176> port 7777 (unsecure)
ZEC: Stratum - Connected (172.16.1.176:7777) (unsecure)
ZEC: Authorized
"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333
Pool sets new share target: 0x00800000 (diff: 511H)

GPU0 t=41C fan=30%
ZEC: Job timeout, disconnect, retry in 20 sec...
GPU0 t=41C fan=30%
ZEC: Stratum - connecting to '172.16.1.176' <172.16.1.176> port 7777 (unsecure)
ZEC: Stratum - Connected (172.16.1.176:7777) (unsecure)
ZEC: Authorized
Pool sets new share target: 0x00800000 (diff: 511H)
GPU0 t=41C fan=30%
ZEC: Job timeout, disconnect, retry in 20 sec...


#219

this will continue to appear until you find your first block, not sure if the same goes for the second line...

as for claymore ... unfortunately i never used it :frowning:


#220

Go though all steps again to verify that you haven't missed anything. Have you config to use port 7777? Also check your blockchain sync. Can you see in log that blocks are being updated?