Pages:
Author

Topic: CKPOOL - Open source pool/proxy/passthrough/redirector/library in c for Linux - page 12. (Read 124144 times)

sr. member
Activity: 419
Merit: 250
Interestingly, it may actually have been working fine. I got similar errors on 64-bit as well. Issue seemed to be hangups with bitcoind. Adding more RAM and setting bitcoind to properly use the notifier seems to made it all work a lot smoother. Still running it on 64-bit.
sr. member
Activity: 419
Merit: 250
Environment is 32-bit ...
Ckpool demands a 64 bit environment and I have no interest in creating support for 32 bits sorry.

Interesting. Thanks for clearing that up.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Environment is 32-bit ...
Ckpool demands a 64 bit environment and I have no interest in creating support for 32 bits sorry.
sr. member
Activity: 419
Merit: 250
Hi ck

I'm getting the same errors over and over. I cloned and built from commit db42a13. Built with all dependencies satisfied. No build problems that I can remember. Running from build directory, not installed. Environment is 32-bit Arch Linux Arm running on a Raspberry Pi2. I haven't yet taken a dive into the lines of code specified here. Was hoping maybe this is something you've encountered before with an easy fix. Any help/pointers would be much appreciated.

Looks to me like stratifier and generator are not starting. I checked and all the sockets and such are getting successfully created in /tmp/ckpool. bitcoind is slow in responding sometimes on this box. Not sure if that could cause this issue.

command line:

Code:
./ckpool -k -A -c ../ckproxy2.conf

ckproxy2.conf:

Code:
{
"btcd" :  [
        {
                "url" : "localhost:8332",
                "auth" : "[user]",
                "pass" : "[pass]"
        }
],
"update_interval" : 30,
"serverurl" : [
        "127.0.0.1:3334"
        ],
"mindiff" : 1,
"startdiff" : 1000,
"maxdiff" : 0,
"logdir" : "logs",
"btcaddress" : "[address]",
"btcsig" : "[sig]"
}

console output:

Code:
[2016-02-14 07:35:22.481] ckpool stratifier starting
[2016-02-14 07:35:22.481] ckpool generator starting
[2016-02-14 07:35:22.482] ckpool connector starting
[2016-02-14 07:35:22.483] ckpool connector ready
[2016-02-14 07:35:27.484] Select1 failed in recv_unix_msg (2) with errno 2: No such file or directory
[2016-02-14 07:35:27.485] Failure in recv_unix_msg from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:27.485] Failure in send_recv_proc from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:32.487] Select1 failed in recv_unix_msg (2) with errno 2: No such file or directory
[2016-02-14 07:35:32.488] Failure in recv_unix_msg from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:32.488] Failure in send_recv_proc from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:37.490] Select1 failed in recv_unix_msg (2) with errno 2: No such file or directory

log output:

Code:
[2016-02-14 07:35:22.475] Setting maxclients to 921 due to max open file limit of 1024
[2016-02-14 07:35:22.481] ckpool stratifier starting
[2016-02-14 07:35:22.475] Setting maxclients to 921 due to max open file limit of 1024
[2016-02-14 07:35:22.481] ckpool generator starting
[2016-02-14 07:35:22.482] ckpool connector starting
[2016-02-14 07:35:22.483] ckpool connector ready
[2016-02-14 07:35:27.484] Select1 failed in recv_unix_msg (2) with errno 2: No such file or directory
[2016-02-14 07:35:27.485] Failure in recv_unix_msg from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:27.485] Failure in send_recv_proc from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:32.487] Select1 failed in recv_unix_msg (2) with errno 2: No such file or directory
[2016-02-14 07:35:32.488] Failure in recv_unix_msg from stratifier.c stratifier:7546 with errno 2: No such file or directory
[2016-02-14 07:35:32.488] Failure in send_recv_proc from stratifier.c stratifier:7546 with errno 2: No such file or directory
hero member
Activity: 672
Merit: 500
yes looks like only MRR doing this, tried stratum.f2pool.com and it is fine too
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
yes, latest git version.
i point proxy to sha256.eu.nicehash.com and there is no such disconnects.
but my miners are pointed to eu-01.miningrigrentals.com directly and they are doing fine.

