October 1st Testnet for Advanced Users

Started by bytemaster, October 01, 2015, 01:48:43 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bytemaster

For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

My bad guys.   I forgot to upgrade the main node and it went off on a fork once the witness count diverged....   :(    :'( :'( :-[ :-[

I am preparing a new test network that has all of the recent changes in it.   
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

sittingduck


Quote from: Troglodactyl on October 02, 2015, 12:35:46 PM
There was a hard fork at block 10,000 from a post-tag commit.  Maybe new witnesses got voted in around 14,000 who hadn't gotten that upgrade yet and dropped us below the required participation level.

That is exactly what happened.   Bm didn't upgrade the init node. 


Sent from my iPhone using Tapatalk

Troglodactyl

There was a hard fork at block 10,000 from a post-tag commit.  Maybe new witnesses got voted in around 14,000 who hadn't gotten that upgrade yet and dropped us below the required participation level.

iHashFury


spartako

Quote from: wackou on October 02, 2015, 09:12:13 AM
I think the main chain is stuck on #14541. Each of us can start its own fork but the main chain stays on #14541. I seem to recall that bytemaster said the main chain needs 2/3 of witnesses to keep on going (or sth like that, not sure anymore).

I guess we're going to have to wait for the next testnet or until bytemaster works his magic somehow to resurrect this one...

Yes, if I remember well we need to use checkpoints in some way to resurrect the network but I don't know how....
wallet_account_set_approval spartako

iHashFury

My witness node - delegate.ihashfury

info
{
  "head_block_num": 12057,
  "head_block_id": "00002f19643260855f86fdb11d4947d3cb7eec7b",
  "head_block_age": "9 hours old",
  "next_maintenance_time": "8 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "15.62500000000000000",


seed node 0
info
{
  "head_block_num": 14541,
  "head_block_id": "000038cd712f759764979352e3f068072ce7fabf",
  "head_block_age": "6 hours old",
  "next_maintenance_time": "5 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "41.40625000000000000",


seed node 1
info
{
  "head_block_num": 14541,
  "head_block_id": "000038cd712f759764979352e3f068072ce7fabf",
  "head_block_age": "6 hours old",
  "next_maintenance_time": "5 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "41.40625000000000000",

wackou

I think the main chain is stuck on #14541. Each of us can start its own fork but the main chain stays on #14541. I seem to recall that bytemaster said the main chain needs 2/3 of witnesses to keep on going (or sth like that, not sure anymore).

I guess we're going to have to wait for the next testnet or until bytemaster works his magic somehow to resurrect this one...
Please vote for witness wackou! More info at [url="http://digitalgaia.io"]http://digitalgaia.io[/url]

betax

[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

cube

Quote from: clayop on October 02, 2015, 04:12:22 AM
I think I'm on the main chain.
How can I be a seed node?

  "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",


Participation rate is 2.3. I think your witness is in your own fork.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

betax

Quote from: spartako on October 02, 2015, 07:26:59 AM
Here what I see with my witness for block production:


new >>> info
info
{
  "head_block_num": 12057,
  "head_block_id": "00002f19643260855f86fdb11d4947d3cb7eec7b",
  "head_block_age": "7 hours old",
  "next_maintenance_time": "6 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "15.62500000000000000",


This is what I see with observer witness:

info
{
  "head_block_num": 14541,
  "head_block_id": "000038cd712f759764979352e3f068072ce7fabf",
  "head_block_age": "4 hours old",
  "next_maintenance_time": "3 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "41.40625000000000000",


And this error code:

1542346ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 000038e34c78828a6de58c8f7c45a4765d35702d, 14563
1542347ms th_a       fork_database.cpp:58          push_block           ] Head: 14542, 000038cee9a448ff754f72a7f2e575eaf72f37cd
1542430ms th_a       application.cpp:416           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block

    {"new_block":{"previous":"000038e2edba3a14378292e57d79343e86ada943","timestamp":"2015-10-02T03:21:36","witness":"1.6.10","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f7c5fa17577ff0fdbe0d3966b2e858c8484e6ade8d55188331e46eddcf58d5e6b258951127c9e311446a61bd432a4854b376a75a9812a28f2793a16586aee5378","transactions":[]}}
    th_a  db_block.cpp:195 _push_block


same as me....
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

betax

Quote from: wackou on October 02, 2015, 06:11:27 AM
My node got stuck during the night, too (didn't crash) on block 14541 with an unlinkable block error. I relaunched it (with --enable-stale-production, wouldn't do anything otherwise) and it seems like I'm producing blocks again (seems like I'm the only one, I did 14542, 14543, 14544 and 14545 as of now). Not sure if I am on my own fork and nobody sees it or if I'm the only one producing blocks (feeling a bit lonely there :( )

Yes you are in your own fork with --enable-stale-production.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

spartako

Here what I see with my witness for block production:


new >>> info
info
{
  "head_block_num": 12057,
  "head_block_id": "00002f19643260855f86fdb11d4947d3cb7eec7b",
  "head_block_age": "7 hours old",
  "next_maintenance_time": "6 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "15.62500000000000000",


This is what I see with observer witness:

info
{
  "head_block_num": 14541,
  "head_block_id": "000038cd712f759764979352e3f068072ce7fabf",
  "head_block_age": "4 hours old",
  "next_maintenance_time": "3 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "41.40625000000000000",


And this error code:

1542346ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 000038e34c78828a6de58c8f7c45a4765d35702d, 14563
1542347ms th_a       fork_database.cpp:58          push_block           ] Head: 14542, 000038cee9a448ff754f72a7f2e575eaf72f37cd
1542430ms th_a       application.cpp:416           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block

    {"new_block":{"previous":"000038e2edba3a14378292e57d79343e86ada943","timestamp":"2015-10-02T03:21:36","witness":"1.6.10","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f7c5fa17577ff0fdbe0d3966b2e858c8484e6ade8d55188331e46eddcf58d5e6b258951127c9e311446a61bd432a4854b376a75a9812a28f2793a16586aee5378","transactions":[]}}
    th_a  db_block.cpp:195 _push_block
wallet_account_set_approval spartako

cube

#103
I woke up and saw the witness went into some kind of dead-end looping.  Cli-wallet not responding to commands.  I killed it and resync.


3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block

    {"new_block":{"previous":"00003971a01a9f240dda7c38084fec9c0cdd03c4","timestamp":"2015-10-02T03:40:33","witness":"1.6.8","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20097269683274da7321de9efe1adb0650a33f2c48abb0416038fd9a1d2ae081a1713c9023cda64637d4d953e100d98aa77894c82baad997596cdccf74992bfb83","transactions":[]}}
    th_a  db_block.cpp:195 _push_block
3356273ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 00003973308552044569cda8bb2fae12db0583d0, 14707
3356274ms th_a       fork_database.cpp:58          push_block           ] Head: 14542, 000038cee9a448ff754f72a7f2e575eaf72f37cd
3356799ms th_a       application.cpp:416           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block

    {"new_block":{"previous":"0000397238fd200cb362a70f061bbcc1541191e8","timestamp":"2015-10-02T03:40:39","witness":"1.6.10","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f6fad5dd8b4f9505fd4b06018d0122da4491f9e525ef311acfb9f9413543d33e32e32ec621c34a4b66c9a5576910f308de40779f5183a83f1ee77601773a91d56","transactions":[]}}
    th_a  db_block.cpp:195 _push_block
3356808ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 0000397412c0eb1b55c8804bc26bf5345a89b522, 14708
3356810ms th_a       fork_database.cpp:58          push_block           ] Head: 14542, 000038cee9a448ff754f72a7f2e575eaf72f37cd
3357282ms th_a       application.cpp:416           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block

    {"new_block":{"previous":"00003973308552044569cda8bb2fae12db0583d0","timestamp":"2015-10-02T03:40:45","witness":"1.6.8","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"202c99e1bd488438009d0514ba920b0cbad487949b61f1220389b694d53399cd5412ee671824ce6a7daef8bcf413757a1e1a1fd6112fff052c9216d256df627665","transactions":[]}}
    th_a  db_block.cpp:195 _push_block
3357291ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 00003975ea2809e2983ca73c29a383bad0ebb4e7, 14709
3357292ms th_a       fork_database.cpp:58          push_block           ] Head: 14542, 000038cee9a448ff754f72a7f2e575eaf72f37cd
3357777ms th_a       application.cpp:416           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block



I tried to resync but stuck at

  "head_block_num": 14541,
  "head_block_id": "000038cd712f759764979352e3f068072ce7fabf",
  "head_block_age": "4 hours old",


@clayop
Which port are you running on?

Edit: I saw your port from my console - 175.223.155.104.b:4969.  I think you are not running a seed. 
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

jtme

Quote from: clayop on October 02, 2015, 05:21:13 AM
Quote from: jtme on October 02, 2015, 05:02:35 AM
Quote from: Fox on October 02, 2015, 04:39:02 AM
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 do not think you are on that ports. Can you try lsof -p PID_OF_YOUR_WITNESS and
see the listen ports ?

How about this?
104.236.51.238:1984

that is the orig node from https://github.com/cryptonomex/graphene/releases/tag/test4
Ending on some dead fork with this one.