Author Topic: Delegates, please make sure you upgrade to 0.4.8 version  (Read 8829 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

My client for the website is stuck as well at block 317208, trying to rebuild the index..

We are looking into these stuck blocks as our next high priority issue... the blockchain shouldn't get stuck on these forks.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline svk

My client for the website is stuck as well at block 317208, trying to rebuild the index..
Worker: dev.bitsharesblocks

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I've updated and delegates are working properly.
However seed node was stuck synchronizing.
Chain server didn't help at all.
I'm showing the logs:
Code: [Select]
Starting fast-sync of blocks from 316927
Finished fast-syncing 0 blocks at 0.000000000000 blocks/sec.
Listening for P2P connections on port 42577
Attempting to connect to peer 178.62.50.61:1776
Attempting to connect to peer 178.62.50.61:1777
Attempting to connect to peer 178.62.50.61:1778
Attempting to connect to peer 80.240.133.79:1776
Attempting to connect to peer 80.240.133.79:1777
Attempting to connect to peer 5.101.106.138:1777
Attempting to connect to peer 5.101.106.138:1778
Attempting to connect to peer 128.199.137.122:1776
Attempting to connect to peer 128.199.137.122:1777
Attempting to connect to peer 95.85.33.16:8764
Attempting to connect to peer 180.153.142.120:1777
Attempting to connect to peer 84.238.140.192:42577
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 316926,
  "blockchain_head_block_age": "39 minutes old",
  "blockchain_head_block_timestamp": "2014-08-25T23:44:20",
  "blockchain_average_delegate_participation": "29.53 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,960.26492 BTSX",
  "blockchain_delegate_pay_rate": "1.40509 BTSX",
  "blockchain_share_supply": "1,999,936,714.40159 BTSX",
  "blockchain_blocks_left_in_round": 12,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:25:40",
  "blockchain_random_seed": "c236f0bdeb181574bbc6f15b76e4e6ac40ebf95f",
  "client_version": "0.4.8",
  "network_num_connections": 3,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:23:40",
  "ntp_time_error": -0.0024220000000000001,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 7449 blocks left to fetch
--- there are now 5 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
--- there are now 5 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 316926,
  "blockchain_head_block_age": "40 minutes old",
  "blockchain_head_block_timestamp": "2014-08-25T23:44:20",
  "blockchain_average_delegate_participation": "29.36 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,960.26492 BTSX",
  "blockchain_delegate_pay_rate": "1.40509 BTSX",
  "blockchain_share_supply": "1,999,936,714.40159 BTSX",
  "blockchain_blocks_left_in_round": 12,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:26:00",
  "blockchain_random_seed": "c236f0bdeb181574bbc6f15b76e4e6ac40ebf95f",

  "client_version": "0.4.8",
  "network_num_connections": 5,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:24:01",
  "ntp_time_error": -0.0024229999999999998,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

I'm now trying --resync-blockchain.... Didn't help.

UPDATE:
I'm trying to sync only with the delegate now... Its OK now.

UPDATE:
I've copied the synchronized data dir from my delegate to the seed node.
It stuck again few blocks after...
Dont know what else I can do about that.

UPDATE:
Copied chain folder from delegate again. It is synchronized ... for now.
« Last Edit: August 26, 2014, 12:59:55 am by emski »

Offline Riverhead

Code: [Select]

  "blockchain_head_block_num": 317148,
  "blockchain_head_block_age": "4 seconds old",
  "blockchain_head_block_timestamp": "2014-08-26T00:24:50",
  "blockchain_average_delegate_participation": "93.52 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "169,735.07740 BTSX",
  "blockchain_delegate_pay_rate": "1.40323 BTSX",
  "blockchain_share_supply": "1,999,936,650.66592 BTSX",
  "blockchain_blocks_left_in_round": 93,
  "blockchain_next_round_time": "at least 15 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-26T00:40:20",
  "blockchain_random_seed": "a3d67ecf082d8150902f1db110d58959dcab04e4",
  "client_data_dir": "/home/riverhead/.BitSharesX",
  "client_version": "0.4.8",
  "network_num_connections": 18,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-26T00:24:54",

Offline svk

Looks good to me, mine's the same.

Code: [Select]
{
  "bitshares_toolkit_revision": "f9612af57c24b5831936bbd2c7d155d4eb2d8af8",
  "bitshares_toolkit_revision_age": "73 minutes ago",
  "fc_revision": "198d858d590f9f968f554a6036275cbbd7f78907",
  "fc_revision_age": "30 hours ago",
  "compile_date": "compiled on Aug 25 2014 at 19:48:47"
}
Worker: dev.bitsharesblocks

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
spartako,spartako1,spartako2 upgraded and running
wallet_account_set_approval spartako

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Code: [Select]
wallet (unlocked) >>> about
{
  "bitshares_toolkit_revision": "f9612af57c24b5831936bbd2c7d155d4eb2d8af8",
  "bitshares_toolkit_revision_age": "70 minutes ago",
  "fc_revision": "198d858d590f9f968f554a6036275cbbd7f78907",
  "fc_revision_age": "30 hours ago",
  "compile_date": "compiled on Aug 25 2014 at 19:45:48"
}
wallet (unlocked) >>>
 

Is what I get.  Is that the correct toolkit and fc revision?
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads