Author Topic: Dry Run 9: [Block]Chain Hang Low (featuring guest performer: ~~BitUSD~~)  (Read 25621 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

It is also apparent that I have the quote/base system all turned around in my head because I was thinking in MATH terms. 

When I see   USD / XTS  I *think*  USD per XTS and not USD priced in XTS; however, upon reviewing bter they list BTSX/BTC as BTCX priced in BTC and BTSX per BTC.  This is further complicated by the fact that i think "BASE" as the bottom half of a fraction and "QUOTE" as what you get when you  divide    100 XTS  *  5 USD / XTS => 500 USD. 

I am going to do a quick review of all code and make sure that we have our terminology correct.   

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 bytemaster

Code: [Select]
asset addition overflowed  {"amount":5837168575529231657,"asset_id":0} + {"amount":5837448775871972696,"asset_id":0} = {"amount":-6772126722308347263,"asset_id":0}
    {"a":{"amount":5837168575529231657,"asset_id":0},"b":{"amount":5837448775871972696,"asset_id":0},"c":{"amount":-6772126722308347263,"asset_id":0}}
    th_a  asset.cpp:29 operator+=

    {"quote_id":22,"base_id":0}
    th_a  chain_database.cpp:294 execute

    {}

This is the reason why the server is hung, every time the order matching attempts to execute we get this bug.  This is triggered by alts transactions that are creating an ungodly amount of USD by manipulating the ratios in a thin market.   I need to review his transaction history and put in guards that protect the block processing even if market operations fail.
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 toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
I think these are legitimate forks caused by broken market functionality... the seed nodes are all stuck as well.

I'm gonna lock this until we figure it out (tomorrow).
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline Fox

I believe the seed node(s) are not functioning properly. 

I have read many reports of stuck at 1034 and 2071.  I too cannot get a fresh client to sync properly with the network.  My latest attempt was to force my client to connect to a single seed node.  Here is the output:
Code: [Select]
2:~/bitshares_toolkit/programs/client$ ./bitshares_client --p2p-port 8902 --max-connections 1 --clear-peer-database --resync-blockchain --connect-to 107.170.30.182:8903 --disable-default-peers --disable-peer-advertising
Deleting old copy of the blockchain in "/home/XTSAdmin/.BitSharesXTS/chain"
Loading config "/home/XTSAdmin/.BitSharesXTS/config.json"
Initializing genesis state from built-in genesis file
Please be patient, this could take a few minutes.
Successfully re-indexed 0 blocks in 0 seconds.
Not starting RPC server, use --server to enable the RPC interface
Attempting to map P2P port 8902 with UPNP...
Erasing old peer database
Listening for P2P connections on port 8902
Attempting to connect to peer 107.170.30.182:8903
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 2271 blocks left to fetch
--- syncing with p2p network, our last block was created 7 hours ago
--- syncing with p2p network, our last block was created 6 hours ago
--- syncing with p2p network, our last block was created 5 hours ago
I am disconnecting peer 107.170.30.182:8903 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1236 blocks left to fetch
(wallet closed) >>>

Note: the client first tells us there are 2271 blocks to fetch. 
Note: the client is disconnected at block 1034, reconnects and looks for the 1236 blocks to fetch, but fails to do so. 

Code: [Select]
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
  "fc_revision_age": "16 hours ago",
  "compile_date": "compiled on Jul 16 2014 at 03:06:57"
}
(wallet closed) >>> config
{
  "blockchain_id": "4b9f25c5e7204fd2af460d7a63fad3ce758e873ade2679c6ac14cfb62d4f05a7"
  ...
}

Does anyone have a peer node IP:PORT properly synced beyond block 2071 that I may connect to?
Witness: fox

Offline Harvey

  • Sr. Member
  • ****
  • Posts: 244
    • View Profile
Wait for 10 hours, still stuck at block 888.

