Have you deleted the object_database and oct5 directories as Spectral did?

Historically all that I have done is issue --resync-blockchain and the witness connects to the seed(s) to rebuild the chain.  Upon witeness startup the console logs:
483498ms th_a       witness.cpp:111               plugin_initialize    ] witness plugin:  plugin_initialize() end
483500ms th_a       db_management.cpp:98          wipe                 ] Wiping database
483513ms th_a       object_database.cpp:81        wipe                 ] Wiping object_database.
484226ms th_a       application.cpp:242           operator()           ] Initializing database...

However, "Wiping object_database" does not seem to be occurring as expected, as the witness was unable to get blocks beyond 45158.

I did take the advise to manually remove both the object_database and data_dir directories from the witness, leaving only the genesis.json file.  This of course forces the node to start from a clean state.  This resulted in a proper sync to the main chain.

This seems like a bug to me, but will defer to development to review if that is as designed functionality.  If so, please advise what the best practice is to force the witness to start from a clean state using command line options, as I'd rather not script from shell.

Best,
Fox

I don't know why I can't upgrade the account, never the less would somebody please vote delegate.verbaltech in?

Thanks!

I've not checked the genesis file, but suspect your IsLifetimeMember flag was set to TRUE for this go. 

I see the witness now:
get_witness delegate.verbaltech
{
  "id": "1.6.34",
  "witness_account": "1.2.22441",
  "last_aslot": 0,
  "signing_key": "GPH6oUevPDj52JK67E199jBAMBuh6CQBQGgkyLtoXKiAvTVCpvYU7",
  "vote_id": "1:45",
  "total_votes": 0,
  "url": "https://bitsharestalk.org/index.php/topic,13837.0.html",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}


Quote from: Fox on October 05, 2015, 10:32:57 pm

I ended up on a fork.  Resync-blockchain in progress.  Back soon...

A fork you couldn't recover from automatically?

Yes, the node failed to find the main chain while actively producing blocks.  I've not yet reviewed the logs to determine when the fork occurred.  We should see a number of blocks that fox produced and were rejected by the network.  I noticed the block_head_age was minutes old, so restarted the node.  It failed to sync upon reboot, so I --resync-blockchain. 

I'm built, synced and <nearly> ready to produce blocks.  I'm looking for 5000+ CORE to complete:
create_witness fox "" true
Thanks in advance.

Voting bias detected: witnesses with the digit 5 in their ID are not in active witness group:
info
{
...
  "active_witnesses": [
    "1.6.2",
...
   "1.6.14",
    "1.6.16",
...
    "1.6.24",
    "1.6.26",
...
    "1.6.31",
...
  ],
Who are these digit 5 witnesses?
get_witness fox
{
  "id": "1.6.25",
  "witness_account": "1.2.30566",
  "last_aslot": 23934,
...
  "total_votes": "9178845900",
...
  "last_confirmed_block_num": 7460
}

get_witness delegate-clayop
{
  "id": "1.6.15",
  "witness_account": "1.2.22404",
  "last_aslot": 23969,
...
  "total_votes": "9178845900",
...
  "last_confirmed_block_num": 7490
}

Both witnesses have votes, have produced in the past, but neither are in the active witness group at this time.  I recall Bytemaster voted out the witness lot, then stated he would vote them all back in, so maybe these were just missed and/or not meeting the minimum vote threshold (I'm not sure how to determine the threshold). 

Thanks for looking into this.

Disclaimer: I am one of the digit 5 witnesses

Sadly there is need for a hardfork for this testnet... this time I promise to upgrade the init nodes.

The issue discovered is that the witness count code was setting a threshold equal to 50% of all stake rather than 50% of voting stake so every witness got voted in unless over 50% of the stake voted for less than everyone.   In other words, the reverse case from the prior hardfork.   

I set the fork time for 24 hours from now.

Is this why my witness was expected to produce blocks as soon as create_witness <accountname> "URL" true completed?  I was quite surprised to have 0 votes and missing blocks.

Rebuilding...

Quote from: clayop on October 02, 2015, 04:30:05 am

104.155.223.175 and did not specify port I think. Maybe 1776? or 1984?

Trying both with --resync-blockchain now from two nodes...

I am unable to connect on either of those two ports. 

I think I'm on the main chain.
How can I be a seed node?

Code: [Select]

  "head_block_num": 14573,
  "head_block_id": "000038edf68d8cf4656f6f9595d8e2f23f9eabfd",
  "head_block_age": "10 seconds old",
  "next_maintenance_time": "49 minutes in the future",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "2.34375000000000000",

What IP:PORT is your node?