Wallet 1.2.8, Error "Block not accepted", how to fix (using Linux) solved


  • admin

    @BurnMe said in Wallet 1.2.8, Error "Block not accepted", how to fix (using Linux) ?:

    ... why does the wallet then start on the wrong block (behind the actuall) ..

    I do not understand what you exactly mean, the wallet should start with the last valid block it got and than sync up to current. Pop off blocks should only be needed if your are on the wrong fork and you want to return to before the fork happens. To go back on right track ...

    ... do you think the CreepMiner gets stuck over the message. I made a chat with Creepsky but we couldn't find a real solution for this behaviour.

    I do not know how creepMiner is implemented ( @Creepsky ), but i guess the miner just requests the mining info from wallet and thats all ... so miner should never stuck ... if somethings stuck it would be the wallet.
    If you pop off blocks or restart the wallet or sync blockchain etc. always shut down miner before and re-start if wallet is fine and in sync again.

    Edit: if you system time was out of sync due to your router ... that would explain all your issues. As you would have rejected legit blocks all the time.



  • @LithStud said in Wallet 1.2.8, Error "Block not accepted", how to fix (using Linux) ?:

    @BurnMe thanks for troubleshooting this (since majority of people using windows there aint that many who could advice about linux).

    @luxe @IceBurst @daWallet someone should know who is working with core and if this is something known/solved ;)

    It's not an issue we are addressing, actually its not something we could fix unless we force NTP syncs at the start of the wallet (feature enhancement). @Luxe is right, it's just information that your system rejected a block that was sent by another peer because of an invalid time stamp, normally it's from someone who has their clock ahead in time and your wallet think the block is from the future.

    As for core development there will be no feature enhancements by the current unless something changes. I have been black listed from the holder of the account and the others have not been paid as I requested.

    Sorry I can't be of more help,

    -IceBurst



  • @IceBurst no problem :) i mostly mentioned all the people since as i understood his client would get stuck anytime that message is show (i do know of instances when API gets stuck up to the point where client reports error 500 couldnt send response).



  • @luxe

    ... why does the wallet then start on the wrong block (behind the actuall) ..

    I mean that when the message block not accepted the Miner stops mining without any message. I tell you step by step what happend and what i mean at all.

    1. Step
      The message "Block not accepted" appears on the wallet terminal

    2.Step
    At exact the time the message "Block not accepted" is appearing the miner get stuck and stop mining without any message or error log

    3.Step
    I shut down the miner by ctrl +c

    1. Step
      I shut down the wallet by ctrl +c

    2. Step
      I restart the wallet

    6.Step
    i restart the miner

    7.Step
    The miner starts without problems but its mining on the wrong block. The block is far behind the actuell block and i don't know why.

    8.Step
    Restarting the miner and the wallet doesn't have any effect. The miner starts always with the wrong block. And even it's always the same block.

    9.Step
    Made pop off some block. Then restart wallet and miner and then the miner the first time is starting again with the right block.

    10.Step
    I know that the blockchain needs time to get in sync but after the message block not accepted i could wait for hours and the miner starts on the block behind, so this is not the solution.


  • admin

    @BurnMe
    I have no experience with creepMiner, how do you know it get stuck? ... it will only do something once a new round starts.
    Did you see the wallet is behind actual block at all? Do not look at the logs of wallet, look into gui. And do not shut down wallet just because a few minutes no new block.
    Last thing i could suggest, forget about the miner. First get your wallet running ... maybe enable debug logs in wallet to find out what the issue is ... seams to have something to do with your environment. Once your wallet is running ... you can focus on miner ...


  • admin

    @IceBurst Glad i'm not part of that bn mess ... however, there is no official burst core dev team whatever ... clone, implement, release ... the ones running the nodes will decide witch development to follow ... i personally would run nothing bn involved ... Serious devs will follow the right clone ...

    Edit: if i say bn, i mainly talk about the ones making them self titles and behave like they are in any kind of leading position, while they are not.



  • @luxe said in Wallet 1.2.8, Error "Block not accepted", how to fix (using Linux) ?:

    @IceBurst Glad i'm not part of that bn mess ... however, there is no official burst core dev team whatever ... clone, implement, release ... the ones running the nodes will decide witch development to follow ... i personally would run nothing bn involved ...

    You are absolutely correct the community picks the current version through adoption. That's why we have never called ourselves the "official" anything. We call ourselves the Core Team as that is the project we are working on and for no other reason. The source is 100% open on GitHub which I feel is best for the community and the skeptics. Once it's completed anyone that would like to fork it into a repo is welcome to. I was not the originator of the GitHub host.

    -IceBurst


  • admin

    @IceBurst Maybe this is a progress to form something sustainable ... but blacklisting devs that want to contribute, is a behaviour that tell me, that there are people involved that are not helpful and need to be left behind.

    @BurnMe Sorry for leaving the topic of this thread ... just needed to respond to that.



  • @luxe its ok to leave the topic. I am learning every day more about burstcoin and the wallet.



  • @luxe

    Hi my wallet get stuck at Block 363935. I checked this in the gui like you said. So now the wallet get stuck again. Time setting on the Router didn't solved the problem :(.


  • admin

    @BurnMe said in Wallet 1.2.8, Error "Block not accepted", how to fix (using Linux) ?:

    Hi my wallet get stuck at Block 363935

    How do you determine that it is stuck?



  • @luxe Hi, every time the miner starts at 363935 and in the gui of the wallet for hours the last block height is shown with 363935 without changing. This is why I'm thinking that it gets stuck. I determine stuck that its alway on the same Block without changing. Perhaps i should use not the word stuck and just say that the wallet is always on the same block.

    But when you have another technical advice or explanation then let me know.

    I will use another Router the next time for testing. I let you know what happens with another Router.

    And I will try to install the jminer to change the software.

    By the way pool mining is stable for days with the CreepMiner. There is no error, no stuck just mining without any problems. The only thing that has been changed from pool to solo mining is that I'm using the local wallet. My PC setup is exactly the same. So on the Hardware side there is for me no explanation for this behavior when pool mining is running without any problems.

    When all this is not working i say goodby to Linux and go back to WIndows.


  • admin

    This post is deleted!


  • @luxe
    Hi,

    it tried mining on windows 7 too with the actual AIO. Its the same issue like in Linux. The local wallet is far behinf the online wallet. I made two screenshots (at nearly the same time at 19:35 local time). You can see that the local wallet is on Block 364187 (and it shows 16:01, but this was not my actual local time, my local time was 19:35 during making this screenshot) and at the same time the online wallet is on 364236.

    When it start the AIO miner on solo mining the miner starts at 364188 (the wrong block). When im starting pool mining you can see thats its starting with the right block.

    So whats going on with the local wallet ? The blockchain sync and updating has been done. When logging in the local wallet there is no more blockchain downloading visible.

    What to do in windows to get the local wallet on the right block. On Linux i made some pop off, but in windows with the AIO i don't know how to configure.

    With windoes its even getting more complex than with Linux. With Windows solo mining has never been working.

    There is something with my setting or the wallet thats causes my issue, but i don't know why my setting should make this strange behavior. Why is local wallet not working. If somebody have more advices for my setting then let me know.



  • @BurnMe it takes time to sync the local wallet. what you see in wallets blocks is the ones that been mined so miner will always be 1 ahead of wallet.



  • @LithStud Yes i know, but the local wallet is a lot more than 1 ahead. The local Wallet is 49 behind the online wallet.



  • @BurnMe as i said it will take some time to sync, just wait (from time to time recent blocks will update)



  • @LithStud Ok i am waiting the next hours. But how is it possible for me to see when sync is done. Actual there is no hint that the local wallet is syncing.

    How to set a burst server in Local Wallet with AIO ? In Linux i have to set nxtAdress=XXX but where to set this in Windows ?

    Thanks for all help and answering my newbie questions and for your patience with me.

    Ok forget my second question i found the config file in windows 7 :)



  • @BurnMe i dont use AIO so cant say where the files are kept, but it is the same as linux you edit config file for local wallet.

    On wallet UI there sometimes is show loading bar at bottom right corner (and at top green notification about blockchain downloading). It is not perfect as i am not sure when it decides to hide those indicators. If indicators are not visible UI updates blocks every 30s (client itself is syncing in background so its just that visuals are affected)



  • Hi, the new CreepMiner Version (development branch) is solving all my problems. No more block not accepted messages.
    Problems solved.


Log in to reply
 

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