Author Topic: Dry Run 6: Great Scott!  (Read 90975 times)

0 Members and 1 Guest are viewing this topic.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
sent me funds please  ;)

XTS5as1STEgLPDq6mW5z8V3QqL2AUub4aasjUXPBhNPdLXmehynyA     liondani

please...

sent you some xts
>>> approve bitcoiners

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
sent me funds please  ;)

XTS5as1STEgLPDq6mW5z8V3QqL2AUub4aasjUXPBhNPdLXmehynyA     liondani

please...
100 xts to you  :)

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
Code: [Select]
wallet_set_delegate_trust_level cass-delegate-x 1
cass for delegate  :P
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1905
    • View Profile
  • BitShares: ebit
Bitshares maybe can reference paxos model or google's spanner system.

来自我的 HTC 802d 上的 Tapatalk

Maybe
telegram:ebit521
https://weibo.com/ebiter

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Code: [Select]
"block_production_enabled": true,
Code: [Select]
  "wallet_open": true,
  "wallet_unlocked_until": "20170827T033301",
Code: [Select]
wallet (unlocked) >>> blockchain_list_delegates 54 55
ID   NAME                          APPROVAL            BLOCKS PRODUCED BLOCKS MISSED   
---------------------------------------------------------
390  dele-puppy                    0.0002794781 %      0               1               
}

delegate loop is not listed in default.log at all.

Can you give the full output of 'get_info'?
Code: [Select]
{
  "blockchain_head_block_num": 557,
  "blockchain_head_block_time": "20140626T201400",
  "blockchain_head_block_time_rel": "2 minutes old",
  "blockchain_confirmation_requirement": 8,
  "blockchain_average_delegate_participation": 75.989085948158248,
  "network_num_connections": 20,
  "ntp_time": "20140626T201547.571215",
  "ntp_error_seconds": 0.0019889999999999999,
  "wallet_unlocked_seconds_remaining": 99991034,
  "wallet_next_block_production_time": "20140626T214800",
  "wallet_seconds_until_next_block_production": 5533,
  "wallet_local_time": "20140626T201547",
  "blockchain_random_seed": "52d21c448f600fac7bfaf8e0416c501da3a1c20f",
  "blockchain_shares": 199999796862876,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "wallet_open": true,
  "wallet_unlocked_until": "20170827T033301",
  "wallet_version": 100
}
« Last Edit: June 26, 2014, 08:19:29 pm by puppies »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline vikram

Code: [Select]
"block_production_enabled": true,
Code: [Select]
  "wallet_open": true,
  "wallet_unlocked_until": "20170827T033301",
Code: [Select]
wallet (unlocked) >>> blockchain_list_delegates 54 55
ID   NAME                          APPROVAL            BLOCKS PRODUCED BLOCKS MISSED   
---------------------------------------------------------
390  dele-puppy                    0.0002794781 %      0               1               
wallet (unlocked) >>>

delegate loop is not listed in default.log at all.

Can you give the full output of 'get_info'?

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Code: [Select]
"block_production_enabled": true,
Code: [Select]
  "wallet_open": true,
  "wallet_unlocked_until": "20170827T033301",
Code: [Select]
wallet (unlocked) >>> blockchain_list_delegates 54 55
ID   NAME                          APPROVAL            BLOCKS PRODUCED BLOCKS MISSED   
---------------------------------------------------------
390  dele-puppy                    0.0002794781 %      0               1               
wallet (unlocked) >>>

delegate loop is not listed in default.log at all.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline vikram

So, my delegate missed a block and I'm trying to figure out why.  the block I missed is block 518.  I had 20 p2p connections at the time.  list_errors returns nothing.  default.log shows a 4 minute gap between block 517 and 518.

Code: [Select]
20140626T182401.070680       th_a         on_new_block ] After push_block, current head block is 517                    client.cpp:763
20140626T182801.038535       th_a       handle_message ] CLIENT: just received block 35876ef9772562d6d3bc910a60d14816c8c84b85                   client.cpp:836

p2p.log shows
Code: [Select]
20140626T182402.649469       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182428.349431       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 114.215.104.153:3$
20140626T182428.349501       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182457.945627       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 46.176.1.230:8601$
20140626T182457.945691       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182611.891259       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 216.252.204.39:61$
20140626T182611.891331       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182704.984028       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 70.114.143.108:86$
20140626T182704.984093       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182708.277491       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 188.138.107.159:8$
20140626T182708.277570       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182714.057405       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 92.243.18.20:4678$
20140626T182714.057465       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182755.985046       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 216.252.204.39:64$
20140626T182755.985122       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182801.035571       th_a           on_message ] handling message item_ids_inventory_message_type 296e79865074646a8dffb99c33328d7c8f31aa96 size 25 from peer 107.170.30.18$
20140626T182801.037188       th_a on_item_ids_inventor ] received inventory of 1 items from peer 107.170.30.182:51623                   node.cpp:1784

As far as I can tell my delegate didn't even try to produce a block around 18:26.  Is there somewhere else I should look for the answer?

Your delegate loop didn't fire according to that default.log. Do you have an ENABLED delegate in the ACTIVE 101 spots? If so, are you seeing a message in default.log every 2 minutes like:
Code: [Select]
Starting delegate loop at time: 20140626T195000

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
sent me funds please  ;)

XTS5as1STEgLPDq6mW5z8V3QqL2AUub4aasjUXPBhNPdLXmehynyA     liondani

please...

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
So, my delegate missed a block and I'm trying to figure out why.  the block I missed is block 518.  I had 20 p2p connections at the time.  list_errors returns nothing.  default.log shows a 4 minute gap between block 517 and 518.

Code: [Select]
20140626T182401.070680       th_a         on_new_block ] After push_block, current head block is 517                    client.cpp:763
20140626T182801.038535       th_a       handle_message ] CLIENT: just received block 35876ef9772562d6d3bc910a60d14816c8c84b85                   client.cpp:836

p2p.log shows
Code: [Select]
20140626T182402.649469       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182428.349431       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 114.215.104.153:3$
20140626T182428.349501       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182457.945627       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 46.176.1.230:8601$
20140626T182457.945691       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182611.891259       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 216.252.204.39:61$
20140626T182611.891331       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182704.984028       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 70.114.143.108:86$
20140626T182704.984093       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182708.277491       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 188.138.107.159:8$
20140626T182708.277570       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182714.057405       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 92.243.18.20:4678$
20140626T182714.057465       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182755.985046       th_a           on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 216.252.204.39:64$
20140626T182755.985122       th_a on_address_request_m ] Received an address request message                    node.cpp:1320
20140626T182801.035571       th_a           on_message ] handling message item_ids_inventory_message_type 296e79865074646a8dffb99c33328d7c8f31aa96 size 25 from peer 107.170.30.18$
20140626T182801.037188       th_a on_item_ids_inventor ] received inventory of 1 items from peer 107.170.30.182:51623                   node.cpp:1784

As far as I can tell my delegate didn't even try to produce a block around 18:26.  Is there somewhere else I should look for the answer?
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline chono

  • Full Member
  • ***
  • Posts: 59
    • View Profile
Bitshares maybe can reference paxos model or google's spanner system.

来自我的 HTC 802d 上的 Tapatalk

Weibo:Will_BTS

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
Looks like my delegate node is on a fork..

Code: [Select]
>>> blockchain_list_forks
[
  111,
  270
]

Code: [Select]
>>> get_info
{
  "blockchain_head_block_num": 274,
  "blockchain_head_block_time": "20140626T125800",
  "blockchain_head_block_time_rel": "4 hours old",
  "blockchain_confirmation_requirement": 303,
  "blockchain_average_delegate_participation": 43.014128728414441,
  "network_num_connections": 8,
  "ntp_time": "20140626T170236.409083",
  "ntp_error_seconds": 21.870723000000002,
  "wallet_unlocked_seconds_remaining": 999997216,
  "wallet_next_block_production_time": "20140626T184000",
  "wallet_seconds_until_next_block_production": 5844,
  "wallet_local_time": "20140626T170236",
  "blockchain_random_seed": "2f085116ca68bbabf87f33a67d2b99724ebb68c4",
  "blockchain_shares": 199999812210311,
  "network_num_connections_max": 200,
  "network_protocol_version": 104,
  "wallet_open": true,
  "wallet_unlocked_until": "19100127T113436",
  "wallet_version": 100
}

Code: [Select]
default (unlocked) >>> about
{
  "bitshares_toolkit_revision": "f804829027a76857fc5d4533a31e6a08aab75e52",
  "bitshares_toolkit_revision_age": "62 minutes ago",
  "fc_revision": "b8efe02cdbeb6ef063390db52301d819170b79fe",
  "fc_revision_age": "63 minutes ago",
  "compile_date": "compiled on Jun 26 2014 at 17:12:02"
}
>>> approve bitcoiners

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
sent me funds please  ;)

XTS5as1STEgLPDq6mW5z8V3QqL2AUub4aasjUXPBhNPdLXmehynyA     liondani

Offline vikram

Code: [Select]
322  light                         0.0000000000 %      0               0Still 0% approval  :o

voted for you, you should be in the active delegates list next block
Thanks, i'm in the Top  :D

Also, my wallet keeps spamming these more and more:
Code: [Select]
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1
active delegates: 1

Make sure you are running the latest code.

Offline vikram

I have 2 strange cases:
1)

dxtr-wallet (unlocked) >>> blockchain_list_blocks 409 3
    HEIGHT                          TIME      TXN COUNT                                                 SIGNING DELEGATE    SIZE LATENCY
----------------------------------------------------------------------------------------------------------------------------------------
       409           2014-06-26T13:28:00              2                                                         scroodge     584       
       410           2014-06-26T13:30:00              1                                                  delegate-dorian     499       1
       411           2014-06-26T13:32:00              0                                                          vikram9     182      25
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats vikram9
[[
    231,{
      "missed": false,
      "latency": null
    }
  ],[
    356,{
      "missed": false,
      "latency": null
    }
  ],[
    411,{
      "missed": false,
      "latency": 25
    }
  ]
]
dxtr-wallet (unlocked) >>> blockchain_get_delegate_block_stats scroodge
[[
    411,{
      "missed": false,
      "latency": 0
    }
  ]
]


One command, blockchain_get_delegate_block_stats says that both scroodge and vikram9 have produced the same block,
another command, blockchain_list_blocks 409 3 lists that block 409 was created by scroodge, not 411.

2) When I send some XTS from one and the same wallet account to another in this same wallet, transaction is processed, but XTS disappears from source and does not appear in target (one of accounts is a delegate, so there is no blockchain rescan afterwards [I think]).

Are those known issues?

I'm not sure about the transfer issue, but it sounds like you are right.  can you manually wallet_rescan_blockchain?  Maybe try turning off block production first.  If neither of those work I would export the private key of the account with funds close the wallet, create another one, and import the key.

As for the blockchain_get_delegate_block_stats that same issue was happening on the last testnet.  I can't remember exactly what Bytemaster said, but it was something along the lines of an issue with delegate ID.  Perhaps its similar to the wallet bug that makes it look like you have access to others accounts.

This is a known issue we are working on.