Keep your system time in sync please!


  • admin

    Everyone running a pool or mining solo should check (if not sure about it) if system time is in sync. i saw some rejected blocks due to wrong time in wallets logs in the last days.


  • admin

    @luxe ntptime reports the time is ok on all mine.


  • admin

    @haitch I was quite sure it was not on your side, maybe new solo miner or a new pool.



  • @luxe seen couple such errors in my command line as well.



  • @ZapbuzZ said in Keep your system time in sync please!:

    http://www.ebay.com.au/itm/1PPS-USB-GPS-ublox-GR-8013W-for-NTP-time-server-GR-601W-replacement/282055709355?_trksid=p2045573.c100033.m2042&_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20131017132637%26meid%3Ded86c8e84efa47f4b6f20cc7e068f739%26pid%3D100033%26rk%3D1%26rkt%3D8%26sd%3D282055709355

    a tip from somebody that went through this: forget USB for Pulse-per-second GPS. USB is polled, eating up a full core with gpsd, and still has only 1ms accuracy. Go for a "proper" serial connection, next-to-no overhead and 50-100 us accuracy.

    But that is uneccesary for the Wallet, it is happy with offsets <1s (for very short blocks), and on the order of 10s in general.



  • @vaxman thanks for that.


  • admin

    Once again, someone is seriously losing money out there, just because his pool or solo setup run through a wallet without system time in sync.
    0_1495261521032_Unbenannt.PNG



  • @luxe Yep :), also from my side, here's my wallet last night infos (CET, same as you I believe...):

    2017-05-20 01:32:00 SEVERE: Block not accepted
    nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87514344 cu
    rrent time is 87514320, previous block timestamp is 87514238
            at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84
    9)
            at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4
    5)
            at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
            at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
            at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    access$301(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    2017-05-20 02:41:29 SEVERE: Block not accepted
    nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87518516 cu
    rrent time is 87518490, previous block timestamp is 87518169
            at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84
    9)
            at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4
    5)
            at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
            at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
            at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    access$301(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    2017-05-20 02:41:39 SEVERE: Block not accepted
    nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87518516 cu
    rrent time is 87518500, previous block timestamp is 87518169
            at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84
    9)
            at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4
    5)
            at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
            at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
            at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    access$301(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    2017-05-20 03:52:59 SEVERE: Block not accepted
    nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87522809 cu
    rrent time is 87522779, previous block timestamp is 87522342
            at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84
    9)
            at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4
    5)
            at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
            at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
            at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    access$301(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    2017-05-20 04:55:38 SEVERE: Block not accepted
    nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87526559 cu
    rrent time is 87526538, previous block timestamp is 87526420
            at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84
    9)
            at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4
    5)
            at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
            at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
            at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    access$301(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    2017-05-20 09:26:59 SEVERE: Block not accepted
    nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87542835 cu
    rrent time is 87542819, previous block timestamp is 87542630
            at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84
    9)
            at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4
    5)
            at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
            at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
            at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    access$301(Unknown Source)
            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
    run(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    

    Three data seem to coincide (01.32, 03.52 and 04.55).
    My time is in sync (checked multiple time in this days, last one 5 minutes ago and it's ok).
    I've checked the invalid timestamp with the local wallet api (http://localhost:8125/burst?requestType=getBlock&timestamp=xxxxxxxx): in the end all blocks has been accepted, except for the 03.52 one.
    The accepted ones timestamps (all of them) belong to blocks forged by @PingOfd3ath pool... I can add that they are not the first blocks generated by this pool that my wallet reject (I lost the logs due to yesterday evening blackout...)


  • admin

    @Dario's-wallet Sad for miners there if you are right ... so @PingOfd3ath please check/fix your system time.



  • @luxe I have to say that I've checked in this way several invalid timestamps logs these days: luckily they were all rejected-then-accepted blocks (Burst network seems flexible atm). The 03.52 one is the first truly rejected block that I've seen and I can't say who forged it ( I cannot retrace it), even if it makes sense to think that it could be that pool...


  • admin

    @Dario's-wallet Therefore is said check/fix ... lot of new miners ... all we can do i pulling this topic up again and again until the right ones notice their problem 🙂 After all, blocks out of the future will not be accepted ...



  • This post is deleted!

  • admin

    @Dario-s-wallet Thanks for your research ... @PingOfd3ath Thanks for fixing ... i did not receive any rejected block for last 24h ...



  • This post is deleted!


  • This post is deleted!


  • @luxe @PingOfd3ath Always glad to help :):)
    @PingOfd3ath Good job! Good luck for your pool!
    I also would like to thank @luxe for this thread:)