Code: [Select]
(wallet closed) >>> getinfo
{
  "blockchain_head_block_num": 888,
  "blockchain_head_block_age": "10 hours old",
  "blockchain_head_block_timestamp": "20140715T191420",
  "blockchain_average_delegate_participation": 2.8378758078111828,
  "blockchain_delegate_pay_rate": 30136187,
  "blockchain_blocks_left_in_round": 21,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199996956227035,
  "blockchain_random_seed": "5f626e10fdc76cf6e2e310a5b95b88f3d8b49ce7",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 4,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": null,
  "ntp_error": null,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:wss://128.199.143.47:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:ws://128.199.143.47:2018

lzr1900

  • Guest
stuck at block 2271

Code: [Select]

(wallet closed) >>> getinfo
{
  "blockchain_head_block_num": 2271,
  "blockchain_head_block_age": "89 minutes old",
  "blockchain_head_block_timestamp": "20140716T030500",
  "blockchain_average_delegate_participation": 15.855572998430141,
  "blockchain_delegate_pay_rate": 58,
  "blockchain_blocks_left_in_round": 52,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199999992930142,
  "blockchain_random_seed": "1b7bd524049868fe753fd7c89c551b85b14f5327",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 8,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140716T043352",
  "ntp_error": -0.026741999999999998,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}

me too

clout

  • Guest
stuck at block 2271

Code: [Select]

(wallet closed) >>> getinfo
{
  "blockchain_head_block_num": 2271,
  "blockchain_head_block_age": "89 minutes old",
  "blockchain_head_block_timestamp": "20140716T030500",
  "blockchain_average_delegate_participation": 15.855572998430141,
  "blockchain_delegate_pay_rate": 58,
  "blockchain_blocks_left_in_round": 52,
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": 199999992930142,
  "blockchain_random_seed": "1b7bd524049868fe753fd7c89c551b85b14f5327",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 8,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140716T043352",
  "ntp_error": -0.026741999999999998,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}


Offline yellowecho

BitSharesXT quit unexpectedly.

I'm not able to load the client.  It quits before opening.
696c6f766562726f776e696573

Xeldal

  • Guest
For continuity, you might switch the order of <quote_symbol> and <base_symbol> of the following 2 commands
Quote
blockchain_market_list_asks <quote_symbol> <base_symbol> [limit]
blockchain_market_list_bids <quote_symbol> <base_symbol> [limit]

The base always come first in a pair and the quote second

XTS/USD currently translates to blockchain_market_list_bids USD XTS (which is backwards)

and should be similar to the order for the command
Quote
wallet_market_submit_bid <from_account_name> <quantity> <quantity_symbol> <quote_price> <quote_symbol>
where <quantity> is your base

obviously this change would be purely cosmetic. 

Unfortunately in trading XTS/USD is used (reads "XTS priced in USD"),  and in math translates to USD/XTS (reads "USD per XTS").  So it's a little counter intuitive and often difficult when reading to figure out which is being referred to.

Offline laow

  • Full Member
  • ***
  • Posts: 155
    • View Profile
BTS acount: laow

Offline gordonhucn

  • Full Member
  • ***
  • Posts: 66
    • View Profile
some funds for testing please, thanks  :D
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb

Sent.

received and voted, thanks again.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
some funds for testing please, thanks  :D
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb

Sent.
>>> approve bitcoiners

Offline gordonhucn

  • Full Member
  • ***
  • Posts: 66
    • View Profile
some funds for testing please, thanks  :D
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
how did you work around with this problem?

stuck at block 1034 for 2 hours

Quote

tiger (unlocked) >>> info
{
  "blockchain_head_block_num": 1034,
  "blockchain_head_block_age": "2 hours old",
  "blockchain_head_block_timestamp": "20140715T233700",
  "blockchain_average_delegate_participation": 10.171198388721047,
  "blockchain_delegate_pay_rate": 18,
  "blockchain_blocks_left_in_round": 77,
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "21.89463 XTS",
  "blockchain_share_supply": 199999997792460,
  "blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 2,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140716T020335",
  "ntp_error": -0.014847000000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "20140727T154955",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}
tiger (unlocked) >>> info

Code: [Select]
tiger (unlocked) >>> about
{
  "bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
  "bitshares_toolkit_revision_age": "2 hours ago",
  "fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
  "fc_revision_age": "14 hours ago",
  "compile_date": "compiled on Jul 15 2014 at 21:41:11"
}
I guess it's not because of fork
It's because you missed block 1035.
I have meet this situation several times.
just waitting or restart.


来自我的 HUAWEI P7-L00 上的 Tapatalk


Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
how did you work around with this problem?

stuck at block 1034 for 2 hours

Quote

tiger (unlocked) >>> info
{
  "blockchain_head_block_num": 1034,
  "blockchain_head_block_age": "2 hours old",
  "blockchain_head_block_timestamp": "20140715T233700",
  "blockchain_average_delegate_participation": 10.171198388721047,
  "blockchain_delegate_pay_rate": 18,
  "blockchain_blocks_left_in_round": 77,
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "21.89463 XTS",
  "blockchain_share_supply": 199999997792460,
  "blockchain_random_seed": "57ba59f7a2ee52c976d3e0385d409c327d1d52f6",
  "blockchain_database_version": 114,
  "blockchain_version": 107,
  "network_num_connections": 2,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140716T020335",
  "ntp_error": -0.014847000000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "20140727T154955",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 100
}
tiger (unlocked) >>> info

Code: [Select]
tiger (unlocked) >>> about
{
  "bitshares_toolkit_revision": "23cd03536932cfbc081de47586316586c2fb16c4",
  "bitshares_toolkit_revision_age": "2 hours ago",
  "fc_revision": "06fe9e0303b10f8cd6ef6a8da506495e5b113c39",
  "fc_revision_age": "14 hours ago",
  "compile_date": "compiled on Jul 15 2014 at 21:41:11"
}
I guess it's not because of fork
It's because you missed block 1035.
I have meet this situation several times.
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students