Here is my theory:
Current testnet is too centralized.
Because the init node have about 90% of active witnesses, if it didn't receive a block produced by other witness (networking issue or so), most time next slot is the init node itself, so it just produce one, and next, next, next, certainly it will be the longest chain. That's why the network is 'robust', but it's not true, it's not safe, we can say we're encountering 51% attack indeed.

Quote from: mudshark79 on August 21, 2015, 08:46:54 am

Quote from: abit on August 21, 2015, 08:45:31 am

Quote from: mudshark79 on August 21, 2015, 08:44:03 am

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..

I see things like this in reference to your ip:

Code: [Select]

2015-08-21T08:46:31 p2p:message read_loop forward_firewall_che ] forwarding firewall check for node 114.92.254.159:63542 to peer 176.9.234.167:58896                node.cpp:3301
2015-08-21T08:46:32 p2p:message read_loop on_check_firewall_re ] Peer 176.9.234.167:58896 reports firewall check status unable_to_connect for 114.92.254.159:63542  node.cpp:3394
2015-08-21T08:46:32 p2p:message read_loop         send_message ] peer_connection::send_message() enqueueing message of type 5015 for peer 114.92.254.159:63542      peer_connection.cpp:365
2015-08-21T08:46:32 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:32 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:32 p2p:p2p_network_connect_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                     node.cpp:1633
2015-08-21T08:46:32 p2p:p2p_network_connect_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                     node.cpp:1633
2015-08-21T08:46:32 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:33 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:33 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:33 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:33 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:33 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:33 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:33 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:33 p2p:message read_loop display_current_conn ]         active: 114.92.254.159:63542 with 9732257b913c2a994ae08ee742ec20c25848a8cb9e88c2aa963fc7ee8e2b40fef9   [inbound]                    node.cpp:1633
2015-08-21T08:46:34 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:34 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:36 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:36 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:37 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:37 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:38 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:38 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:39 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:39 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:40 p2p:message read_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                 peer_connection.cpp:479
2015-08-21T08:46:40 p2p:advertise_inventory_loop  clear_old_inventory ] Expiring old inventory for peer 114.92.254.159:63542: removing 0 items advertised to peer (0 left), and 0 advertised to us (0 left)                  peer_connection.cpp:479
2015-08-21T08:46:41 p2p:message read_loop on_connection_closed ] Remote peer 114.92.254.159:63542 closed their connection to us                 node.cpp:2724
2015-08-21T08:46:41 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 114.92.254.159:63542 (this will not block)


Those line with firewall sounds like there is some potentail for being blacklisted. ON the other hand it clearly states you are not blocked.

Do you know it is on purpose that the port changes everytime one fires up the node? Have you already tried moving to fixed port?

I have two nodes running, both have fixed p2p port, one is 62015 and the other is 60002.
Nodes might have been introducing correct p2p-ports to other peers for inbound connection, but may use other ports for outbound connection.

//Edit: I enabled NAT for 62015 but not for 60002. That's why some firewall tests failed.

Quote from: abit on August 21, 2015, 08:18:13 am

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.
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.

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.

Back online now.

Try connecting to 176.221.43.130:33323, that's where all the blocks I get seem to be coming from, so I'm guessing that's my peer with lowest latency to the rest of the network.

Yes that's one.
And puppies' node 45.55.6.216:1776
But it's hard for my node to connect to them.

The seed node down?
$ telnet 104.236.51.238 1776
Trying 104.236.51.238...
telnet: Unable to connect to remote host: Connection refused