Author

Topic: Blocks rejected when solo mining but accepted on pool? (Read 249 times)

hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
Thanks but unfortunately it doesn't display the reject reason. It seems there is a software bug
that only affects solo mining. Your best bet is to look for another compatible miner, I can't help
you there.

Thanks!

Ill setup my Pi with cgminer and see if it works on that one instead Cheesy
full member
Activity: 1424
Merit: 225
Thanks but unfortunately it doesn't display the reject reason. It seems there is a software bug
that only affects solo mining. Your best bet is to look for another compatible miner, I can't help
you there.
hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
Based on your initial problem description I suspect a SW bug in the miner for solo mining. The protocol
sems to be correct if you're getting blocks, submitting hash and getting a reply.

The reject reason will provide more info. Invalid shares are usually user error (wrong algo) or a SW bug in the
hash code. There are other types of rejects that could point in another direction.

You could try another version of cgminer. I've never used it myself so I'm not familiar with it's issues and quirks.

But it's best to get more info before drawing any conclusions.

Got a screenshot for ya:



That is what I get when I hit a block.
hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
Based on your initial problem description I suspect a SW bug in the miner for solo mining. The protocol
sems to be correct if you're getting blocks, submitting hash and getting a reply.

The reject reason will provide more info. Invalid shares are usually user error (wrong algo) or a SW bug in the
hash code. There are other types of rejects that could point in another direction.

You could try another version of cgminer. I've never used it myself so I'm not familiar with it's issues and quirks.

But it's best to get more info before drawing any conclusions.

Interesting..

I am using CGminer 4.10 on windows.

I am not sure how to compile it on Linux, but I have a server that I could test it on instead.

And I dont know how to compile previous versions of CGminer on Windows.
full member
Activity: 1424
Merit: 225
Based on your initial problem description I suspect a SW bug in the miner for solo mining. The protocol
sems to be correct if you're getting blocks, submitting hash and getting a reply.

The reject reason will provide more info. Invalid shares are usually user error (wrong algo) or a SW bug in the
hash code. There are other types of rejects that could point in another direction.

You could try another version of cgminer. I've never used it myself so I'm not familiar with it's issues and quirks.

But it's best to get more info before drawing any conclusions.
hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
If you're getting rejects you were properly connected to  the wallet in the first place.
Perhaps you should provide more info as I requested rather than following random
advice based on incomplete information.

Gotcha, ill setup the solo mining again tonight and take some screenshots and a copy of the config.

full member
Activity: 1424
Merit: 225
If you're getting rejects you were properly connected to  the wallet in the first place.
Perhaps you should provide more info as I requested rather than following random
advice based on incomplete information.
hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
So, I checked out my config, and did not have the rpcport setup.

I changed it and its now:
rpcuser=x
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=18124
server=1
daemon=1
listen=1

Still getting rejects :/
hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
Did you set the conf file correctly? Afaik you have to do a little more than just start the wallet/daemon.
I don't know if this is (still) OK for the coin you mine, since it's 5 years old, but it could be a start: https://bitcointalksearch.org/topic/a-how-to-guide-for-solo-mining-521563
At least the
Code:
server=1
listen=1
daemon=1
part may be of interest.

Thank you for this.

I am currently at work, but when I get home tonight I will check the config and see if I forgot to add this.
Ill report back later with my findings! Cheesy
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
Did you set the conf file correctly? Afaik you have to do a little more than just start the wallet/daemon.
I don't know if this is (still) OK for the coin you mine, since it's 5 years old, but it could be a start: https://bitcointalksearch.org/topic/a-how-to-guide-for-solo-mining-521563
At least the
Code:
server=1
listen=1
daemon=1
part may be of interest.
full member
Activity: 1424
Merit: 225
If you're submitting blocks and they are being rejected it's not problem with your network.
More "technical" details would help, like command line options and console output.
The backstory wasn't necessary.
hero member
Activity: 1202
Merit: 507
Pinch.Network Guaranteed Airdrop
Hi Bitcointalk.

So, I got my hands on a good old Butterfly Labs Jalapeño.

It runs at around 8GH/s and its enough to play around with some old dead coins and mine for fun.

I found a coin that I have mined for a few days and today the network hash dropped to a point where it should be easy for me to solo mine it.

So I switched over and started to solo mine, and I did start mining blocks.. But every single one of them got rejected.

This makes no sense to me since Pool mining was working great.

Could it be a problem with my network?
Do I need to port forward the wallet rpc port? Miner issue? (Using cgminer).

Any ideas?
Jump to: