Dry Run 7: The Power of DPOS

[vikram]

It seems I lost 100 FREE.

I have issued 1M FREE, then I tried to send 100 FREE to demonstra but the transaction was pending for long time (more then 10 minutes) and I used the command wallet_clear_pending_transactions. So now I can't see the transaction any more but my balance it is not synced with my transactions:

Init balance: 1,000,0000 FREE

Code Select Expand


3411.11   2014-07-02T11:55:15 spartako-w          spartako-w          1.000000 FREE       0.10000 XTS                                                1b8b05d1
   3432.12   2014-07-02T12:01:00 spartako-w          demonstra           100.000000 FREE     0.10000 XTS                                                68a98a80
   3447.9    2014-07-02T12:05:30 spartako-w          bitdraw             100.000000 FREE     0.10000 XTS                                                30626c46


Finale balance: 999,700.000000 FREE but should be 999,800 FREE

I have made an issue: https://github.com/BitShares/bitshares_toolkit/issues/444

[lzr1900]

want some funds for testing purpose.thanks!!
lzr1900
XTS7XaDD7TB8CR5zoxuZmc2hPAaVD7ybE8knTW7CC2afdv99PEC29

[bennyliaa]

what is below error??

RPC Server Error
In method 'batch': 6 key_not_found_exception: Key Not Found unable to find key 539 {"key":539} bitshares level_map.hpp:74 bts::db::level_map::fetch error fetching key 539 {"key":539} bitshares level_map.hpp:84 bts::db::level_map::fetch {"block_num":539} bitshares chain_database.cpp:1109 bts::blockchain::chain_database::get_block_id {} bitshares common_api_client.cpp:339 bts::rpc_stubs::common_api_client (500)

[bennyliaa]

send me some funds please, Thanks.
XTS6fFRG8YePxSRwMNvvpQndEc7HqmxmcqmLvTsCn8J9F3vtMg5k4

[Webber]

Code Select Expand

ID    NAME                            APPROVAL         PRODUCED MISSED   RELIABILITY   PAY RATE PAY BALANCE     LAST BLOCK
366   clout-delegate2                 0.0075000283 %       0        18       0.00 %        50 %     0.00000 XTS     NONE
397   webber                          0.0025000094 %      0        7        0.00 %        100 %    0.00000 XTS     NONE


Whats going on guys?

I am also very confused.My server is in China,i guess is network problem in china.delay with us/eur more than 250ms.
How about somebody else's server in chian?

[betax]

- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)

same with me after first log-out

that means you must have it open all the time

but even that is not possible because the "Logout timeout, seconds" option on Preferences didnt't work !!!

so the client log automaticaly out even when you have updated to 6000 seconds....



PS only after I deleted directories:

1.chain
2.exceptions
3.peers.leveldb
(not wallets)

I could sign-in again

Yes same issue and solution, only problem is that by the time it syncs it locks again.

CPU is active 16 / 17 percent whilst spinning and trying to login, I guess this is due to the UI.

Other issues. Importing multibit wallet did not get any response.

When deleting chain and peers, I am able to see and navigate through the wallet before I get redirected to the logon screen.

[cass]

send me some funs for test,pls!
XTS7g35g4ZYA9NQ7xjpbXac6s7qogDPTRwbeg47XzeMyGKNp9skUL

sent

[kinglaw0577]

send me some funs for test,pls!
XTS7g35g4ZYA9NQ7xjpbXac6s7qogDPTRwbeg47XzeMyGKNp9skUL

[metalallen]

XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D

50 XTS on the way

XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D

Sent

Code Select Expand


  3921.0    2014-07-02T14:17:45 spartako-w          metalallen          100.00000 XTS       0.10000 XTS                                                e30da037
   3925.0    2014-07-02T14:18:45 spartako-w          metalallen          100.000000 FREE     0.10000 XTS                                                2e6cff90



XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D

111xts on the way

Got it! Thx guys~ +5%

[liondani]

- when i try to log in with my password i just see the rotating symbol but it doesnt log me in and goes on forever
(temporary issue)

same with me after first log-out

that means you must have it open all the time

but even that is not possible because the "Logout timeout, seconds" option on Preferences didnt't work !!!

so the client log automaticaly out even when you have updated to 6000 seconds....



PS only after I deleted directories:

1.chain        EDIT (only delete this folder and it schould be enough....)
2.exceptions
3.peers.leveldb
(not wallets)

I could sign-in again

[bytemaster]

I experienced the same problem many times from different dry run .  It always happened after many hours running and suddenly client stop synchronize with main chain and block number count stop . if I quit the client and re-run it following error will appear and client crashed

Code Select Expand


(wallet closed) >>> open doggy

Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=0x7ffff697e760 <main_arena>, bytes=128) at malloc.c:3302
3302    malloc.c: No such file or directory.
(gdb)

then I will reboot my linux box and delete the "peers.leveldb" folder and restart my client then client will restart but keeping on disconnecting form peer as I posted in my last post.

the only way for me to get back to normal is to delete all the /.BitSharesXTS folder and re-sync the block chain form beginning

more info below

Code Select Expand

doggy (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_age": "15 seconds old",
  "blockchain_head_block_timestamp": "20140702T132130",
  "blockchain_average_delegate_participation": 0,
  "blockchain_blocks_left_in_round": 101,
  "blockchain_confirmation_requirement": 202,
  "blockchain_share_supply": 199999999981923,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_database_version": 109,
  "blockchain_version": 104,
  "network_num_connections": 1,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140702T132145",
  "ntp_error": -0.0023029999999999999,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "77 days in the future",
  "wallet_unlocked_until_timestamp": "20140917T171137",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 101
}
--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>>
[detached from 1587.bts]
coins@coins:~$ ^C
coins@coins:~$ screen -r bts
I am disconnecting peer 107.170.30.182:8701 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, 1716 blocks left to fetch
--- there are now 2 active connections to the p2p network
I am disconnecting peer 107.170.90.142:8701 for reason: You offered us a block that we reject as invalid
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
I am disconnecting peer 84.238.140.192:36350 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39931 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.112:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.91.24:35790 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 114.215.104.153:36016 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, 1718 blocks left to fetch
I am disconnecting peer 176.9.234.167:39967 for reason: You offered us a block that we reject as invalid
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- syncing with p2p network, 1719 blocks left to fetch
--- there are now 4 active connections to the p2p network
--- there are now 5 active connections to the p2p network
--- there are now 6 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8703 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 107.170.170.214:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 162.243.160.72:46456 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 92.243.18.20:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 188.138.107.159:8701 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 128.199.180.19:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
I am disconnecting peer 146.185.186.245:54482 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.24.234:8701 for reason: You offered us a block that we reject as invalid
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1720 blocks left to fetch
I am disconnecting peer 176.9.234.167:39978 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
doggy (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_age": "18 seconds old",
  "blockchain_head_block_timestamp": "20140702T132445",
  "blockchain_average_delegate_participation": 0,
  "blockchain_blocks_left_in_round": 101,
  "blockchain_confirmation_requirement": 202,
  "blockchain_share_supply": 199999999981923,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_database_version": 109,
  "blockchain_version": 104,
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "ntp_time": "20140702T132503",
  "ntp_error": -0.0023029999999999999,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "77 days in the future",
  "wallet_unlocked_until_timestamp": "20140917T171137",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null,
  "wallet_version": 101
}
--- there are now 1 active connections to the p2p network
--- syncing with p2p network, 1722 blocks left to fetch
I am disconnecting peer 176.9.234.167:39984 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, 1723 blocks left to fetch
I am disconnecting peer 176.9.234.167:39997 for reason: You offered us a block that we reject as invalid

client keep on been disconnected form peers.

Code Select Expand

--- there are now 1 active connections to the p2p network
I am disconnecting peer 114.215.104.153:36016 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 176.9.234.167:39844 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network

This peer is showing up on both of our seed nodes....

Code Select Expand

Peer 209.141.182.156:8701 disconnected us: You offered us a block that we reject as invalid

We are looking into the cause of this message... so don't take it personally if a peer rejects you right now.

Very interesting you are rejecting the very first block as invalid...

If you start with a fresh data directory do you always get this problem?

Ok, so I think I can summarize your problem as:
1) log files getting to large (32 bit machine?)
2) crashing that leaves the database in inconsistent state.
3) unable to synchronize with a database in an inconsistent state.

Our solutions are:
1) We need to add extra validation checks on startup
2) We are putting in code today to greatly reduce logging now that we have found most issues.

[sfinder]

XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D

111xts on the way

[spartako]

XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D

Sent

Code Select Expand


  3921.0    2014-07-02T14:17:45 spartako-w          metalallen          100.00000 XTS       0.10000 XTS                                                e30da037
   3925.0    2014-07-02T14:18:45 spartako-w          metalallen          100.000000 FREE     0.10000 XTS                                                2e6cff90



[xeroc]

XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D

50 XTS on the way

[metalallen]

XTS6qkmjqq48eqUwQ6NR8jgrE26FVkTaC5qk4XhxQDiSwBmDeUQ98

Some funds please. :D :D