[Public Testnet] testnet.bitshares.eu

[boombastic]

@xeroc my witness is ready, please throw some votes this way.

Code: [Select]

agsexplorer-test

[startail]

The test is schedule till tomorrow, just 24 hrs left, and so far we only have 3 witnesses joining. I'm also not a voted in witness on the main net, so just 2 regular witnesses so far. I think this is worrisome if witnesses aren't active in the community development.

[kimziv]

My Testnet witness has been activated, kindly asking @xeroc to vote me in.

Witness: witness.yao.test

[pc]

My testnet witness is blocked at block 6693517. I have tried 3 times and failed. is there any others as me.

Blocked in what way?

At around that time a load test was run, which means the blocks were huge. This can lead to problems if you're trying to sync on a slow connection.

Keep an eye on the block log and the corresponding index file. As long as they are growing your node is still alive. It'll speed up once you are past the large blocks.

[kimziv]

My testnet witness is blocked at block 6693517. I have tried 3 times and failed. is there any others as me.

[gordo]

My witness node has been created and running. @xeroc, could you please vote me in?
Witness account:  witness-still

[startail]

My Testnet witness has been activated, kindly asking @xeroc to vote me in.

Witness: sc-bitshares-testnet

[pc]

A hardfork has been scheduled on testnet for friday 2017-09-15 12:00:00 UTC.

Changes:

* BSIP-0018 https://github.com/bitshares/bitshares-core/pull/340
* Improved startup time https://github.com/bitshares/bitshares-core/pull/339
* Fix for early withdrawal claims https://github.com/bitshares/bitshares-core/pull/23
* Fix for bug in vote evaluation https://github.com/bitshares/bitshares-core/pull/369
* Fix to prohibit voting for non-existant entities https://github.com/bitshares/bitshares-core/pull/348
* Some API changes https://github.com/bitshares/bitshares-core/pull/352 https://github.com/bitshares/bitshares-core/pull/344 https://github.com/bitshares/bitshares-core/pull/347 https://github.com/bitshares/bitshares-core/pull/330 https://github.com/bitshares/bitshares-core/pull/311 https://github.com/bitshares/bitshares-core/pull/312 https://github.com/bitshares/bitshares-core/pull/306 https://github.com/bitshares/bitshares-core/pull/304
* new option --plugins for run-time selection of active plugins https://github.com/bitshares/bitshares-core/pull/288
* Fix for the "no blocks to pop" message during shutdown https://github.com/bitshares/bitshares-core/pull/336
* Fix for transaction signing in cli_wallet https://github.com/bitshares/bitshares-core/pull/321
* Improved error logging https://github.com/bitshares/bitshares-core/pull/332
* Get rid of broken flat_index https://github.com/bitshares/bitshares-core/pull/335
* Fix for blockchain crash https://github.com/bitshares/bitshares-core/pull/324

@witnesses this will be our test run for the hardfork on mainnet. Please create witness nodes on testnet and ask xeroc to vote you in.

Edit: forgot to mention the tag... https://github.com/bitshares/bitshares-core/tree/test-2.0.170909

[sahkan]

Looks right, I voted for your witness. I checked on my witness and it was stuck on"

Code: [Select]

762234ms th_a       application.cpp:523           handle_block         ] Got block: #10791565 time: 2017-09-07T01:12:42 latency: 234 ms from: init3  irreversible: 10791555 (-10)I have to restart and resync.

I found the issue, will fix it and have it back online today.

The node shut down because my storage went to 100%. The P2P file filled my drive reporting this error:

Code: [Select]

2017-09-07T03:39:51       p2p:accept_loop          accept_loop ] 0: 0 node.cpp:4192
2017-09-07T03:39:51       p2p:accept_loop   destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:286
2017-09-07T03:39:51       p2p:accept_loop   destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:286
2017-09-07T03:39:51       p2p:accept_loop          accept_loop ] 0 exception: unspecified
Too many open files
    {"message":"Too many open files"}
    asio  asio.cpp:60 error_handler
Unable to accept connection on socket.
    {}


[pc]

I think xeroc accidentally created a fork when he turned on his block producers without syncing first.
On my node, the last correct block was 10775881, but last irreversible was 10775883.

Solution: truncate your block db's index to 10775881 * 32 bytes and set a checkpoint:
checkpoint = [10775882, "00a46d4ad4fc72f0385ee5fda67155fd8d2cb7f9"]

Then replay.

[sahkan]

Looks right, I voted for your witness. I checked on my witness and it was stuck on"

Code: [Select]

762234ms th_a       application.cpp:523           handle_block         ] Got block: #10791565 time: 2017-09-07T01:12:42 latency: 234 ms from: init3  irreversible: 10791555 (-10)I have to restart and resync.

I found the issue, will fix it and have it back online today.

[sahkan]

Looks right, I voted for your witness. I checked on my witness and it was stuck on"

Code: [Select]

762234ms th_a       application.cpp:523           handle_block         ] Got block: #10791565 time: 2017-09-07T01:12:42 latency: 234 ms from: init3  irreversible: 10791555 (-10)I have to restart and resync.

[wackou]

anyone has the hash of a recent block? I think I always end up on a minority fork (re-synced twice already), although close to 100% with mostly the init witnesses...

here's what I got:

Code: [Select]

info
{
  "head_block_num": 10806310,
  "head_block_id": "00a4e42671894c00043e33f98551e3e3e21b499f",
  "head_block_age": "8 seconds old",
  "next_maintenance_time": "2 minutes in the future",
  "chain_id": "39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447",
  "participation": "91.40625000000000000",
  "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.23"
  ],

[sahkan]

As you might have noticed already, the seed node broke and the network for some reason split into two parts with me signing blocks on my majority "fork". This is interesting but I expected this to happen as we basically have a pretty weak p2p network. Those of you that are running the network, please resync the whole chain if you get errors while pushing blocks.
The seed node should be up again any moment.

To prevent this from happening again, I would like to request more SEED nodes to be added to the `testnet` code base.
Please consider setting up a seed node on the testnet (by opening up the p2p-node setting to 0.0.0.0:PORT) and send a pull request for this part of the code
https://github.com/bitshares/bitshares-core/blob/testnet/libraries/app/application.cpp#L163-L166
or send a mail to

   testnet@lists.bitshares.foundation

Thanks!!

Yep, will do. I am also short on votes after the restart.

[paliboy]

It seems reasonable to require all active witnesses on main net to be also active on test net, wdyt?