Test Net for Advanced Users

[abit]

My node crashed while generating a block. 
No interesting info found in logs.
Will launch in gdb this time.

Did you have
-DCMAKE_BUILD_TYPE=Debug
while building? Mine is commenting on everything quite detailed about everything in the console....

Yes I think I have.

Code: [Select]

cmake -DBOOST_ROOT="/app/boost_1_57_0.bin" -DCMAKE_BUILD_TYPE=Debug .
But the 'crash' last time looks like a clean exit. No info at all.

[mudshark79]

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...

Mine is 114.92.254.159:62015 or other ports.

Try 176.221.43.130:33323 as seed... if not already doing so. Will have a look if I see reference to your ip somewhere..

[abit]

Yes it's alive nonstop. Which is your node? I see some coming and going in netstat, maybe your's is somehow blacklisted or so...

Mine is 114.92.254.159:62015 or other ports.

[mudshark79]

Hey Everyone,

Just got back "Online". 10 AM in the morning. Seems most of you are in the western hemisphere....
However, I also don't see original seed-node "104.236.51.238:1776" anymore (but I think it already left when i went to bed), my node on port 33323 doesn't seem to have major issues (at least not like the last times) and is now running ~10h nonstop. Here's some error grepped from my p2p log rigth now:

Code: [Select]

2015-08-21T08:22:23 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:22:23"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":153,"method":"writesome","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":264,"method":"send_message","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"unable to send message","data":{}}]}.  Closing connection.                     peer_connection.cpp:303



and then

Code: [Select]

2015-08-21T08:26:38   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.156.226.183:58884: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:38 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:38"},"format":"${message} ","data":{"message":"Operation canceled"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.236.255.53:36548: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.236.51.238:1776: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.131.205.149:44815: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158

So it seems it is complaining about some peer-nodes not online anymore...
To be more precise these nodes seem to online and offline. I can see them in netstat but they seem to have changed the port because they have been restarted without a fixed p2p-prt in the config? Maybe it's a good idea to fix that port or not? Is the networking part supoosed to sort this out or is it even for a purpose that the ports change everytime you restart your node?

Hi, is the chain still alive? I'm stuck at about a hour ago and unable to connect right now.

Yes it's alive nonstop. Which is your node? Try 176.221.43.130:33323 as a seed.

[mudshark79]

My node crashed while generating a block. 
No interesting info found in logs.
Will launch in gdb this time.

Did you have
-DCMAKE_BUILD_TYPE=Debug
while building? Mine is commenting on everything quite detailed about everything in the console....

[abit]

Hey Everyone,

Just got back "Online". 10 AM in the morning. Seems most of you are in the western hemisphere....
However, I also don't see original seed-node "104.236.51.238:1776" anymore (but I think it already left when i went to bed), my node on port 33323 doesn't seem to have major issues (at least not like the last times) and is now running ~10h nonstop. Here's some error grepped from my p2p log rigth now:

Code: [Select]

2015-08-21T08:22:23 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:22:23"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":153,"method":"writesome","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":264,"method":"send_message","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"unable to send message","data":{}}]}.  Closing connection.                     peer_connection.cpp:303



and then

Code: [Select]

2015-08-21T08:26:38   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.156.226.183:58884: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:38 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:38"},"format":"${message} ","data":{"message":"Operation canceled"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.236.255.53:36548: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.236.51.238:1776: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.131.205.149:44815: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158

So it seems it is complaining about some peer-nodes not online anymore...
To be more precise these nodes seem to online and offline. I can see them in netstat but they seem to have changed the port because they have been restarted without a fixed p2p-prt in the config? Maybe it's a good idea to fix that port or not? Is the networking part supoosed to sort this out or is it even for a purpose that the ports change everytime you restart your node?

Hi, is the chain still alive? I'm stuck at about a hour ago and unable to connect right now.

[mudshark79]

Hey Everyone,

Just got back "Online". 10 AM in the morning. Seems most of you are in the western hemisphere....
However, I also don't see original seed-node "104.236.51.238:1776" anymore (but I think it already left when i went to bed), my node on port 33323 doesn't seem to have major issues (at least not like the last times) and is now running ~10h nonstop. Here's some error grepped from my p2p log rigth now:

Code: [Select]

2015-08-21T08:22:23 p2p:send_queued_messages_task send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":37,"method":"operator()","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:22:23"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":153,"method":"writesome","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":264,"method":"send_message","hostname":"","thread_name":"p2p","timestamp":"2015-08-21T08:22:23"},"format":"unable to send message","data":{}}]}.  Closing connection.                     peer_connection.cpp:303



and then

Code: [Select]

2015-08-21T08:26:38   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.156.226.183:58884: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:38 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:38"},"format":"${message} ","data":{"message":"Operation canceled"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.236.255.53:36548: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.236.51.238:1776: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158
2015-08-21T08:26:42   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 104.131.205.149:44815: 0 exception: unspecified
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255
2015-08-21T08:26:42 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":59,"method":"error_handler","hostname":"","thread_name":"asio","timestamp":"2015-08-21T08:26:42"},"format":"${message} ","data":{"message":"Connection refused"}}]}                       peer_connection.cpp:158

