[Public Testnet] testnet.bitshares.eu

[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]

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

[startail]

My Testnet witness has been activated, kindly asking [member=120]xeroc[/member] to vote me in.

Witness: sc-bitshares-testnet

[gordo]

My witness node has been created and running. [member=120]xeroc[/member], could you please vote me in?
Witness account:  witness-still

[kimziv]

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

[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 has been activated, kindly asking [member=120]xeroc[/member] to vote me in.

Witness: witness.yao.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.

[boombastic]

[member=120]xeroc[/member] my witness is ready, please throw some votes this way.

Code: [Select]

agsexplorer-test

[crazybit]

finally syned the blocks, pls help to vote(crazybit.witness) in on testnet.

[startail]

So, in less than 24 hours we will activate the new hard fork on BitShares.

To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.

My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?

[pc]

So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.

My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?

Using a release build is fine. If you feel capable of doing debugging in case of an emergency you can build in "RelWithDebInfo" mode, which will activate optimizations but still create debugging symbols.

[startail]

So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

Obviously

[Harvey]

delegate-oraclechain (1.6.57) is ready on the testnet, votes will be really appreciated. ^^

Code: [Select]

get_witness delegate-oraclechain
{
  "id": "1.6.57",
  "witness_account": "1.2.3670",
  "last_aslot": 0,
  "signing_key": "TEST5hwhHZz21NkuGZDgKBFTNf8HSL6wond3S1TWQ3JDMAaFAJAkkP",
  "vote_id": "1:88",
  "total_votes": 998994119,
  "url": "delegate-oraclechain",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

[freedom]

my witness freedom-t is ready, pls help to vote in on testnet.

freedom-t
"id": "1.6.59"