Author Topic: What the Fork??  (Read 3938 times)

0 Members and 1 Guest are viewing this topic.

Offline Marco

  • Newbie
  • *
  • Posts: 1
    • View Profile
My client is not synching any longer. Missed a bunch of blocks a couple of hours ago and it is in limbo.
It seems to not count the 30 odd blocks that the client missed. Last block before it started missing blocks was 554889 and after 30 odd missed blocks it got block 554890.
After this no more synching...

Deleting the node_config.json file does not help.
Has anybody found a way to get the client synching again.
I am on the latest client version. Thx.

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
After dilation...

win7/32bit    if this matters.

Code: [Select]
>> get_info

{
  "blockchain_head_block_num": 555302,
  "blockchain_head_block_age": "6 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T21:35:00",
  "blockchain_average_delegate_participation": "59.76 %",
  "blockchain_confirmation_requirement": 50,
  "blockchain_delegate_pay_rate": "2.19326 BTSX",
  "blockchain_share_supply": "2,000,000,006.04770 BTSX",
  "blockchain_blocks_left_in_round": 97,
  "blockchain_next_round_time": "at least 16 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-22T21:57:00",
  "blockchain_random_seed": "3fec7728c2a94f0a0d10e75e7b572393280acbad",
  "client_data_dir": "C:/Users/Toni/AppData/Roaming/BITSHA~1",
  "client_version": "v0.4.16",
  "network_num_connections": 14,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T21:40:50",
  "ntp_time_error": 2.0256059999999998,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2014-10-04T10:08:52",
  "wallet_last_scanned_block_timestamp": "2014-09-22T21:35:00",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

Will limit the max connections to 8. This never happened to me before when the default was 8 connections.
{UPDATE} Setting the max to 7 connections reproduced the issue (after restart) in less then 15min.

Code: [Select]
>> get_info

{
  "blockchain_head_block_num": 555441,
  "blockchain_head_block_age": "6 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T21:55:50",
  "blockchain_average_delegate_participation": "71.63 %",
« Last Edit: September 22, 2014, 10:02:30 pm by tonyk »
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
Code: [Select]
>> get_info

{
  "blockchain_head_block_num": 554852,
  "blockchain_head_block_age": "6 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T20:10:50",
  "blockchain_average_delegate_participation": "74.26 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.20136 BTSX",
  "blockchain_share_supply": "2,000,187,518.50463 BTSX",
  "blockchain_blocks_left_in_round": 42,
  "blockchain_next_round_time": "at least 7 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-22T20:23:40",
  "blockchain_random_seed": "cca1278fda16821b701399d4b061a331c259008d",
  "client_data_dir": "C:/Users/Toni/AppData/Roaming/BITSHA~1",
  "client_version": "v0.4.16",
  "network_num_connections": 14,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T20:16:42",
  "ntp_time_error": 1.9602310000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2014-10-04T08:49:10",
  "wallet_last_scanned_block_timestamp": "2014-09-22T20:10:50",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

Deleted.
« Last Edit: September 22, 2014, 08:22:50 pm by tonyk »
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline Riverhead



Can you try deleting the node_config.json in your data directory for that client and see if the problem goes away? I want to check if it's this issue: https://github.com/BitShares/bitshares_toolkit/issues/794

Deleted.


Offline CalabiYau

Code: [Select]
       552367
     2c084d3ebd8bbfdbdfdbd7bf8785d3c83778af4e              a.delegate.xeroc              0       166 2014-09-22T13:12:40         0     YES                 YES
     b7c66ee7c18d952c2243e7254265b12e28bb6b3f               anchor.crazybit              0       166 2014-09-22T13:14:20         0     N/A                  NO
         552563
     eae05293ddcb22a2cef8b1e196fe646f69c99441                 delegate.adam              0       166 2014-09-22T13:45:40         0     YES                 YES
     422b027cf7424c9e08c7b9aef35dc79522eddec5                   dc-delegate             13      2344 2014-09-22T13:59:40         1     N/A                  NO
         553071
     f83e68347c0cbc04270023632ad3364acfa831ba                      crazybit              1       410 2014-09-22T15:11:10         1     YES                 YES
     67036b28d3890e11c18b096e1d4b0016d90adf01              delegate.cgafeng              1       410 2014-09-22T15:12:00         0     N/A                  NO
         553310
     0c0b4b133d29340801c1a10dc1950d1127d8b014                     calabiyau              8      9577 2014-09-22T16:03:40         0     N/A                  NO
     da5e0d99b7dbff3524ba6244b0cac9ea8d24b465      delegate.nathanhourt.com              0       166 2014-09-22T15:51:20      1701     YES                 YES

for the second time in 24 hours the delegate client lost the chain and was missing a block.
Deleted  node_config.json and restart.
Watching.

Offline dannotestein

  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Thank you for the research, svk. That is an interesting point as a few times I have found that on another wallet (where I'm playing with bots) I sometimes see that my client is five to 10 minutes behind.

So I guess the next question is....why is my client experiencing these stoppages in block syncing? I wonder if there's enough information in the logs to correlate connection count and the missing blocks.

Experiencing similar things since some delegates upgraded to 0.4.16 (cr1/2) with my non delegate client. My client was still on 0.4.15; Now with me on 0.4.16 I have seen this behavior 3 or 4 times. Restarting seems to fix the problem for me but then again it is easy when one is not delegate... Will post more info the next time this happens...will be good if somebody points me to what info will be helpful.
My initial post/info: https://bitsharestalk.org/index.php?topic=9099.msg118456#msg118456

I can confirm that since upgrading to 0.4.16 my delegate has missed blocks.
My non-delegate client (also running 0.4.16) stopped syncing.
Code: [Select]
   "blockchain_head_block_age": "5 hours old",
   "client_version": "v0.4.16",
   "network_num_connections": 5,

Restarted the non-delegate client and it made some progress but stopped syncing again

Code: [Select]
  "blockchain_head_block_num": 552498,
  "blockchain_head_block_age": "22 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T13:34:40",
  "client_version": "v0.4.16",
  "network_num_connections": 14,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T13:57:02",
  "ntp_time_error": -0.024471,
Can you try deleting the node_config.json in your data directory for that client and see if the problem goes away? I want to check if it's this issue: https://github.com/BitShares/bitshares_toolkit/issues/794
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline bitder

  • Full Member
  • ***
  • Posts: 65
    • View Profile
Thank you for the research, svk. That is an interesting point as a few times I have found that on another wallet (where I'm playing with bots) I sometimes see that my client is five to 10 minutes behind.

So I guess the next question is....why is my client experiencing these stoppages in block syncing? I wonder if there's enough information in the logs to correlate connection count and the missing blocks.

Experiencing similar things since some delegates upgraded to 0.4.16 (cr1/2) with my non delegate client. My client was still on 0.4.15; Now with me on 0.4.16 I have seen this behavior 3 or 4 times. Restarting seems to fix the problem for me but then again it is easy when one is not delegate... Will post more info the next time this happens...will be good if somebody points me to what info will be helpful.
My initial post/info: https://bitsharestalk.org/index.php?topic=9099.msg118456#msg118456

I can confirm that since upgrading to 0.4.16 my delegate has missed blocks.
My non-delegate client (also running 0.4.16) stopped syncing.
Code: [Select]
   "blockchain_head_block_age": "5 hours old",
   "client_version": "v0.4.16",
   "network_num_connections": 5,

Restarted the non-delegate client and it made some progress but stopped syncing again

Code: [Select]
  "blockchain_head_block_num": 552498,
  "blockchain_head_block_age": "22 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T13:34:40",
  "client_version": "v0.4.16",
  "network_num_connections": 14,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T13:57:02",
  "ntp_time_error": -0.024471,

Restarted my non-delegate client again and it caught up.
wallet_account_set_approval delegate.bitder 1

Offline bitder

  • Full Member
  • ***
  • Posts: 65
    • View Profile
Thank you for the research, svk. That is an interesting point as a few times I have found that on another wallet (where I'm playing with bots) I sometimes see that my client is five to 10 minutes behind.

So I guess the next question is....why is my client experiencing these stoppages in block syncing? I wonder if there's enough information in the logs to correlate connection count and the missing blocks.

Experiencing similar things since some delegates upgraded to 0.4.16 (cr1/2) with my non delegate client. My client was still on 0.4.15; Now with me on 0.4.16 I have seen this behavior 3 or 4 times. Restarting seems to fix the problem for me but then again it is easy when one is not delegate... Will post more info the next time this happens...will be good if somebody points me to what info will be helpful.
My initial post/info: https://bitsharestalk.org/index.php?topic=9099.msg118456#msg118456

I can confirm that since upgrading to 0.4.16 my delegate has missed blocks.
My non-delegate client (also running 0.4.16) stopped syncing.
Code: [Select]
   "blockchain_head_block_age": "5 hours old",
   "client_version": "v0.4.16",
   "network_num_connections": 5,

Restarted the non-delegate client and it made some progress but stopped syncing again

Code: [Select]
  "blockchain_head_block_num": 552498,
  "blockchain_head_block_age": "22 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T13:34:40",
  "client_version": "v0.4.16",
  "network_num_connections": 14,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T13:57:02",
  "ntp_time_error": -0.024471,
wallet_account_set_approval delegate.bitder 1

Offline svk

I meant to say I missed blocks when I set it to true, sorry about that. It's when you're blocking incoming connections that you end up losing connections and getting out of sync.
Worker: dev.bitsharesblocks

Offline Riverhead

Just caught this. Restarted and didn't miss a block. I'll have to keep an eye on it until we figure out what's going on.

"blockchain_head_block_age": "14 minutes old",

Code: [Select]
info
{
  "blockchain_head_block_num": 552313,
  "blockchain_head_block_age": "14 minutes old",
  "blockchain_head_block_timestamp": "2014-09-22T13:03:30",
  "blockchain_average_delegate_participation": "55.19 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "2.23912 BTSX",
  "blockchain_share_supply": "1,999,861,866.73016 BTSX",
  "blockchain_blocks_left_in_round": 56,
  "blockchain_next_round_time": "at least 9 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-22T13:26:30",
  "blockchain_random_seed": "61c71a80b3c2f54aedc92f0c72c8f321352fcd0b",
  "client_data_dir": "/home/riverhead/.delegate_0.4.16",
  "client_version": "v0.4.16",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-22T13:17:16",
  "ntp_time_error": -0.022846000000000002,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "3 years 2 months in the future",
  "wallet_unlocked_until_timestamp": "2017-11-22T22:50:43",
  "wallet_last_scanned_block_timestamp": "2014-07-21T07:02:30",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 9 minutes in the future",
  "wallet_next_block_production_timestamp": "2014-09-22T13:33:50"
« Last Edit: September 22, 2014, 01:25:03 pm by Riverhead »

Offline Riverhead

I am running with it that way; but I always have been (it's behind a strict firewall). Perhaps things have changes. I'll try it with that flag set to true and see what happens.

Update: it is set to true...must have missed that in an upgrade. Anyway, I get this at start which looks normal.

Code: [Select]
./run_delegate.sh
Loading blockchain from: .delegate_0.4.16/chain
Loading config from file: .delegate_0.4.16/config.json
Starting JSON RPC server on port 49333 (localhost only)
Starting HTTP JSON RPC server on port 1579 (localhost only)
UPnP: ExternalIPAddress = xxx.xxx.xxx.xxx
UPnP Port Mapping successful
« Last Edit: September 22, 2014, 01:05:28 pm by Riverhead »

Offline svk

Just thought of something, are you running your client with "--accept-incoming-connections false"? That's how I missed blocks last time, after a certain time you start losing connections and your client gets out of sync. That doesn't explain the latency though..
Worker: dev.bitsharesblocks

Offline Riverhead

Thanks tonyk, glad I'm not alone on this. The reason I noticed it with my bots is that they would a long time without a price update. When I checked the wallet I noticed it was minutes behind. A restart fixed it then as well. However, it seems the client does eventually catch up on its own.

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
Thank you for the research, svk. That is an interesting point as a few times I have found that on another wallet (where I'm playing with bots) I sometimes see that my client is five to 10 minutes behind.

So I guess the next question is....why is my client experiencing these stoppages in block syncing? I wonder if there's enough information in the logs to correlate connection count and the missing blocks.

Experiencing similar things since some delegates upgraded to 0.4.16 (cr1/2) with my non delegate client. My client was still on 0.4.15; Now with me on 0.4.16 I have seen this behavior 3 or 4 times. Restarting seems to fix the problem for me but then again it is easy when one is not delegate... Will post more info the next time this happens...will be good if somebody points me to what info will be helpful.
My initial post/info: https://bitsharestalk.org/index.php?topic=9099.msg118456#msg118456
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline Riverhead

Thank you for the research, svk. That is an interesting point as a few times I have found that on another wallet (where I'm playing with bots) I sometimes see that my client is five to 10 minutes behind.

So I guess the next question is....why is my client experiencing these stoppages in block syncing? I wonder if there's enough information in the logs to correlate connection count and the missing blocks.