Author Topic: October 2nd Test Network  (Read 16758 times)

0 Members and 1 Guest are viewing this topic.

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
Can't we restart the network with checkpoints instead of waiting for bm to do it?  I'm assuming the stress testing just delayed some nodes' block production and caused forking until no branch had minimum participation.

Offline Spectral

My witness (which was not voted in) currently has the following output, and just keeps going like that... 'bitspace-testaccount1'

Code: [Select]
3221000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
3222000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
3223000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
3224000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn

The CLI interface is still working.
Vote for BTS-2 witness: spectral (1.6.30)
0.9 DVS delegate: dvs1.bitspace
Stay tuned for bitspace-clains worker!

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
It's dead for me. I tried --resync-blockchain but it didn't work. Not getting any blocks from the seed node.
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
I assume the network is still dead.... or have I locally the  problem?

Offline jsidhu

  • Hero Member
  • *****
  • Posts: 1335
    • View Profile
would be nice if those stress tests would be preanounced.
so we could observe the nodes behaviour (cpu/io load etc) and
bytemaster could set up new testnet if things go wrong
and the network dies.

Before the last stress test (when the network was mostly idle), I have noticed my witness was constantly consuming
10-15% cpu which was strange, also mising some blocks. So I switched
to backup witness. The new witness was under 1% cpu and reported
extra 20 missed blocks, althought the switchower was immediate using update_witness
without any block loss. So it seems the original witness lost track
of lost blocks somehow too.

Also would it not be better to run stress tests without debug mode on
to get better performance ?
Yea unless you want to find bugs first which they are going to have to do first anyway
Hired by blockchain | Developer
delegate: dev.sidhujag

Offline CalabiYau


last signs of life .....

Offline jtme

would be nice if those stress tests would be preanounced.
so we could observe the nodes behaviour (cpu/io load etc) and
bytemaster could set up new testnet if things go wrong
and the network dies.

Before the last stress test (when the network was mostly idle), I have noticed my witness was constantly consuming
10-15% cpu which was strange, also mising some blocks. So I switched
to backup witness. The new witness was under 1% cpu and reported
extra 20 missed blocks, althought the switchower was immediate using update_witness
without any block loss. So it seems the original witness lost track
of lost blocks somehow too.

Also would it not be better to run stress tests without debug mode on
to get better performance ?
« Last Edit: October 04, 2015, 07:09:38 am by jtme »

Offline rnglab

  • Full Member
  • ***
  • Posts: 171
    • View Profile
  • BitShares: rnglab
Sorry guys... I killed the testnet with spamming  :'(

that's becoming a success = )

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Sorry guys... I killed the testnet with spamming  :'(
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline CalabiYau

early morning:
Code: [Select]
{
  "head_block_num": 36472,
  "head_block_id": "00008e780f52da8c7a599c3a1d0b8dfeaf3a331d",
  "head_block_age": "6 hours old",
  "next_maintenance_time": "6 hours ago",
  "chain_id": "c746b258deb5e476601488d8dbb98cf6dcacc2dec857fda58514907257d461c3",
  "participation": "21.87500000000000000",
  "active_witnesses": [

edit: p2p log
Code: [Select]
2015-10-04T06:33:19 p2p:message read_loop            broadcast ] broadcasting trx: {"trx":{"ref_block_num":36472,"ref_block_prefix":2363118095,"expiration":"2015-10-03T23:49:03","operations":[[19,{"fee":{"amount":100000,"asset_id":"1.3.0"},"publisher":"1.2.91956","asset_id":"1.3.379","feed":{"settlement_price":{"base":{"amount":211,"asset_id":"1.3.379"},"quote":{"amount":63128,"asset_id":"1.3.0"}},"maintenance_collateral_ratio":1750,"maximum_short_squeeze_ratio":1500,"core_exchange_rate":{"base":{"amount":66284,"asset_id":"1.3.0"},"quote":{"amount":211,"asset_id":"1.3.379"}}},"extensions":[]}]],"extensions":[],"signatures":["1f5bb7a3f99bbd9dc22df0605758ce021a29a1b880f7e034edcd880d1b5e5c45622748b20976134e0a7faf34845058fc451654cae1f0d3a89f16cdc864a5f434e0"]}} node.cpp:4839
« Last Edit: October 04, 2015, 07:02:54 am by CalabiYau »

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
I woke up and found my witness node stuck at

Code: [Select]
{
  "head_block_num": 36472,
  "head_block_id": "00008e780f52da8c7a599c3a1d0b8dfeaf3a331d",
  "head_block_age": "5 hours old",
  "next_maintenance_time": "4 hours ago",
  "chain_id": "c746b258deb5e476601488d8dbb98cf6dcacc2dec857fda58514907257d461c3",
  "participation": "21.87500000000000000",


I found the error from the console log.
Code: [Select]
1743466ms th_a       db_block.cpp:189              _push_block          ] Failed to push new block:
3070000 undo_database_exception: undo database exception
The database does not have enough undo history to support a blockchain with so many missed blocks. Please add a checkpoint if you would like to continue applying blocks beyond this point.
    {"recently_missed":23405,"max_undo":1000}
    th_a  db_update.cpp:86 update_global_dynamic_data

    {"next_block.block_num()":36473}
    th_a  db_block.cpp:508 _apply_block

It seems the network cannot proceed due to 'too many missed blocks' - possibly due to the spam.
« Last Edit: October 04, 2015, 04:31:10 am by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline Thom

Mine is 4 hours old!
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline twitter

  • Sr. Member
  • ****
  • Posts: 279
    • View Profile
Why my chain is not able to sync ??....

Code: [Select]
./cli_wallet -w test_wallet  --chain-id c746b258deb5e476601488d8dbb98cf6dcacc2dec857fda58514907257d461c3

unlocked >>> info
info
{
  "head_block_num": 0,
  "head_block_id": "0000000000000000000000000000000000000000",
  "head_block_age": "51 hours old",
  "next_maintenance_time": "45 years ago",
  "chain_id": "c746b258deb5e476601488d8dbb98cf6dcacc2dec857fda58514907257d461c3",
  "participation": "100.00000000000000000",
  "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": []


witness:

Offline Thom

Witness is running, just need to be voted in:

get_witness delegate.verbaltech
{
  "id": "1.6.36",
  "witness_account": "1.2.22503",
  "last_aslot": 0,
  "signing_key": "GPH6oUevPDj52JK67E199jBAMBuh6CQBQGgkyLtoXKiAvTVCpvYU7",
  "vote_id": "1:57",
  "total_votes": 0,
  "url": "https://bitsharestalk.org/index.php/topic,13837.0.html",
  "total_missed": 0
}

 +5% to whoever sent the 20K CORE, much appreciated!

edit: Woops, forgot to upgrade! Doing that now... Done.
« Last Edit: October 04, 2015, 03:20:37 am by Thom »
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4572
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Unable to connect to the seed node "104.236.51.238:2001". Any idea?
BitShares committee member: abit
BitShares witness: in.abit