New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CGminer can't connect over RPC on 0.20.0 #19182
Comments
Could be related to e42c959 |
There's a message in bitcoin talk that this is due to the coinbaseaux flags field being removed: https://bitcointalk.org/index.php?topic=5253096.msg54839526#msg54839526 |
I'm not very familiar with ckpool but it looks like that's the problem: https://bitbucket.org/ckolivas/ckpool/src/b8f66852483542326de8c5705a3e36242347ad12/src/bitcoin.c#lines-147 If I'm right, that's a bug in ckpool. It shouldn't be failing on absence of the coinbaseaux flag, since that's not a required field in the gbt response: https://github.com/bitcoin/bips/blob/master/bip-0022.mediawiki#block-template-request. @jameshilliard does that look right to you? |
Agree with @jnewbery's assessment. |
This happens with solo mining too. Also happens on 20.1 |
I'm new to solo mining but I'm noticing the same after full node sync and cgminer config. Anyone find a workaround to the GBT decode issue? |
If you need a workaround, you should be able to use BFGMiner as a stratum proxy for cgminer. |
Could you provide more detailed instructions? |
To validate your setup on testnet, also pass |
Any reason we can't just include |
@sipa that would probably work, but seems ugly just to deal with third-party unmaintained and broken code... Core doesn't even try to remain reasonably compatible with Knots, so why unreasonably for cgminer? |
If it's unmaintained then I withdraw my suggestion. |
We definitely need a maintained alternative for desktop miners. Even if usb asics do not make any profit, it's still a good learning experience and people use them. |
Ok that's for bfg. What do I do with cgminer after that? |
Point it at localhost:3334 (But if it's a USB stick miner, you can probably just use BFGMiner by itself...) |
Yeah, looks right.
Last I checked Con Kolivas seemed open to transferring the cgminer project if a suitable organization was interested in maintaining cgminer. |
I just dropped BTC core 0.19 (latest before 0.20) on top of the new files to revert installation and keep block info and now it's working. Solo mining on valid address :) with cgminer and no stratum port. Not that I'll ever solve a block but maybe I'll start learning the space and make/update a miner? |
I've tried using bfgminer but it reports the pool is down or invalid, using the same server settings that I use for cgminer. I'll keep checking into this, I was using cgminer since it was updated for my device. If anyone has any suggestions, I'd appreciate them. |
Did you include |
Yes, I tried it both with and without. bfgminer -o 'http://127.0.0.1:8332/#getcbaddr' -u User -p Password --generate-to 394zcJWJfDwQPYxJ18u5fWaJkVwx76D8KP --stratum-port 3334 |
Add Is the node synced? |
Yes the node is synced. I see multiple errors in that log: [2021-01-18 08:30:22] Stratum connect failed with TLS to pool 0: gnutls_handshake() failed: An unexpected TLS packet was received. [2021-01-18 08:30:22] JSON decode failed(1): '[' or '{' expected near 'HTTP' [2021-01-18 08:30:22] Pool 0: gnutls_handshake() failed: An unexpected TLS packet was received. [2021-01-18 08:30:22] Pool 0: RECV: HTTP/1.1 400 Bad Request [2021-01-18 08:30:22] FAILED to retrieve work from pool 0 http://127.0.0.1:8332/#getcbaddr |
@Beeskee Im not sure if this would have helped bfgminer but try downgrading your Bitcoin core to v0.19.1 and configuring cgminer again. I've been solo mining on 8 newpac miners @500mhz (907.5GH/s avg) for a couple weeks now with only one reboot for core disconnect. Two more incoming :) I know odds are crap but I told myself to build a 1TH unit and leave it for the lotto! Good luck! |
Yes, I downgraded Bitcoin in the meantime to continue using cgminer directly, but I don't like the idea of being stuck on a prior version with no way to upgrade. |
Gotcha. I thought about this as well. If you do get bfgminer working on newest core ver. Reach out to me. I might want to follow along. |
|
after starting ckpool, on fresh install of bitcoind and ready synced with txindex=1 I got this lines on bitcoind, and ckpool tries and tries this :
BITCOIND |
Did your lotto work |
@mshalabi1990 I haven't found a block yet (though I wouldn't tell anyone if I did ;) ) but my highest share has been 537m. That's a long way from 20.6t. |
Sucks. I also solo mine with newpacs and cg. Finally was upgrading node from 19.1 to 21.0 tonight and wasted last 2h troubleshooting this. Downgrading... |
@Joz3d Why downgrade the node rather than upgrade the miner? |
@luke-jr Downgraded to previous version bitcoind as the quickest solution to get up and running again. You're right, the miner needs to be upgraded but getting author to update that/forking if need-be is an unexpected effort. Oh well, will work on it. |
@Zwilla
|
This issue is resolved in https://github.com/cmmodtools/cgminer Specifically in commit cmmodtools/cgminer@b9e0f86 |
Can this be closed, given that this is an upstream issue? Let me know if it should be reopened. |
@Zwilla I ran into the same issue with ckpool v0.9.5 + bitcoind v22.0.0. I was able to get ckpool working by commenting out references to "coinbase_aux" in ckpool src/bitcoin.c as well as setting the "flags" variable to an empty string. |
After upgrading to 0.20.0 cgminer throws the following error:
Pool 0 JSON failed to decode GBT
I'm assuming there are some additional rpc settings for the .conf file which I need to specify as of 0.20.0, but I don't know which. I downgraded to 0.19.1 and it's working fine. Any help would be appreciated.
`
The text was updated successfully, but these errors were encountered: