Author Topic: October 5 Test Network  (Read 140981 times)

0 Members and 1 Guest are viewing this topic.

Offline roadscape


@Spectral @Bhuz

If you guys are having trouble publishing feeds, could you update to latest master and try again?  I made the error message you're getting more informative.

I had similar error messages... turns out the hard drive was full (p2p logs)
http://cryptofresh.com  |  witness: roadscape

Offline Thom


In Graphene terminology, "reindexing" and "replaying" are the same thing.

Yes, I thought they were different. If they are truly the same thing, why bother having 2 separate command line args?

I bet you guys just like to confuse us for fun! ;)

There's also "resyncing" which is different.  Reindexing / replaying just nukes the chain state DB, but keeps the blocks and reads them off the local disk.  Resyncing nukes the blocks too, and re-downloads them from the network.

Code: [Select]
rm -Rf witness_node_data_dir/blockchain/object_database       # this is what reindex / replay does
rm -Rf witness_node_data_dir/blockchain                       # this is what resync does

Coolness, thanks for the info theoretical!

I just switched production to to another VPS, which worked well and quickly. That was an excellent and very important enhancement! With just a bit of automation we can detect and switch to alternate witness nodes in case of attack or any other reason. Nice!
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline theoretical


In Graphene terminology, "reindexing" and "replaying" are the same thing.

Yes, I thought they were different. If they are truly the same thing, why bother having 2 separate command line args?

I bet you guys just like to confuse us for fun! ;)

There's also "resyncing" which is different.  Reindexing / replaying just nukes the chain state DB, but keeps the blocks and reads them off the local disk.  Resyncing nukes the blocks too, and re-downloads them from the network.

Code: [Select]
rm -Rf witness_node_data_dir/blockchain/object_database       # this is what reindex / replay does
rm -Rf witness_node_data_dir/blockchain                       # this is what resync does
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline Thom

If it was only replaying it never caught up. It just ended in a firey crash:

witness_node: /home/deletech/BitShares2_build/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.
Aborted

I've had the same thing happen to me, see https://github.com/cryptonomex/graphene/issues/332 -- but I've never been able to reproduce it.

I was able to bring up another node on a different VPS, it synced up just fine. I'm about to do an update_witness to verify the switching process.
Don't know what it is about that particular VPS in LA, but I cannot get it working today. I will resinstall the OS from scratch and use it for VPS setup script testing.

In Graphene terminology, "reindexing" and "replaying" are the same thing.  They both mean starting the chain state database in the genesis state, then applying your previously saved blocks to advance the chain state.  You say "these percentages aren't for the replay but rather for the reindexing" as if "replay" and "reindexing" are different things.  They're actually the same thing.

I agree the get_blockchain_synop message is spammy and we should probably get rid of it.

Yes, I thought they were different. If they are truly the same thing, why bother having 2 separate command line args?

I bet you guys just like to confuse us for fun! ;)
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline theoretical


@Spectral @Bhuz

If you guys are having trouble publishing feeds, could you update to latest master and try again?  I made the error message you're getting more informative.
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline theoretical

If it was only replaying it never caught up. It just ended in a firey crash:

Quote
witness_node: /home/deletech/BitShares2_build/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.
Aborted


I've had the same thing happen to me, see https://github.com/cryptonomex/graphene/issues/332 -- but I've never been able to reproduce it.

Note that it never gets to 100%, but I see now that these percentages aren't for the replay but rather for the reindexing. If the replay is still in progress and the blockchain is yet to be synced, why does it consistently fail and crash? I notice these  "get_blockchain_synop" lines also appear quite frequently in the witness node that is working properly and signing blocks.

At least I think it's working properly, I don't see my missed blocks count increasing and I do see blocks from other witnesses and these lines:
Quote
2748001ms th_a       witness.cpp:176               block_production_loo ] Generated block #111989 with timestamp 2015-10-09T20:45:48 at time 2015-10-09T20:45:48
Which tell me all is well.

Looks fine to me.  It doesn't show 100% because the print is just printing every 10,000th block, the message when it's done doesn't say 100%, rather the "Done reindexing" message is what indicates the reindex is finished.

In Graphene terminology, "reindexing" and "replaying" are the same thing.  They both mean starting the chain state database in the genesis state, then applying your previously saved blocks to advance the chain state.  You say "these percentages aren't for the replay but rather for the reindexing" as if "replay" and "reindexing" are different things.  They're actually the same thing.

I agree the get_blockchain_synop message is spammy and we should probably get rid of it.
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline Bhuz

  • Committee member
  • Sr. Member
  • *
  • Posts: 467
    • View Profile
  • BitShares: bhuz
Can't public feed too

Offline bytemaster

If it was only replaying it never caught up. It just ended in a firey crash:

Quote
237745ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237755ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237789ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237792ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237800ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237856ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e"]
witness_node: /home/deletech/BitShares2_build/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.
Aborted
Quote

This was an attempt to start from scratch. Wiped object_database, blockchain, p2p, logs. No --replay-blockchain or --resync-blockchain. No cmd line params except --data-dir, everything is in the config.ini file. All essentials from config noted in my previous posts.
For starters you built in DEBUG mode, but you didn't run it in gdb so I don't have a stack trace.   

I have just made some commits to *fc* that should attempt to prevent that particular crash.
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 Spectral

Witness spectral stopped producing blocks and started producing error messages at the witness output. Here is a log from the screen buffer of the witness output:

https://drive.google.com/file/d/0BzEEZBS7b6xPUnJvQXFZUHZQZW8/view?usp=sharing

Did this also happen to the others?

I deleted oct5 and object_database, restarted witness, and it's back to producing blocks and price feed.

Looks like we missed the real error.

Yes... I will enable file logging on screen, so next time it happens, the log should include everything.


I checked the CLI now, and it seems something is not right. Feeds do not publish anymore, since 2 hours ago. Here's the cli_wallet output:

Code: [Select]
3007026ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id b75bf74af11ab7210e24e79b665fddb77a70b37b
4117ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id d83a159834150bfb4f6ba6ae767b6e6b2187fbdf
606929ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 3375e940443eb7b123a4d905a23e86cb475b7761
1204093ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 9eea37c7051673a6e0e6e8bda816ac682ddf7312
1806802ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id ae4e7532a0024a244a2b431e834aa4487304fa40
2405192ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id d70a6e10be5f7f45a000efe1c945fab97cfc6cf4
3007726ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 1c61a0c93fe43ce1080e7e617d8173ec034e1786
6366ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 314093bb2434cd1ac9322bdfb01ed15549860cb3
605558ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 67d051fbe2795f7ad61f8f4bb15fcdae2c894511
1205379ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id eb4c2e45fe8e129586a422c41caa0f476a17b806
1804573ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id a362dd39f7768bcc07d56f7a964bb1e2bba361fb
unlocked >>> get_witness spectral
get_witness spectral
{
  "id": "1.6.38",
  "witness_account": "1.2.73210",
  "last_aslot": 123874,
  "signing_key": "GPH8ZWNd9K82gPqKVDbkK8etaYTBMQ3ME3MTQ6HqF586ZbMLrZ5DH",
  "pay_vb": "1.13.64",
  "vote_id": "1:49",
  "total_votes": "7774534618288",
  "url": "bitspace.no",
  "total_missed": 958,
  "last_confirmed_block_num": 111813
}
unlocked >>>

get_witness seems right, so does the witness_output.
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline Thom

If it was only replaying it never caught up. It just ended in a firey crash:

Quote
237745ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237755ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237789ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237792ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237800ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e","0000dd2ddbe5e2f349056489807735ee69a72f64","0000dd3361101334b8cd482d158f26075aa19cda","0000dd36f4282b71818c080ed38b031694afacc9","0000dd388f8db8edf41e928637f20e2720b34082"]
237856ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd20f0f688d88c6ecafa73e9396da128575e"]
witness_node: /home/deletech/BitShares2_build/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.
Aborted

This was an attempt to start from scratch. Wiped object_database, blockchain, p2p, logs. No --replay-blockchain or --resync-blockchain. No cmd line params except --data-dir, everything is in the config.ini file. All essentials from config noted in my previous posts.

Here's the start of another attempt. This time left everything intact from the run that crashed except I removed the object_database folder AND I used puppies seed instead of the :2005 seed.

Quote
973661ms th_a       witness.cpp:111               plugin_initialize    ] witness plugin:  plugin_initialize() end
973662ms th_a       application.cpp:302           startup              ] Detected unclean shutdown. Replaying blockchain...
973662ms th_a       application.cpp:243           operator()           ] Initializing database...
1073034ms th_a       db_management.cpp:45          reindex              ] reindexing blockchain
1073047ms th_a       db_management.cpp:98          wipe                 ] Wiping database
1073179ms th_a       object_database.cpp:81        wipe                 ] Wiping object_database.
1133390ms th_a       db_debug.cpp:79               debug_dump           ] total_balances[asset_id_type()].value: 14239376866944 core_asset_data.current_supply.value: 271289987694689
1133406ms th_a       db_debug.cpp:82               debug_dump           ] core_in_orders: 14239376866944 reported_core_in_orders: 14239376866944
1133477ms th_a       db_management.cpp:147         open                 ] last_block->id(): 0000dd388f8db8edf41e928637f20e2720b34082 last_block->block_num(): 56632
1133477ms th_a       db_management.cpp:59          reindex              ] Replaying blocks...
   3.53157%   2000 of 56632   
   7.06314%   4000 of 56632   
   10.5947%   6000 of 56632   
   14.1263%   8000 of 56632   
   17.6579%   10000 of 56632   
   21.1894%   12000 of 56632   
   24.721%   14000 of 56632   
   28.2526%   16000 of 56632   
   31.7842%   18000 of 56632   
   35.3157%   20000 of 56632   
   38.8473%   22000 of 56632   
   42.3789%   24000 of 56632   
   45.9104%   26000 of 56632   
   49.442%   28000 of 56632   
   52.9736%   30000 of 56632   
   56.5052%   32000 of 56632   
   60.0367%   34000 of 56632   
1272503ms th_a       asset_evaluator.cpp:553       do_evaluate          ] USD feed pub with wrong ass
et by wackou in block 34129
1272511ms th_a       asset_evaluator.cpp:618       do_apply             ] Ignoring bad feed
1272603ms th_a       asset_evaluator.cpp:553       do_evaluate          ] SEK feed pub with wrong asset by wackou in block 34215
1272616ms th_a       asset_evaluator.cpp:618       do_apply             ] Ignoring bad feed
   63.5683%   36000 of 56632   
1279203ms th_a       asset_evaluator.cpp:553       do_evaluate          ] SILVER feed pub with wrong asset by wackou in block 36010
1279220ms th_a       asset_evaluator.cpp:618       do_apply             ] Ignoring bad feed
   67.0999%   38000 of 56632   
   70.6314%   40000 of 56632   
   74.163%   42000 of 56632   
   77.6946%   44000 of 56632   
   81.2262%   46000 of 56632   
   84.7577%   48000 of 56632   
1425106ms th_a       asset_evaluator.cpp:553       do_evaluate          ] EUR feed pub with wrong ass
et by wackou in block 49903
1425118ms th_a       asset_evaluator.cpp:618       do_apply             ] Ignoring bad feed
   88.2893%   50000 of 56632   
1427034ms th_a       asset_evaluator.cpp:553       do_evaluate          ] RUB feed pub with wrong ass
et by wackou in block 50353
1427045ms th_a       asset_evaluator.cpp:618       do_apply             ] Ignoring bad feed
   91.8209%   52000 of 56632   
   95.3525%   54000 of 56632   
   98.884%   56000 of 56632   
1459060ms th_a       db_management.cpp:93          reindex              ] Done reindexing, elapsed ti
me: 325.58274599999998600 sec

1459300ms th_a       thread.cpp:95                 thread               ] name:ntp tid:14049966996044
8
1459327ms th_a       thread.cpp:95                 thread               ] name:p2p tid:14049965107788
8
1459390ms th_a       application.cpp:123           reset_p2p_node       ] Adding seed node 104.236.14
4.84:1776
1459394ms th_a       application.cpp:135           reset_p2p_node       ] Configured p2p node to list
en on 0.0.0.0:1776
1459419ms th_a       application.cpp:185           reset_websocket_serv ] Configured websocket rpc to
 listen on 127.0.0.1:8090
1459435ms th_a       witness.cpp:116               plugin_startup       ] witness plugin:  plugin_sta
rtup() begin
1459435ms th_a       witness.cpp:123               plugin_startup       ] Launching block production
for 1 witnesses.
1459435ms th_a       witness.cpp:134               plugin_startup       ] witness plugin:  plugin_sta
rtup() end
1459435ms th_a       main.cpp:167                  main                 ] Started witness node on a c
hain with 56632 blocks.
1459435ms th_a       main.cpp:168                  main                 ] Chain ID is 60e21871125ea99
95fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83
1459450ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -
23481 us
1459561ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd388f8db8e
df41e928637f20e2720b34082"]
1459627ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd388f8db8e
df41e928637f20e2720b34082"]
1459678ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd388f8db8e
df41e928637f20e2720b34082"]
1459724ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd388f8db8e
df41e928637f20e2720b34082"]
1459774ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd388f8db8e
df41e928637f20e2720b34082"]
1459823ms th_a       application.cpp:712           get_blockchain_synop ] synopsis: ["0000dd388f8db8e
df41e928637f20e2720b34082"]

Note that it never gets to 100%, but I see now that these percentages aren't for the replay but rather for the reindexing. If the replay is still in progress and the blockchain is yet to be synced, why does it consistently fail and crash? I notice these  "get_blockchain_synop" lines also appear quite frequently in the witness node that is working properly and signing blocks.

At least I think it's working properly, I don't see my missed blocks count increasing and I do see blocks from other witnesses and these lines:
Quote
2748001ms th_a       witness.cpp:176               block_production_loo ] Generated block #111989 with timestamp 2015-10-09T20:45:48 at time 2015-10-09T20:45:48
Which tell me all is well.
« Last Edit: October 09, 2015, 08:52:25 pm by Thom »
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Ive set up another seed node at 104.236.144.84:1776

This will be my seed node on the main chain as well.  Is there a good reason to use a different ip/port once we go live?

https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Any chance we can end the flood tests a tad early?   It is interfering with my ability to test other features.

It seems like the network is holding up fine under load with high participation and high throughput of over 100 TPS.

Sure. Just tell me when do I have to stop it.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline bytemaster

Any chance we can end the flood tests a tad early?   It is interfering with my ability to test other features.

It seems like the network is holding up fine under load with high participation and high throughput of over 100 TPS. 
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 Bhuz

  • Committee member
  • Sr. Member
  • *
  • Posts: 467
    • View Profile
  • BitShares: bhuz
I got this on my cli_wallet, in red:

Code: [Select]
7364ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 0be4839dfa602f3be290b7d2a5524a318f889e50

Still, it is not crashed...

Once again

Code: [Select]
1804914ms th_a       wallet.cpp:1717               sign_transaction     ] Caught exception while broadcasting transaction with id 57a9c867a04e5adb669e208325606f02c204bc9e

What are they?

Offline Thom

How does the info command output look incorrect?  If you are doing --resync-blockchain then it nukes all the downloaded blocks and starts at the beginning, so you will see block times / block numbers in the past until you've finished downloading the chain.  The get_blockchain_synop messages are normal, they show your node exchanging block ID's with peers.

I see that it does make sense if the blockchain is not yet synced:

Code: [Select]
unlocked >>> info                                                                           [24/1938]
info
{
  "head_block_num": 271,
  "head_block_id": "0000010f433d8be806b267a237c6a81f176168a3",
  "head_block_age": "4 days old",
  "next_maintenance_time": "4 days ago",
  "chain_id": "60e21871125ea9995fe498b7f68a87a85c6583725ea5448f6fd969c59a37df83",
  "participation": "85.93750000000000000",
  "active_witnesses": [
    "1.6.1",
    "1.6.2",
    "1.6.3",
    "1.6.4",
    "1.6.5",
    "1.6.6",
    "1.6.7",
    "1.6.8",
    "1.6.9",
    "1.6.10",
    "1.6.11"
  ],
  "active_committee_members": [
    "1.5.0",
    "1.5.1",
    "1.5.2",
    "1.5.3",
    "1.5.4",
    "1.5.5",
    "1.5.6",
    "1.5.7",
    "1.5.8",
    "1.5.9",
    "1.5.10"
  ]
}

I was confused, and thought the replay was done before it was. I have seen the % reports along the way but then those stop & I get this voluminous output, plus I see no witness / irreversible block reports and it takes a really long time. I'll just let it go and see if it eventually syncs up.

If it doesn't (and just crashes) could it be due to the flood test, or is that irrelevant and not stressful in a replay scenario?

Still seeing tons of these "get_blockchain_synop" lines in the witness output, and occasionally one of these:
Code: [Select]
3184761ms th_a       witness.cpp:188               block_production_loo ] Not producing block because
 I don't have the private key for GPH6oUevPDj52JK67E199jBAMBuh6CQBQGgkyLtoXKiAvTVCpvYU7

If it's still in the replay phase why would that show up? That surely can't be part of the reply could it? It is going on 20 minutes and I see no change to the witness output. I've not seen any reports that others have taken this long. It really seems abnomal. However, the output of info looks OK now, generally.
« Last Edit: October 09, 2015, 08:01:56 pm by Thom »
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html