btw is it possible to switch pools in the proxy list on the fly while miners are connected and working?
Not at the moment, no. I suspect it's just some incompatibility with MRR but I can't guess what it might be sorry. Earlier on I had tested with MRR and saw they *always* disconnect idle miners, and additionally they use redirects with reconnects for changes in where the rentals are pointed.
hero member
Activity: 672
Merit: 500
yes, latest git version.
i point proxy to sha256.eu.nicehash.com and there is no such disconnects.
but my miners are pointed to eu-01.miningrigrentals.com directly and they are doing fine.

btw is it possible to switch pools in the proxy list on the fly while miners are connected and working?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
hero member
Activity: 672
Merit: 500
Code:
[2016-02-14 03:46:32.283] Setting maxclients to 921 due to max open file limit of 1024
[2016-02-14 03:46:32.284] ckproxy stratifier starting
[2016-02-14 03:46:32.283] ckproxy connector starting
[2016-02-14 03:46:32.283] ckproxy connector ready
[2016-02-14 03:46:32.284] ckproxy generator starting
[2016-02-14 03:46:32.284] ckproxy stratifier ready
[2016-02-14 03:46:32.283] File /tmp/ckproxy/generator.pid exists
[2016-02-14 03:46:32.283] File /tmp/ckproxy/stratifier.pid exists
[2016-02-14 03:46:32.283] File /tmp/ckproxy/connector.pid exists
[2016-02-14 03:46:32.507] Found notify for new proxy 0:0 with enonce f800002e nonce2len 4
[2016-02-14 03:46:32.507] Got updated subscribe for proxy 0
[2016-02-14 03:46:32.507] Stratifier added new proxy 0
[2016-02-14 03:46:32.507] Upstream pool stratum+tcp://eu-01.miningrigrentals.com:3333 0 extranonce2 length 4, max proxy clients 256
[2016-02-14 03:46:32.657] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 connection established
[2016-02-14 03:46:32.712] Proxy 0:0 stratum+tcp://eu-01.miningrigrentals.com:3333 failed to epoll/read_socket_line in proxy_recv
[2016-02-14 03:46:32.712] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:46:32.923] Found notify for new proxy 0:0 with enonce f800002e nonce2len 4
[2016-02-14 03:46:32.923] Got updated subscribe for proxy 0
[2016-02-14 03:46:32.923] Upstream pool stratum+tcp://eu-01.miningrigrentals.com:3333 0 extranonce2 length 4, max proxy clients 256
[2016-02-14 03:46:33.285] Pool:{"runtime": 1, "lastupdate": 1455410793, "Users": 0, "Workers": 0, "Idle": 0, "Disconnected": 0}
[2016-02-14 03:46:33.285] Pool:{"hashrate1m": "0", "hashrate5m": "0", "hashrate15m": "0", "hashrate1hr": "0", "hashrate6hr": "0", "hashrate1d": "0", "hashrate7d": "0"}
[2016-02-14 03:46:33.285] Pool:{"SPS1m": 0.0, "SPS5m": 0.0, "SPS15m": 0.0, "SPS1h": 0.0}
[2016-02-14 03:46:33.294] Successfully connected to pool 0 stratum+tcp://eu-01.miningrigrentals.com:3333 as proxy
[2016-02-14 03:46:33.295] ckproxy generator ready
[2016-02-14 03:46:37.712] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:46:37.713] Proxy 0:0 stratum+tcp://eu-01.miningrigrentals.com:3333 failed to epoll/read_socket_line in proxy_recv
[2016-02-14 03:46:37.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:46:37.927] Found notify for new proxy 0:0 with enonce f800002e nonce2len 4
[2016-02-14 03:46:37.927] Got updated subscribe for proxy 0
[2016-02-14 03:46:37.927] Upstream pool stratum+tcp://eu-01.miningrigrentals.com:3333 0 extranonce2 length 4, max proxy clients 256
[2016-02-14 03:46:42.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:46:42.713] Proxy 0:0 stratum+tcp://eu-01.miningrigrentals.com:3333 failed to epoll/read_socket_line in proxy_recv
[2016-02-14 03:46:42.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:46:42.928] Found notify for new proxy 0:0 with enonce f800002e nonce2len 4
[2016-02-14 03:46:42.928] Got updated subscribe for proxy 0
[2016-02-14 03:46:42.928] Upstream pool stratum+tcp://eu-01.miningrigrentals.com:3333 0 extranonce2 length 4, max proxy clients 256
[2016-02-14 03:46:47.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:46:47.713] Proxy 0:0 stratum+tcp://eu-01.miningrigrentals.com:3333 failed to epoll/read_socket_line in proxy_recv
[2016-02-14 03:46:47.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:46:47.922] Found notify for new proxy 0:0 with enonce f800002e nonce2len 4
[2016-02-14 03:46:47.922] Got updated subscribe for proxy 0
[2016-02-14 03:46:47.922] Upstream pool stratum+tcp://eu-01.miningrigrentals.com:3333 0 extranonce2 length 4, max proxy clients 256
[2016-02-14 03:46:52.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:46:52.713] Proxy 0:0 stratum+tcp://eu-01.miningrigrentals.com:3333 failed to epoll/read_socket_line in proxy_recv
[2016-02-14 03:46:52.713] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:46:52.927] Found notify for new proxy 0:0 with enonce f800002e nonce2len 4
[2016-02-14 03:46:52.928] Got updated subscribe for proxy 0
[2016-02-14 03:46:52.928] Upstream pool stratum+tcp://eu-01.miningrigrentals.com:3333 0 extranonce2 length 4, max proxy clients 256
[2016-02-14 03:46:53.645] Parent process ckproxy received signal 2, shutting down
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
hero member
Activity: 672
Merit: 500
credential are valid i copied them from miner's config.


here is level 7 log:
Code:
sudo ./ckpool --proxy -c ckproxy.conf --loglevel 7
[2016-02-14 03:37:57.104] ckproxy connector starting
[2016-02-14 03:37:57.104] ckproxy connector ready
[2016-02-14 03:37:57.105] ckproxy stratifier starting
[2016-02-14 03:37:57.105] ckproxy generator starting
[2016-02-14 03:37:57.105] ckproxy stratifier ready
[2016-02-14 03:37:57.480] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 connection established
[2016-02-14 03:37:57.536] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:37:58.117] Successfully connected to pool 0 stratum+tcp://eu-01.miningrigrentals.com:3333 as proxy
[2016-02-14 03:37:58.117] ckproxy generator ready
[2016-02-14 03:38:02.536] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:02.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:38:07.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:07.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:38:12.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:12.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:38:17.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:17.537] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:38:22.538] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:22.538] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:38:27.538] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:27.539] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 03:38:32.539] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 03:38:32.539] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
true, no miners connected through proxy, but look at a second log it is constant reconnects, no 5 min delays there, it reconnects every 5 seconds
I can't speak for what your upstream pools do with your chosen credentials. Try logging in debug mode and you might get more info.
hero member
Activity: 672
Merit: 500
true, no miners connected through proxy, but look at a second log it is constant reconnects, no 5 min delays there, it reconnects every 5 seconds
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
hero member
Activity: 672
Merit: 500
Code:
[2016-02-13 20:44:15.742] Proxy 1:stratum+tcp://stratum.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 20:44:20.742] Proxy 1:stratum+tcp://stratum.f2pool.com:3333 recovered
[2016-02-13 20:57:25.442] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 recovered
[2016-02-13 20:57:25.442] Successfully connected to pool 0 stratum+tcp://sha256.eu.nicehash.com:3334 as proxy
[2016-02-13 20:59:30.354] Proxy 1:stratum+tcp://stratum.f2pool.com:3333 reconnect issue to zombies.f2pool.com:3333, dropping existing connection
[2016-02-13 20:59:30.354] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 20:59:35.354] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 21:01:55.891] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 reconnect issue to stratum+tcp://sha256.eu.nicehash.com:3334, dropping existing connection
[2016-02-13 21:01:55.891] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 failed, attempting reconnect
[2016-02-13 21:01:55.892] Successfully connected to pool 1 zombies.f2pool.com:3333 as proxy
[2016-02-13 21:02:00.892] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 recovered
[2016-02-13 21:02:00.892] Successfully connected to pool 0 stratum+tcp://sha256.eu.nicehash.com:3334 as proxy
[2016-02-13 21:08:56.245] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 failed, attempting reconnect
[2016-02-13 21:08:56.245] Successfully connected to pool 1 zombies.f2pool.com:3333 as proxy
[2016-02-13 21:20:20.762] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 21:20:25.763] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 21:40:31.450] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 21:40:36.450] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 22:01:31.443] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 22:01:36.443] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 22:22:30.755] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 22:22:35.755] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 22:42:48.924] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 22:42:53.924] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 23:03:09.367] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 23:03:14.368] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 23:25:08.741] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 23:25:13.741] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-13 23:45:31.433] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-13 23:45:36.433] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 00:06:11.522] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 00:06:16.522] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 00:26:31.409] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 00:26:36.409] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 00:46:48.799] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 00:46:53.799] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 00:57:21.523] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 recovered
[2016-02-14 00:57:21.524] Successfully connected to pool 0 stratum+tcp://sha256.eu.nicehash.com:3334 as proxy
[2016-02-14 01:04:16.722] Proxy 0:stratum+tcp://sha256.eu.nicehash.com:3334 failed, attempting reconnect
[2016-02-14 01:04:16.723] Successfully connected to pool 1 zombies.f2pool.com:3333 as proxy
[2016-02-14 01:08:28.734] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 01:08:33.734] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 01:28:48.041] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 01:28:53.041] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 01:49:08.817] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 01:49:13.817] Proxy 1:zombies.f2pool.com:3333 recovered
[2016-02-14 02:09:28.039] Proxy 1:zombies.f2pool.com:3333 failed, attempting reconnect
[2016-02-14 02:09:33.039] Proxy 1:zombies.f2pool.com:3333 recovered

Code:
[2016-02-14 02:36:43.014] ckproxy generator starting
[2016-02-14 02:36:43.015] ckproxy connector starting
[2016-02-14 02:36:43.015] ckproxy connector ready
[2016-02-14 02:36:43.015] ckproxy stratifier starting
[2016-02-14 02:36:43.015] ckproxy stratifier ready
[2016-02-14 02:36:43.517] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 connection established
[2016-02-14 02:36:43.572] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:36:44.025] Successfully connected to pool 0 stratum+tcp://eu-01.miningrigrentals.com:3333 as proxy
[2016-02-14 02:36:44.025] ckproxy generator ready
[2016-02-14 02:36:48.572] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:36:48.572] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:36:53.573] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:36:53.573] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:36:58.573] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:36:58.573] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:37:03.573] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:37:03.573] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:37:08.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:37:08.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:37:13.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:37:13.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:37:18.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:37:18.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:37:23.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:37:23.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect
[2016-02-14 02:37:28.574] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 recovered
[2016-02-14 02:37:28.575] Proxy 0:stratum+tcp://eu-01.miningrigrentals.com:3333 failed, attempting reconnect


why do i have so many reconnects? i belive my connection is not a problem here
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
quick question: do i need to wire the notifier to a bitcoind node to pick up block solve messages from upstream in proxy mode?   trying to read through the stratum protocol docs to understand it a bit more, but thought i'd just ask.
Bitcoind is not used at all in proxy modes except for node mode.
legendary
Activity: 872
Merit: 1010
Coins, Games & Miners
...
trying it out was my next step.   initially sounded like it applied only in solo mining mode, was unsure if proxy mode get broadcasts from upstream pools.

There's a stratum message that just does that, but i doubt ckproxy has a way to handle it from the command line, you could watch the log for the block hash change messages though.
vh
hero member
Activity: 699
Merit: 666
From ckpool's readme:

Code:
notifier - An application designed to be run with bitcoind's -blocknotify to notify ckpool of block changes.

So you must set your blocknotify option on either bitcoind's command line or bitcoin.conf's

trying it out was my next step.   initially sounded like it applied only in solo mining mode, was unsure if proxy mode get broadcasts from upstream pools.
legendary
Activity: 872
Merit: 1010
Coins, Games & Miners
quick question: do i need to wire the notifier to a bitcoind node to pick up block solve messages from upstream in proxy mode?   trying to read through the stratum protocol docs to understand it a bit more, but thought i'd just ask.

From ckpool's readme:

Code:
notifier - An application designed to be run with bitcoind's -blocknotify to notify ckpool of block changes.

So you must set your blocknotify option on either bitcoind's command line or bitcoin.conf's
vh
hero member
Activity: 699
Merit: 666
quick question: do i need to wire the notifier to a bitcoind node to pick up block solve messages from upstream in proxy mode?   trying to read through the stratum protocol docs to understand it a bit more, but thought i'd just ask.
Pages:
Jump to: