What's the deal with these NOT confirmed deadlines?
-
@luxe No, I meant I had no idea where it could be coming from - I've never seen a "strange DL source" error.
-
@haitch Did you ever see a 'NOT confirmed' ? If you turn 'debug=true' the current version will log infos about the 'stragne DL source' that leads to 'NOT confirmed'.
In case of a really corrupted plotfile ... the plot will show up over and over again, and you can consider replotting that starnge one. Thats the whole intention.
-
@luxe Thanks for the info. I( have some GPU plotted files that I consider suspect, they get not confirmed or "really" bad deadline message. Will enable the debug and see if I can track them down.
-
@luxe I see it fairly regularly and I have log files full of them, but I really don't think this specific error is a problem with jminer, or if it is then maybe it's a problem with the mining algorithm that both miners are using. I've gotten Blago's miner to report similar errors in debug mode. jminer and blago's miner both work quite well for me too and like I said, my earnings don't seem to be suffering.
@haitch Interested to hear what results you get on your setup as well.
-
@cryo Since you're active in the forums now, could you take a look at the issue above?
@haitch Have you had a chance to test your GPU plots vs your CPU plots? Interested to hear if one or both are throwing this error for you or not.
I'm getting ready to start plotting on a new machine with Xplotter, so I will be able to compare results myself soon. Will report back here when I do.
-
@sevencardz It may be related to this issue.
The GPU plot generator comes with a
verifycommand to verify plots files based on freshly computed nonces.
As you have a large mining power, the fact you experience it from time to time could help to debug this.
Can you try to verify one file reported by the miner? If it's the same problem as the linked issue, the missing/faultly scoop should be located at the end of the file. So a call like the following should suffice:# We generate a test file located at the end of the faultly file ./gpuPlotGenerator generate buffer Z:/13668371040637458609_100699660_800_800 # We verify it against the actual file ./gpuPlotGenerator verify O:/13668371040637458609_99174400_1525760_1525760 Z:/13668371040637458609_100699660_800_800If it's confirmed, I'll track down this bug and help you restore the missing scoops (maybe by adding a
repaircommand).
-
@cryo All this time and I never knew there was a verify command. Here's an offending plot, but the verify command doesn't seem to report any issues:
2017-06-19 17:49:52.972 INFO 2740 --- [roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '268656' send (solo) [nonce '320348789'] 2017-06-19 17:49:53.160 DEBUG 2740 --- [SimpleAsyncTaskExecutor-137481] burstcoin.jminer.JMinerCommandLine : strange dl source 'A:\13668371040637458609_318883840_1525760_1525760' 2017-06-19 17:49:53.160 DEBUG 2740 --- [SimpleAsyncTaskExecutor-137481] burstcoin.jminer.JMinerCommandLine : strange dl file chunks '1', parts per chunk '2', block '372896' 2017-06-19 17:49:53.160 INFO 2740 --- [SimpleAsyncTaskExecutor-137481] burstcoin.jminer.JMinerCommandLine : dl '268656' NOT confirmed! [ 3d 2h 37m 36s ] 2017-06-19 17:49:53.160 DEBUG 2740 --- [SimpleAsyncTaskExecutor-137481] burstcoin.jminer.JMinerCommandLine : strange dl result '50384046118002', calculated '268656' block '372896' nonce '320348789'
-
@sevencardz Can you test around the nonce reported in the miner output (
320348789from your example output):./gpuPlotGenerator generate buffer C:/13668371040637458609_320348689_200_200 ./gpuPlotGenerator verify A:/13668371040637458609_318883840_1525760_1525760 C:/13668371040637458609_320348689_200_200
-
@cryo Oh yes thank you, seems I can't maths. I will try that once I'm home in a few hours. :)
-
@cryo OK, I switched to another drive, but I think I've got the hang of it now.
First, the offending plot and nonce:
2017-06-16 18:28:48.657 INFO 8580 --- [roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '285118' send (solo) [nonce '457319171'] 2017-06-16 18:28:48.891 DEBUG 8580 --- [SimpleAsyncTaskExecutor-19339] burstcoin.jminer.JMinerCommandLine : strange dl source 'E:\13668371040637458609_456202240_1525760_1525760' 2017-06-16 18:28:48.907 DEBUG 8580 --- [SimpleAsyncTaskExecutor-19339] burstcoin.jminer.JMinerCommandLine : strange dl file chunks '1', parts per chunk '2', block '371829' 2017-06-16 18:28:48.907 INFO 8580 --- [SimpleAsyncTaskExecutor-19339] burstcoin.jminer.JMinerCommandLine : dl '285118' NOT confirmed! [ 3d 7h 11m 58s ] 2017-06-16 18:28:48.907 DEBUG 8580 --- [SimpleAsyncTaskExecutor-19339] burstcoin.jminer.JMinerCommandLine : strange dl result '6440749087779', calculated '285118' block '371829' nonce '457319171'
-
@sevencardz Sounds like it's not only affecting the last scoop. I'll run some tests on my side to try to reproduce this.


