Here's the case: @luxe @haitch @blago @Propagandalf
Every few blocks or so, jminer will report 'strange dl source' and the corresponding deadline is rejected by the wallet. I get very similar errors when running blago's miner if I run it alongside jminer and both miners find and submit the same faulty deadline, which suggests it's not an issue with jminer. Mining capability doesn't seem to be hindered at all and I am forging one or two blocks a day just as the calculator predicts.
Here's one of the best examples I've seen. Not one, but two instances of this particular error, followed by a rejected deadline. What makes this once special is that in both instances an identical deadline was found with a DIFFERENT nonce, submitted, and confirmed all in the same round!
Kudos to @luxe for the nice new jminer debug and resubmit features. :)
So to recap, the sequence of events was as follows:
101828 send (solo) nonce 100456385
strange dl source ...
101828 NOT confirmed!
101828 send (solo) nonce 69945281
55249 send (solo) nonce 356987563
strange dl source...
55249 NOT confirmed!
55249 send (solo) nonce 326476459
The same deadline being confirmed from a different nonce doesn't always happen alongside the strange dl error, but it seems to happen too frequently to be pure cooincidence. My setup:
I have 96TB of optimized plots on twelve 8TB drives.
All plots were created in direct mode with GPU Plot Generator.
I mine solo on a dedicated machine with a local wallet on the latest version: 1.2.8.
One theory is that GPU plot generator is somehow creating semi-corrupted plot files where some nonces are faulty. However, it seems unlikely that a plotting algorithm would create an incorrect nonce only about 1% of the time. On top of that, many of the exact same plot files are currently being mined and they report valid deadlines and some have even forged blocks.
Another theory is that the algorithm for scanning plot files is shared by both (or all?) miners and that this algorithm is finding and reporting deadlines which are false positives... but only sometimes... on certain plot files... for some reason. If this is the case, then there's not really anything to worry about.
Any suggestions or comments on what might be causing this or what I might have done TO cause it? Are you guys seeing these errors too?