So it seems it is complaining about some peer-nodes not online anymore...
To be more precise these nodes seem to online and offline. I can see them in netstat but they seem to have changed the port because they have been restarted without a fixed p2p-prt in the config? Maybe it's a good idea to fix that port or not? Is the networking part supoosed to sort this out or is it even for a purpose that the ports change everytime you restart your node?

[abit]

My node crashed while generating a block. 
No interesting info found in logs.
Will launch in gdb this time.

[betax]

I found some problems related to spam transactions.

1) In a normal node without block production, when spam transactions occurred (in my case 100 txs in few seconds), block sync stops for about 3 minutes.

2) In a witness node with block production, spam transactions caused witness node crash. In this case, I have to resync my witness node.

3) Only part of spam transactions are accepted. I sent a hundred transactions but only 9 out of 100 are shown.

Im rebuilding, was travelling yesterday,  once done I will do the same and confirm on my side.

[clayop]

I found some problems related to spam transactions.

1) In a normal node without block production, when spam transactions occurred (in my case 100 txs in few seconds), block sync stops for about 3 minutes.

2) In a witness node with block production, spam transactions caused witness node crash. In this case, I have to resync my witness node.

3) Only part of spam transactions are accepted. I sent a hundred transactions but only 9 out of 100 are shown.

[betax]

Docker is great thanks, but at the moment not for me as I might want to fiddle with the code , But if I spin up  more vms... that will be the way !

[cryptosile]

my witness is now producing blocks:

Code: [Select]

get_witness everydaycrypto
{
  "id": "1.6.5251",
  "witness_account": "1.2.27645",
  "vote_id": "1:5468",
  "url": "https://everydaycrypto.com"
....

get_dynamic_global_properties
{
  "id": "2.1.0",
  "random": "4fc3d0459cf6eb73a00a0a9f9128b83a46a7dfc3",
  "head_block_number": 42483,
...

Here are the commands I used to run this using docker... (you all are probably tired of the docker thing by now... I'm not sure it's even that useful, pretty much just a way to distribute binaries... but I've come this far and can't go back now!)

Code: [Select]

cd
mkdir test1
cd test1
wget https://github.com/cryptonomex/graphene/releases/download/test1/aug-20-test-genesis.json
cd ..
sudo docker run --net=host -it -d -v ~/test1:/test1 sile16/graphene-witness:test1 -d test1 --genesis-json /test1/aug-20-test-genesis.json -s "176.221.43.1:33323" --rpc-endpoint  "0.0.0.0:8090"
sudo docker run --net=host -it --rm sile16/graphene-cli:test1  --chain-id d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083

 
###In Graphene CLI
>>> set_password <pass>
>>> unlock <pass>
>>> import_key everydaycrypto <owner wif key>
>>> import_balance everydaycrypto [<balance wif key>] true
>>> upgrade_account everydaycrypto true
>>> create_witness everydaycrypto "https://everydaycrypto.com" true
>>> vote_for_witness everydaycrypto everydaycrypto true true
>>> dump_private_keys

#Kill witness the nice way via a control C,  docker kill container ID would work too but blows away graphene DB
#get container IDs
docker ps
docker attach aefe50505f89
^C     

#just docker kill the cli container
docker kill 3a8cbffabc5d

nano test1/config.ini      #set witness-id and private-keys items
sudo docker run --net=host -it -d -v ~/test1:/test1 sile16/graphene-witness:test1 -d test1 --genesis-json /test1/aug-20-test-genesis.json -s "104.236.51.238:1776" --rpc-endpoint  "0.0.0.0:8090" -s "45.55.6.216:1776"


[brainbug]

General question (since I could not find this elsewhere):

Is there a genuine place from where I can download "an up-to-date" BitShares blockchain? Setting up a new client is easy, but syncing it takes long and sometimes does not work such that the whole process needs to be repeated again and again (my slow little pc, c847/8gb, often has problems here and it takes days to re-sync/re-download the chain)... As such, it would be awesome to have an official and always "up-to-date" download link for the BitShares blockchain.

That said, my question is if such a download link is already there (and I could not find it), or would it be a great addition to the BitShare's homepage?

EDIT: Also 8gb ram seem sometimes not enough for a re-sync (using v0.9.2)... is that true? Did some one else make similar experiences?

I don't know if there is a download link for the blockchain.
8GB RAM is more than enough. If you're using Windows or Linux, try run  'bitshares_client' rather than GUI for initial syncing. After in-sync you can press ctrl+d to close it then open GUI.
Wish you good luck.

Thanks :-) It turned out that 8gb are not enough (using the Win7 v0.9.2 GUI-client) when syncing from scratch. So, I downloaded a blockchain found on the web (1.6gb compressed; July 2015). Using that "bootstrap", things worked flawlessly, consuming 4gb ram at max.

[abit]

Back online now.

[abit]

Did the chain ID change or am I on a fork?

test5 is a brand new data directory.

Code: [Select]

./witness_node -d test5 genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"


./witness_node -d test5 --genesis-json ...