Author Topic: Anyone else's delegates missing blocks unexpectedly?  (Read 2765 times)

0 Members and 1 Guest are viewing this topic.

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
v0.4.17-RC1 fixed the issue for me.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.


Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

There's definitely something wrong with the networking code with 0.4.16
I left my non-delegate client (CLI) running after upgrading to 0.4.16 and it has stopped syncing multiple times now.
It requires one or more restarts of the client for it to sync again.

I have the same problem with v0.4.17-RC1 !!!

Offline amencon

  • Sr. Member
  • ****
  • Posts: 227
    • View Profile
My delegate also mysteriously missed a couple chunks of blocks while I was sleeping last night.  The connection was fine and it started producing on main chain again on it's own so I'm not sure what the problem was exactly.

Offline eagleeye

  • Hero Member
  • *****
  • Posts: 931
    • View Profile
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

There's definitely something wrong with the networking code with 0.4.16
I left my non-delegate client (CLI) running after upgrading to 0.4.16 and it has stopped syncing multiple times now.
It requires one or more restarts of the client for it to sync again.

Hey bitder, sign up to www.beyondbitcoinx.net to say what your delegate policies are.

Offline bitder

  • Full Member
  • ***
  • Posts: 65
    • View Profile
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

There's definitely something wrong with the networking code with 0.4.16
I left my non-delegate client (CLI) running after upgrading to 0.4.16 and it has stopped syncing multiple times now.
It requires one or more restarts of the client for it to sync again.
wallet_account_set_approval delegate.bitder 1

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I experienced something very strange.
Although I had perfect internet connection my delegates end up on a fork.
They didn't synchronize until I've restarted the client.
This never happened before.

Offline Riverhead

I am experiencing that as well. It seems that the client goes through periods of being a few minutes behind. If one of these lags happens during your slot you miss those blocks.

Check out this thread: https://bitsharestalk.org/index.php?topic=9195.msg118971#msg118971

Offline nethyb

  • Full Member
  • ***
  • Posts: 197
    • View Profile
  • BitShares: nethyb
Both my delegates www.minebitshares-com and www2.minebitshares-com have missed blocks yesterday/today without explanation for the first time.

They both run on Amazon AWS instances (Ireland and Sydney) and nothing has changed apart from upgrading to 0.4.16   :'(

I know delegate.liondani has also had similar issues.

Anyone else experience missing blocks for the first time, or have any troubleshooting tips?