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

Understood - but I thought I saw a message earlier that someone had compiled it on a 32bit processor and it worked. I expected it wouldn't compile if that were the issue but it does and connects to kano.is with no problem. Just can't submit any shares.

I'll drop the experiment. Thought a simple, cheap, power efficient proxy would be good to run vs having it on one of my servers. It would be good to have a redundant, backup proxy.

32bit processor? There's no 32 bit support in ckpool code.

I've been using ckproxy on a Centos machine for a while to connect to Kano.is and haven't had any problems. Thanks for writing this - its nice to have one connection out instead of one per machine.

I thought I would see if one of the small project boards would work as a proxy so I compiled it on an Odroid C1 (fedora). Compiled easily with only signed/unsigned warnings and connects just fine to kano.is but I get the following error when a miner finds a share and tries to submit it:

[2015-06-13 23:36:56] Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2953
[2015-06-13 23:36:56] Attempted to send null message to generator in send_proc
[2015-06-13 23:37:00] Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2953
[2015-06-13 23:37:00] Attempted to send null message to generator in send_proc
[2015-06-13 23:37:06] Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2953
[2015-06-13 23:37:06] Attempted to send null message to generator in send_proc
[2015-06-13 23:37:12] Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2953
[2015-06-13 23:37:12] Attempted to send null message to generator in send_proc
[2015-06-13 23:37:13] Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2953
[2015-06-13 23:37:13] Attempted to send null message to generator in send_proc
[2015-06-13 23:37:17] Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2953
[2015-06-13 23:37:17] Attempted to send null message to generator in send_proc

Any ideas on what could cause this?

I have it running right now without any miners attached and the log just has standard messages (0 hashrate and block hash change messages). When miners attach, they show share submitals, etc so it looks OK on that side. But proxy has the errors above and the pool doesn't show the shares since I'm sure they're not getting submitted.

Thanks

My Pool Now is Online )))

Thank You CK for your effort , Your ckpool now connected to bitcoind.

It's take about 14 days , more than 30 issues fixed until i seen my miners online and worked to my pool .

Actually it takes this period due to low resources on internet to running this kind of programs , Also my linux knowledge not so good .

I run bitcoind on windows server 2012  5G Ram 4 Processor

Running ckpool on centos   3g Ram .

Now Trying to fix Internal Server Error in webserver to got stats but ckpool.log is working fine for me as privet pool .

Now I don't care to spent 6 btc renting hash to my pool expect for orphans race .

Finlay Thanks very much you CK and Kano .
I ll be happy to know donation address to support this develop .

Regards


I got this Error every 10 minutes and sometimes every 1 h But pool working good and accept works .

[2015-06-09 02:29:27] Failed to recv in read_socket_line with errno 11: Resource temporarily unavailable
[2015-06-09 02:29:27] Failed to read http socket lines in json_rpc_call
[2015-06-09 02:29:27] Reopening socket to 64.#####:8332
[2015-06-09 02:29:27] Failed to get valid json response to getblocktemplate
[2015-06-09 02:29:29] Failed to recv in read_socket_line with errno 11: Resource temporarily unavailable
[2015-06-09 02:29:29] Failed to read http socket lines in json_rpc_call
[2015-06-09 02:29:29] Reopening socket to 64.#####:8332
[2015-06-09 02:29:29] Failed to get valid json response to getblocktemplate
[2015-06-09 02:29:29] CRITICAL: No bitcoinds active!

Restarting Bitcoind is a pain killer then restarting ckpool it return to

root@ip-###### [/home/owner/public_html]# ckpool -A
[2015-06-09 02:40:15] Unable to parse serverurl entries as an array
[2015-06-09 02:40:15] ckpool generator starting
[2015-06-09 02:40:15] ckpool stratifier starting
[2015-06-09 02:40:15] ckpool connector starting
[2015-06-09 02:40:16] ckpool connector ready
[2015-06-09 02:40:16] ckpool stratifier ready

Look at this address sir,, make me confuse https://blockchain.info/address/1CD523oyvmb9QVyABc1uu9Zt9ovjPzXV7h

Maybe this attack the network?

You need to look at bitcoind not ckpool.

Thank you for answer sir,,but on my control panel show like this

Peer connected above 40,so with my problems like that,it's safe for solo mining or not sir...last day i was sending 1200Th and seems no problem,,but when i check ckpool.log showing error 

You need more resources for bitcoind or protect it from the bitcoin network
It's god awful resource hungry and on occasions when you are getting spammed with transactions, it wont reply for quite a while.
I've spent a lot of time over the past 4 days dealing with bitcoin problems and making sure (in advance) that the 2 blocks my pool found over that time weren't orphans ...

Runing ckpool without ckdb on my vps one week,but every 2-3 hour showing error ,,


My vps spec
Ram 4Gb swap 4 Gb
bitcoind version 0.10.1

I have been running a bunch of S3+ to BTC Guild and solo.ckpool.  The other day I installed ckproxy to combine all my miners into one connection. This is working well, with essentially the same hash rate at the pools as before.  However, my individual miners are showing 10 - 13 % rejected shares and around 1% stales.  I am curious as to why I am getting these errors or if anyone else sees similar errors.

I am using standard configuration of ckproxy.  The miners are using August, 2014 firmware, with cgminer updated to 4.6.0.

Yeah all the main loops in all the threads, and the db loading at the start, check 'everyone_die'
It's a simple trigger to shut down in a tidy manner - once they all say they've finished, it then completes the (unnecessary) code shutdown of freeing all the ram and disconnecting.

There's a main loop that checks if 'everyone is dead' and reports every few seconds who isn't finished yet so you can see on shutdown if a thread has locked up for some unexpected reason, and which thread it is - and a Ctrl-C will simply kill it all then and there.
i.e. you can decide if it doesn't matter to hit Ctrl-C now and kill it during an unexpected shutdown failure
- rather than the code killing everything when you send a terminate message, and threads not having a chance to finish their current action

I do lots of updates to ckdb quite regularly - so if you want to stay up to date with it, it's best to idle in the #ckpool IRC to know when I make changes and ask if you need to know if there's any steps required with a change
e.g. the recent change to no longer storing sharesummaries in the permanent DB means you can:
 delete * from sharesummary; vacuum sharesummary;
since the leftover data in there is no longer needed

Watch out for disk space, the hourly logs can get big fast if you have a lot of shares coming in.
- also note you can compress the ckpool logs/ckdb2*.log files and the ckdb reload will still reload them, use any of: lrzip, bzip2 or gzip
... but don't compress the current one while it's still being written to or the hour in it's UTC name is current
all other log files can of course be compressed as and when you like since ckdb doesn't need to read them

Its already been taken care of.  It is now up and running.. btw.. love the Findshare&&EveroneDie!

Thanks Mikestang

Be sure to use a secure rpc username and password, like the one Bitcoind generates.

Thank you very much

I'm creating it now .

I really appreciate your reply.

Thanks

Bitcoind doesn't automatically create bitcoin.conf when you install it so you have to create one yourself. Make a new text file (with any text editor) and put in those lines. Then save it as bitoin.conf and put it in the bitcoin data directory.

Watch the extension of the file; it needs to be exactly bitcoin.conf and not for example bitcoin.conf.txt


edit: if your bitcoind is running on another pc then ckpool you'll have to put in 'rpcallowip=ip of ckpool pc' as well

edit: and for the port you might want to add 'rpcport=8332'. You can look at https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File for all the options

Hi Con

I spent about 10 h last night to connect but its always Failed to connect socket

I tried
localhost:8332
localhost:3333
myserverip:3333
myserverip:8332
myserverip:80
url:3333

still Failed to connect socket
No bitcoinds Active !

Im running centos 6.6

Also I cant find
bitcoin.conf  file as you said in documet

CKPOOL configuration

At least one bitcoind (aka btcd) is mandatory in ckpool mode with the minimum requirements of server, rpcuser and rpcpassword set. If no btcd is set up in the configuration, ckpool will look for a running bitcoind on the local machine on the default port 8332 and the username "user" and password "pass" set up.

At the very least you will need the following lines in your bitcoin.conf file:

Code:

server=1
rpcuser=user
rpcpassword=pass
rpcallowip=127.0.0.1

I like your style, kano.  Now if only we could do something about some of those pools that do have "bad code" (for lack of a better description) that lets miners do things that are bad for bitcoin...

Its up to you

You can answer simple questions or ignore, but setup a db is not easy and some users here like me can pay for setup db pool .

if you can do it with charge it will be a solution than ignoring us .

... create the database ...

... and I'll add my usual comment about this:
If you need someone to tell you how to create a database and configure it and can't understand the sql/ directory then you shouldn't be running a pool.
I wont ever be supplying step by step hand holding instructions for setting up ckdb since what needs to be done there is mostly what someone who can run a pool should know how to do.

If you ask questions that show that you know what you are doing, you will get answers.
If you ask questions for hand holding, I'll ignore them.

If you are going to ask more than 1 or 2 questions, then visit IRC, since I'm also not going to spend pages posting answers here.

I'm not interested in helping someone setup a pool that is bad for the miners if the pool OP can't fully manage the pool.
We have enough scams in the community without me helping people screw over miners (intentionally or unintentionally)