CKPOOL - Open source pool/database/proxy/passthrough/library in c for Linux

[kano]

... Is there a way to prevent this switch from happening on a pool restart?

It's more a problem of knowing at what commit the ckpool programs are tested and working ...
As far as I know that is some time last year ...
The last tag is v0.9.4 2016-08-23 (for standard ckpool I run ded126d5 which is the same thing since there's no ckpool changes in between them and there's a deadlock some point after that and the workinfo changes after that can break ckdb shift processing and payouts)

The problem is that there's a collection of ckpool programs in there and they aren't all tested properly or at all (and at what version/commit):
Mining pool, standard proxy, passthru proxy, proxy node, remote node, redirector, bitmain's hidden ckpool api to manage ckpool programs directly.

[dogedood]

... Is there a way to prevent this switch from happening on a pool restart?

It's more a problem of knowing at what commit the ckpool programs are tested and working ...
As far as I know that is some time last year ...
The last tag is v0.9.4 2016-08-23 (for standard ckpool I run ded126d5 which is the same thing since there's no ckpool changes in between them and there's a deadlock some point after that and the workinfo changes after that can break ckdb shift processing and payouts)

The problem is that there's a collection of ckpool programs in there and they aren't all tested properly or at all (and at what version/commit):
Mining pool, standard proxy, passthru proxy, proxy node, remote node, redirector, bitmain's hidden ckpool api to manage ckpool programs directly.

This deadlock you mention, can you provide more info?

[kano]

... Is there a way to prevent this switch from happening on a pool restart?

It's more a problem of knowing at what commit the ckpool programs are tested and working ...
As far as I know that is some time last year ...
The last tag is v0.9.4 2016-08-23 (for standard ckpool I run ded126d5 which is the same thing since there's no ckpool changes in between them and there's a deadlock some point after that and the workinfo changes after that can break ckdb shift processing and payouts)

The problem is that there's a collection of ckpool programs in there and they aren't all tested properly or at all (and at what version/commit):
Mining pool, standard proxy, passthru proxy, proxy node, remote node, redirector, bitmain's hidden ckpool api to manage ckpool programs directly.

This deadlock you mention, can you provide more info?

It's no longer relevant.
ckpool deadlocks talking to ckdb, he doesn't test his changes with ckdb ... i.e. Bitmain pays him to break ckdb ... often.
... and he doesn't even test the effects of his changes on all the other ckpool modules

[agentcash]

Might have a memory leak when running ckproxy. Had a Pi start acting up this morning after running fine for about 3 weeks. Turned out it ran out of free memory and the watchdog had trouble killing it and killed some system processes instead. Checked the other Pis and the ckproxy process was using high amounts of memory. Percentage-wise the memory on most of them had gone over 60%, where on a fresh start it's more around 6-7%.

Edit: To note the Pi that locked up was also the one handling the highest hashrate, so that may be related. Since it ran out of memory while the lower hashrate Pis still had some free.

[-ck]

Might have a memory leak when running ckproxy. Had a Pi start acting up this morning after running fine for about 3 weeks. Turned out it ran out of free memory and the watchdog had trouble killing it and killed some system processes instead. Checked the other Pis and the ckproxy process was using high amounts of memory. Percentage-wise the memory on most of them had gone over 60%, where on a fresh start it's more around 6-7%.

There could well be, especially if you're running older code. Try running latest git if you haven't upgraded lately as the code has been dramatically updated. When time permits I'll do a more extensive search for memleaks with the proxy code.

[JanAndre]

Hi guys, I hope this is the right thread to submit a question.
We have successfully installed, and started CKpool, but only in Standalone mode. It doesn't seems like we are receving any blocks, so i want to start the pool in regular mode. we have installed DB, so that should be ok. The problem is when we start with just ckpool, we can connect any workers.
I know im a noob in this, so Im hoping to get some tips of what could be wrong. Im helping out a freind in Asia, that have 70 units of Antminer S9 ready.
Any input would be helpful. Im not sure about the directory permissions and also the correct syntax to startup the pool.

There are so little information about CKpool and how to run it.

Please help!

[-ck]

Hi guys, I hope this is the right thread to submit a question.
We have successfully installed, and started CKpool, but only in Standalone mode. It doesn't seems like we are receving any blocks, so i want to start the pool in regular mode. we have installed DB, so that should be ok. The problem is when we start with just ckpool, we can connect any workers.
I know im a noob in this, so Im hoping to get some tips of what could be wrong. Im helping out a freind in Asia, that have 70 units of Antminer S9 ready.
Any input would be helpful. Im not sure about the directory permissions and also the correct syntax to startup the pool.

