Let me know if you'd like a blurb at the bottom of my pool's home page (which is somewhat inspired by ckpool.org, although, when you're going for the simple look, there aren't a ton of options... maybe I'll add a splash of color).
So long as you say what code it's based on, I'm happy. You need to set max block size to smaller instead then by say 15kb.... though the chance of having a full sized moronic 8MB block is pretty slim. 
Topic: CKPOOL - Open source pool/proxy/passthrough/redirector/library in c for Linux - page 4. (Read 123941 times)
January 12, 2018, 02:31:49 AM
January 12, 2018, 01:39:26 AM
So I'm pretty sure I know your stance on the subject, but FYI I (re-)launched luckypool.co running on ckpool-splns. Its a Bitcoin Cash mining pool backed by a Bitcoin Unlimited node. No Segwit, so not sure how that will affect ckpool (if at all). I did test on testnet and it worked as expected. blockmaxweight is something specific to segwit.
Let me know if you'd like a blurb at the bottom of my pool's home page (which is somewhat inspired by ckpool.org, although, when you're going for the simple look, there aren't a ton of options... maybe I'll add a splash of color).
Let me know if you'd like a blurb at the bottom of my pool's home page (which is somewhat inspired by ckpool.org, although, when you're going for the simple look, there aren't a ton of options... maybe I'll add a splash of color).
January 11, 2018, 09:08:15 PM
You mean with blockmaxweight right?
Yes January 11, 2018, 06:56:11 PM
You mean with blockmaxweight right?
January 11, 2018, 05:45:44 PM
@-ck
I get a segfault with ckpool-splns. It is easily reproducible and so is the fix.
When starting with empty/nonexistant log directories and sock directories, ckpool starts but segfaults as soon as it connects to a bitcoind.
Fix I stumbled upon is to run non-splns ckpool for a bit, then close and run ckpool-splns. No segfaults.
Sorry if this is documented somewhere. Bitbucket seems to have been a mess lately.
Ckpool-splns was designed to be used on the ckpool.org pool only so I didn't really add much in the way of documentation for it apart from in code comments, nor tested it in many environments. Thanks for that. Be aware that if you're using the splns fork with hundreds of users, you must leave room in your block size for the generation transaction as well so set block weight in bitcoind to less than the full amount (something like 3.85MB instead of the max 4MB). Bitbucket had a major cloud storage failure of some sort. I get a segfault with ckpool-splns. It is easily reproducible and so is the fix.
When starting with empty/nonexistant log directories and sock directories, ckpool starts but segfaults as soon as it connects to a bitcoind.
Fix I stumbled upon is to run non-splns ckpool for a bit, then close and run ckpool-splns. No segfaults.
Sorry if this is documented somewhere. Bitbucket seems to have been a mess lately.
January 11, 2018, 05:41:13 PM
@-ck
I get a segfault with ckpool-splns. It is easily reproducible and so is the fix.
When starting with empty/nonexistant log directories and sock directories, ckpool starts but segfaults as soon as it connects to a bitcoind.
Fix I stumbled upon is to run non-splns ckpool for a bit, then close and run ckpool-splns. No segfaults.
Sorry if this is documented somewhere. Bitbucket seems to have been a mess lately.
I get a segfault with ckpool-splns. It is easily reproducible and so is the fix.
When starting with empty/nonexistant log directories and sock directories, ckpool starts but segfaults as soon as it connects to a bitcoind.
Fix I stumbled upon is to run non-splns ckpool for a bit, then close and run ckpool-splns. No segfaults.
Sorry if this is documented somewhere. Bitbucket seems to have been a mess lately.
December 26, 2017, 06:24:31 PM
Hello,
Than it can be treated?
doindex() ?
Thank.
Than it can be treated?
doindex() ?
Quote
[Tue Dec 26 18:52:23.898781 2017] [:error] [pid 7865] [client ip:35162] PHP Fatal error: Uncaught Error: Call to undefined function doindex() in /home/user/ckpool/pool/page.php:594\nStack trace:\n#0
/home/user/ckpool/pool/page_index.php(7): gopage(Array, NULL, 'doindex', 'index', Array, '', false)\n#1
/home/user/ckpool/pool/base.php(455): show_index(Array, 'index', Array, '', false)\n#2
/home/user/ckpool/pool/prime.php(49): showPage(Array, 'index', Array, '', false)\n#3
/home/user/ckpool/pool/prime.php(117): process(NULL, false, Array)\n#4
/home/user/ckpool/pool/prime.php(128): check()\n#5
/home/user/ckpool/html/index.php(2): include_once('/home/user/ck...')\n#6 {main}\n thrown in /home/user/ckpool/pool/page.php on line 594
/home/user/ckpool/pool/page_index.php(7): gopage(Array, NULL, 'doindex', 'index', Array, '', false)\n#1
/home/user/ckpool/pool/base.php(455): show_index(Array, 'index', Array, '', false)\n#2
/home/user/ckpool/pool/prime.php(49): showPage(Array, 'index', Array, '', false)\n#3
/home/user/ckpool/pool/prime.php(117): process(NULL, false, Array)\n#4
/home/user/ckpool/pool/prime.php(128): check()\n#5
/home/user/ckpool/html/index.php(2): include_once('/home/user/ck...')\n#6 {main}\n thrown in /home/user/ckpool/pool/page.php on line 594
Thank.
December 21, 2017, 08:28:30 PM
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.org
Does the SPLNS fork give the block finder a bonus in the block like p2pool does?
December 21, 2017, 08:09:43 PM
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.org
Does the SPLNS fork give the block finder a bonus in the block like p2pool does?
December 20, 2017, 02:32:57 AM
hi ck and kano
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.orgsorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
is that fork public?
edit: nevermind i found it
so, ckpool-splns changes that control the coinbase generation are in stratifier? Is it all documented only in code? or also in a readme somewhere?
Got it. So if I compile and run the splns fork I can expect it to work like your splns pool @ ckpool.org?
December 20, 2017, 12:55:14 AM
hi ck and kano
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.orgsorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
is that fork public?
edit: nevermind i found it
so, ckpool-splns changes that control the coinbase generation are in stratifier? Is it all documented only in code? or also in a readme somewhere?
December 20, 2017, 12:53:53 AM
hi ck and kano
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.orgsorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
is that fork public?
edit: nevermind i found it
so, ckpool-splns changes that control the coinbase generation are in stratifier? Is it all documented only in code? or also in a readme somewhere?
December 20, 2017, 12:03:24 AM
hi ck and kano
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.orgsorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
is that fork public?
edit: nevermind i found it
December 19, 2017, 11:57:43 PM
hi ck and kano
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
That's correct, though there is the ckpool-splns fork which does all the apportioning of reward via coinbase generation without a database, as used on ckpool.org sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
December 19, 2017, 11:55:53 PM
hi ck and kano
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
sorry to hear about the falling out.
without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?
December 08, 2017, 03:53:16 PM
I'm hoping someone has already encountered this and has a quick answer. Otherwise I'll do some digging this weekend. I have set up the ckpool on just a clean local server. If I'm reading the error correctly, it's the URL in the ckpool.conf file that's throwing the error when trying to bind to stratum port. I also haven't seen any info on increasing the rcvbufsiz. TIA.
Assuming you have the correct IP address and you're not trying to bind to a privileged port, usually that means something else is bound to the port already. The rcvbufsiz message tells you what you need to change in your linux config (sysctl.conf). If you're only going to be using ckpool locally it is not needed. Code:
[2017-12-08 12:52:01.802] ckpool generator starting
[2017-12-08 12:52:01.802] ckpool stratifier starting
[2017-12-08 12:52:01.802] ckpool connector starting
[2017-12-08 12:52:01.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:01.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:01.962] Failed to increase rcvbufsiz to 532480, increase rmem_max or start ckpool privileged
[2017-12-08 12:52:02.215] ckpool generator ready
[2017-12-08 12:52:02.215] Connected to bitcoind: localhost:8332
[2017-12-08 12:52:02.287] ckpool stratifier ready[2017-12-08 12:52:06.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:06.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:11.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:11.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:01.802] ckpool stratifier starting
[2017-12-08 12:52:01.802] ckpool connector starting
[2017-12-08 12:52:01.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:01.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:01.962] Failed to increase rcvbufsiz to 532480, increase rmem_max or start ckpool privileged
[2017-12-08 12:52:02.215] ckpool generator ready
[2017-12-08 12:52:02.215] Connected to bitcoind: localhost:8332
[2017-12-08 12:52:02.287] ckpool stratifier ready[2017-12-08 12:52:06.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:06.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:11.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:11.803] Connector failed to bind to socket, retrying in 5s
December 08, 2017, 03:04:21 PM
I'm hoping someone has already encountered this and has a quick answer. Otherwise I'll do some digging this weekend. I have set up the ckpool on just a clean local server. If I'm reading the error correctly, it's the URL in the ckpool.conf file that's throwing the error when trying to bind to stratum port. I also haven't seen any info on increasing the rcvbufsiz. TIA.
[2017-12-08 12:52:01.802] ckpool generator starting
[2017-12-08 12:52:01.802] ckpool stratifier starting
[2017-12-08 12:52:01.802] ckpool connector starting
[2017-12-08 12:52:01.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:01.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:01.962] Failed to increase rcvbufsiz to 532480, increase rmem_max or start ckpool privileged
[2017-12-08 12:52:02.215] ckpool generator ready
[2017-12-08 12:52:02.215] Connected to bitcoind: localhost:8332
[2017-12-08 12:52:02.287] ckpool stratifier ready[2017-12-08 12:52:06.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:06.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:11.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:11.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:01.802] ckpool generator starting
[2017-12-08 12:52:01.802] ckpool stratifier starting
[2017-12-08 12:52:01.802] ckpool connector starting
[2017-12-08 12:52:01.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:01.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:01.962] Failed to increase rcvbufsiz to 532480, increase rmem_max or start ckpool privileged
[2017-12-08 12:52:02.215] ckpool generator ready
[2017-12-08 12:52:02.215] Connected to bitcoind: localhost:8332
[2017-12-08 12:52:02.287] ckpool stratifier ready[2017-12-08 12:52:06.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:06.803] Connector failed to bind to socket, retrying in 5s
[2017-12-08 12:52:11.803] Failed to bind socket for 192.168.1.46:3333
[2017-12-08 12:52:11.803] Connector failed to bind to socket, retrying in 5s
December 02, 2017, 04:24:22 AM
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.
November 13, 2017, 08:46:12 PM
can I mine with nicehash on here?
This is the ckpool SOFTWARE thread. You want the ckpool.org or solo.ckpool.org mining pool thread and the answer is yes. November 13, 2017, 08:45:03 PM
can I mine with nicehash on here?
Jump to: