Something i miss in wallet version 1.2.7?



  • Miner works fine with no errors. Network is stable. Maybe i switch back to 1.2.6 and give it a try if there is no other way. :)



  • @piezo
    first thing I'd do is check for Network or Pool issues
    could you start jminer not from whithin the wallet and post the output?!
    what you posted is only the wallet starting up and unrelated to the miner.

    or just the jminer log file if you have it configured to make one. (search for "not confirmed" or "error 1007")



  • @piezo Yes you were right. Every time I change to 1.2.7 i'm block less. Every time I go back to 1.2.6 its great however its been forking twice this past week. At some point we need to update as the network has. The longer you run your plotted drive the better your plot times will get. You'll see.



  • @piezo sorry, just saw that your solo mining! but still, logs with your password removed would be much more helpful.
    also check if your wallet is not forked! (just compare the current Block number with one or two pools)



  • @nixxda

    I check the logfiles for the jminer. Found no Errors so far and all deadlines get confirmed.
    Iam not on a Fork in the wallet and was at no time the last 9 days.

    But: Actually i hit one Block a few minutes ago.
    I hope this was only an example of really bad luck. If i didn´t hit another one the next 2-3 days i switch back to wallet version 1.2.6 . :)

    Here is (as you asked) an output-example for 1 Block...

    2016-12-07 21:59:25.190  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : START block '303502', scoopNumber '3858', capacity '43069 GB'
    2016-12-07 21:59:25.190 DEBUG 8165 --- [        Timer-1] burstcoin.jminer.core.round.Round        : trigger garbage collection ... 
    2016-12-07 21:59:25.190  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       :       targetDeadline '50000', baseTarget '1735676'
    2016-12-07 21:59:25.193  INFO 8165 --- [  networkPool-1] burstcoin.jminer.JMinerCommandLine       :       winner block '303501', 'BURST-MVSE-LLUM-6NW4-7JMXZ'
    2016-12-07 21:59:25.323  INFO 8165 --- [readerPool-1384] burstcoin.jminer.JMinerCommandLine       : 1% done (0TB 5GB), avg.'44 MB/s'
    2016-12-07 21:59:25.326  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '3516650582' > '50000' skipped
    2016-12-07 21:59:25.334  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '381802021' > '50000' skipped
    2016-12-07 21:59:25.338  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '25399760' > '50000' skipped
    2016-12-07 21:59:25.387  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '19285954' > '50000' skipped
    2016-12-07 21:59:25.411  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '2299246' > '50000' skipped
    2016-12-07 21:59:25.921  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '1232996' > '50000' skipped
    2016-12-07 21:59:25.925  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '127686' > '50000' skipped
    2016-12-07 21:59:26.865  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : dl '9111' send (solo)
    2016-12-07 21:59:27.077  INFO 8165 --- [  networkPool-1] burstcoin.jminer.JMinerCommandLine       : dl '9111' confirmed!  [ 0d 2h 31m 51s ]
    2016-12-07 21:59:29.035  INFO 8165 --- [readerPool-1391] burstcoin.jminer.JMinerCommandLine       : 21% done (8TB 617GB), avg.'544 MB/s', eff.'548 MB/s'
    2016-12-07 21:59:32.688  INFO 8165 --- [readerPool-1394] burstcoin.jminer.JMinerCommandLine       : 41% done (17TB 229GB), avg.'562 MB/s', eff.'582 MB/s'
    2016-12-07 21:59:36.519  INFO 8165 --- [readerPool-1392] burstcoin.jminer.JMinerCommandLine       : 61% done (25TB 853GB), avg.'558 MB/s', eff.'548 MB/s'
    2016-12-07 21:59:41.114  INFO 8165 --- [readerPool-1391] burstcoin.jminer.JMinerCommandLine       : 81% done (34TB 457GB), avg.'528 MB/s', eff.'457 MB/s'
    2016-12-07 21:59:51.055  INFO 8165 --- [readerPool-1389] burstcoin.jminer.JMinerCommandLine       : 100% done (43TB 69GB), avg.'406 MB/s', eff.'211 MB/s'
    2016-12-07 21:59:51.309  INFO 8165 --- [    roundPool-1] burstcoin.jminer.JMinerCommandLine       : FINISH block '303502', best deadline '9111', round time '25s 891ms'
    2016-12-07 21:59:52.059 DEBUG 8165 --- [        Timer-1] burstcoin.jminer.core.reader.Reader      : cleanup was successful ...
    2016-12-07 21:59:52.559 DEBUG 8165 --- [        Timer-1] burstcoin.jminer.core.round.Round        : trigger garbage collection ... 
    
    

    And for the startup...

    java -jar -d64 -XX:+UseG1GC burstcoin-jminer-0.4.5-RELEASE.jar |  tee  /dev/stderr  |  sed -nue 's/.*best deadline.*/jminer: &/p'  >>  /home/path/example/Coins/Burst/burst_miner/sharelog.txt
    22:17:59.544 [main] INFO burstcoin.jminer.JMinerApplication - Starting the engines ... please wait!
    2016-12-07 22:18:00.753  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    : -------------------------------------------------------
    2016-12-07 22:18:00.755  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    : List of system openCL platforms and devices (* = used for mining)
    2016-12-07 22:18:00.756  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    : 
    2016-12-07 22:18:00.760  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    :  * PLATFORM-[0] Intel(R) OpenCL - (OpenCL 2.0)
    2016-12-07 22:18:00.762  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    :  *   DEVICE-[0] Intel(R) HD Graphics (1GB) - Intel(R) Corporation (OpenCL 1.2 | 'r2.0.54425')
    2016-12-07 22:18:00.764  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    :  *          [0] work group size: '256', computing units: '48', available 'true'
    2016-12-07 22:18:00.765  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    :      DEVICE-[1] Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (2GB) - Intel(R) Corporation (OpenCL 2.0 (Build 10264) | '1.2.0.10264')
    2016-12-07 22:18:00.765  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    :             [1] work group size: '8192', computing units: '4', available 'true'
    2016-12-07 22:18:01.451  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    : 
    2016-12-07 22:18:01.451  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    : (*) openCL context successfully started! (platformId: 0, deviceId: 0)
    2016-12-07 22:18:01.451  INFO 17062 --- [           main] b.jminer.core.checker.util.OCLChecker    : -------------------------------------------------------
    2016-12-07 22:18:01.568  INFO 17062 --- [           main] burstcoin.jminer.core.CoreProperties     : Default 'http://localhost:8125' used for 'soloServer' property!
    2016-12-07 22:18:02.134  INFO 17062 --- [  networkPool-1] b.j.c.n.t.NetworkRequestLastWinnerTask   : Requesting mined blocks from wallet ...
    2016-12-07 22:18:02.283  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       : -------------------------------------------------------
    2016-12-07 22:18:02.283  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :                             Burstcoin (BURST)
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :             __         __   GPU assisted PoC-Miner
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :            |__| _____ |__| ____   ___________ 
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :    version |  |/     \|  |/    \_/ __ \_  __ \
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :      0.4.5 |  |  Y Y  \  |   |  \  ___/|  | \/
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :        /\__|  |__|_|  /__|___|  /\___  >__| 
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :        \______|     \/        \/     \/
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :       mining engine: BURST-LUXE-RED2-G6JW-H4HG5
    2016-12-07 22:18:02.284  INFO 17062 --- [           main] burstcoin.jminer.JMinerCommandLine       :      openCL checker: BURST-QHCJ-9HB5-PTGC-5Q8J9
    2016-12-07 22:18:02.431  INFO 17062 --- [  networkPool-1] b.j.c.n.t.NetworkRequestLastWinnerTask   : Total mined blocks: '150', received in '21' ms
    
    

    Thanks so far...


  • admin

    @piezo I see no reason, why it should be related to 1.2.7 ... however, it is strange if i view your stats ... must be very bad luck ...

    Not sure if it helps, but you could try increase 'nxt.maxNumberOfConnectedPublicPeers' to ensure your deadlines reach the network ... i had multiple times best deadline but someone else got the block ... i can not proof that not a disconnect or my vpn caused that, but sometimes i think some manipulated peers out there (ignoring / not propagating results of blacklisted accounts) ... But i'm a very paranoid person :-)



  • @luxe
    "Just because you're paranoid doesn't mean they aren't after you" :)


  • admin

    @piezo Yes Kurt :-) If such issue exists, there is only one solution ... we need more pool miners to run a node, even if they do not need it for mining ... but i really hope it was just bad luck ...



  • @piezo Is your time in sync?



  • @nixxda
    I checked it and noticed, that my system time was 3sec behind. Maybe this cause the problems?


  • admin

    @piezo
    Before you do anything, sync your clock. Burst uses your computer clock's time, and having the time off too much could cause you to reject legit blocks, or miss out on blocks you could have mined. On linux "sudo ntpd -gq", on windows go to change date/time, and go to internet time and tell it to sync with a time server.
    https://github.com/burst-team/burstcoin/blob/master/Readme.txt

    So yes, that could be a issue.

    I use http://www.timesynctool.com/


Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.