There are so little information about CKpool and how to run it.

The documentation is all in the ckpool readme for running it in standalone mode and it is well documented. If that is not clear enough then can I suggest you're probably not skilled enough to run a pool? If you're not finding blocks then you're not finding blocks; perhaps you don't even understand that 70 Antminer S9s is an extremely small hashrate to find blocks by today's standards.

[JanAndre]

Thank you for your answer.. I found it a bit arrogant, but a answer anyway.
I'm not running the pool, I'm trying to help out friends in Asia, that dont understand English to good.

I would find your answer more helpful if it actually contained some info about the problem.

The only good information i got from your post, is that its maybe not a good idea to run CKpool with 'just' 70 units of Antminer S9. I will let the right persons know.

I know they are waiting to get a confirmation that the CKpool works, and they will purchase another 1000 units.

Have a nice day, regards Jan.

[martelu]

Thx CK for the reviews and the explanations.

[Hannu]

Oh no did i lost you on technical problems? "Cannot send to channel #ckpool" Nou! What is wrong with it? I use data cloud.
I dont have purpose to trolling or anything like that   Technical data is important to me and if you need ask something.

[-ck]

Oh no did i lost you on technical problems? "Cannot send to channel #ckpool" Nou! What is wrong with it? I use data cloud.
I dont have purpose to trolling or anything like that   Technical data is important to me and if you need ask something.

The IRC channel was under attack and moderation of the whole channel had to be turned on to manage it. This has been rectified now.

[makkotech]

Awesome, Thank you, guys!!! Full Node running !!!, I am a Happy Panda lol, Guys I need a recommendation, what is the best option to run this like a behind process and close my terminal without killing the process, I try it using:

-  screen, Forever, pm2, & option, etc .. etc ..

But every time that I use one of those the process was broken, I need help to apply the best practice doing this last step.

Thank you in advance.

[o_solo_miner]

If you use screen, you have to start screen first and then
your bitcoind in daemon mode with blocknotify:
bitcoind -daemon -blocknotify=/usr/bin/notify.sh

then you must start ckpool with your wanted option like this:
ckpool -A -s /opt/ckpool

and optional the Relaynetworkclient:
./relaynetworkclient 127.0.0.1 8333

or you use the Fibrenetwork in conjunction with bitcoind 14.1 and a propper bitcoin.conf

Some Help for Screen:

screen [ENTER]
CTRL A followed by CTRL C to open another Screen console
CTRL A followed by CTRL K to kill a Screen console
to switch between screen console
CTRL A followed by N for next screen
CTRL A followed by P for previous screen

If you want to return to main console, without stopping screen and all running processes:
CTRL A followed by D to detach from screen and return to main console
( ckpool and all other stuff you started is still running in the background, you can check that with top or
htop if you have it installed )

to reconnect later to a running screen just type:
screen -r [ENTER]

sometimes that is not possible and a message appears telling you allready connected
so you type screen -d -r [ENTER]

thats all

But every time that I use one of those the process was broken

is not very helpfull, please include the complete message for fault finding next time

EDIT: like allways typo

[makkotech]

If you use screen, you have to start screen first and then
your bitcoind in daemon mode with blocknotify:
bitcoind -daemon -blocknotify=/usr/bin/notify.sh

then you must start ckpool with your wanted option like this:
ckpool -A -s /opt/ckpool

and optional the Relaynetworkclient:
./relaynetworkclient 127.0.0.1 8333

or you use the Fibrenetwork in conjunction with bitcoind 14.1 and a propper bintcoin.conf

Some Help for Screen:

screen [ENTER]
CTRL A followed by CTRL C to open another Screen console
CTRL A followed by CTRL K to kill a Screen console
to switch between screen console
CTRL A followed by N for next screen
CTRL A followed by P for previous screen

If you want to return to main console, without stopping screen and all running processes:
CTRL A followed by D to detach from screen and return to main console
( ckpool and all other stuff you started is still running in the background, you can check that with top or
htop if you have it installed )

to reconnect later to a running screen just type:
screen -r [ENTER]

sometimes that is not possible and a message appears telling you allready connected
so you type screen -d -r [ENTER]

thats all

But every time that I use one of those the process was broken

is not very helpfull, please include the complete message for fault finding next time

EDIT: like allways

Awesome thank you for your response now my ckpool is running behind using screen, I am so Happy guys, all of you are amazing, I´ll keep you posted!! Next Goal: Implement a new node using ckdb !!!