late nonce submission
-
-
@jervis In witch pool are you mining?
-
@gpedro eu
-
@jervis I'd never encountered this issue. The error stopped or continues on every single block?
-
@gpedro come and goes.
-
@jervis If i was me, i wouldn't care... but i would try to understand why its happening so @Blago could you take a look?
-
@gpedro yup. I wouldn't care too much but it's always good to know what's what. :D
-
@jervis Block 257021 was won in 3 seconds. Your miner continued to send deadlines for this round before the miner realized another block has started. The pool realizes that the submissions you submitted were for the last round, and sends back that update message - "Yes I got your DL, but we've moved onto the next block already". Are you using the AIO miner ? Check the UpdateInterval setting in the miner.conf, and consider lowering it if it's too high - default is 2 seconds.
-
@haitch {
"Mode" : "pool",
"Server" : "pool.burstcoin.eu",
"Port" : 8124,"UpdaterAddr" : "pool.burstcoin.eu",
"UpdaterPort" : 8124,"InfoAddr" : "pool.burstcoin.eu",
"InfoPort" : 8124,"EnableProxy" : false,
"ProxyPort" : 8126,"Paths":
[
"E:\Burst\plots","D:\Burst\plots"
],
"CacheSize" : 100000,
"ShowMsg" : false,
"ShowUpdates" : false,"Debug" : true,
"SendBestOnly" : true,
"TargetDeadline": 4000000,"UseFastRcv" : false,
"SendInterval" : 100,
"UpdateInterval" : 950,"UseLog" : true,
"ShowWinner" : false,
"UseBoost" : false,"WinSizeX" : 80,
"WinSizeY" : 60
}
-
@jervis That looks fine, only other suggestion is to make sure your clock is accurate, if it's off it can cause mining issues. I use: http://www.worldtimeserver.com/atomic-clock/
-
@jervis very interesting... pls send to me blagodarenko@gmail.com your last logs from
%AppData%\BurstWallet\miner-burst-1.160705\Logs\




