Test Net for Advanced Users

[mudshark79]

Restarted my node and seem to be back on chain:

Code: [Select]

get_dynamic_global_properties
{
  "id": "2.1.0",
  "random": "35ece2ef7aac03b97de7c75e54830f57d2c8100c",
  "head_block_number": 64591,
  "head_block_id": "0000fc4f697a5655e44786cfea52ab4c6025ea86",
  "time": "2015-08-21T12:46:15",
  "current_witness": "1.6.85",
  "next_maintenance_time": "2015-08-21T12:50:00",
  "witness_budget": 51808059,
  "accounts_registered_this_interval": 0,
  "recently_missed_count": 0,
  "dynamic_flags": 0
}
Seems like the main issue I'm having is that I'm not getting enough connections.  If every node is only getting one or two connections, and running lower performance servers, it could be forking from latency issues.  How many connections are other people getting?

I've never seen more than 5 or 6 and Abit and me saw issues connecting our nodes for no apparent reason. At the moment this is the connection count:


root@localhost:~/graphene/programs/cli_wallet# netstat -tuapen | grep "witness"
tcp        0      0 176.221.43.130:33323    0.0.0.0:*               LISTEN      0          150060      21758/witness_node
tcp        0      0 127.0.0.1:8090          0.0.0.0:*               LISTEN      0          150065      21758/witness_node
tcp        0      0 176.221.43.130:33323    176.9.234.167:36713     ESTABLISHED 0          269002      21758/witness_node
tcp        0      0 127.0.0.1:8090          127.0.0.1:50714         ESTABLISHED 0          388908      21758/witness_node
tcp        0      0 176.221.43.130:33323    104.156.226.183:51054   ESTABLISHED 0          204158      21758/witness_node
tcp        0      0 176.221.43.130:33323    70.114.143.108:47834    ESTABLISHED 0          373346      21758/witness_node
tcp        0      1 176.221.43.130:33323    104.156.226.183:49584   SYN_SENT    0          383968      21758/witness_node
tcp        0      0 176.221.43.130:33323    216.252.204.69:51525    ESTABLISHED 0          150127      21758/witness_node
tcp        0      0 176.221.43.130:33323    107.167.187.88:55405    ESTABLISHED 0          221553      21758/witness_node
udp        0      0 0.0.0.0:54304           0.0.0.0:*                           0          150054      21758/witness_node

[mudshark79]

Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

you can vote me in to test @ betaxtrade

Meanwhile you're in it seems.

[Troglodactyl]

Restarted my node and seem to be back on chain:

Code: [Select]

get_dynamic_global_properties
{
  "id": "2.1.0",
  "random": "35ece2ef7aac03b97de7c75e54830f57d2c8100c",
  "head_block_number": 64591,
  "head_block_id": "0000fc4f697a5655e44786cfea52ab4c6025ea86",
  "time": "2015-08-21T12:46:15",
  "current_witness": "1.6.85",
  "next_maintenance_time": "2015-08-21T12:50:00",
  "witness_budget": 51808059,
  "accounts_registered_this_interval": 0,
  "recently_missed_count": 0,
  "dynamic_flags": 0
}
Seems like the main issue I'm having is that I'm not getting enough connections.  If every node is only getting one or two connections, and running lower performance servers, it could be forking from latency issues.  How many connections are other people getting?

[bytemaster]

The seed node crashed in the P2P code due to an assert exception.

https://github.com/cryptonomex/graphene/issues/260

The annoying thing is that this is the same P2P code BitShares is using without issue! 

I am rebuilding it in release mode where the assert statement will not be there.   Hopefully that will prevent it from crashing. 

The blockchain is still alive and well on block #64497 at the time of this writing.   It is clear that there is something very wrong with fork handling.  We are attempting to work out ways to reproduce this easily because it hasn't happened in our own performance tests.

[Troglodactyl]

Looks like my node fell off the chain over the night, probably because I never got more than one peer connection consistently.

Code: [Select]

get_dynamic_global_properties
{
  "id": "2.1.0",
  "random": "e96759cb979ef4620404d4a116c64d4e6b9bd0e8",
  "head_block_number": 43793,
  "head_block_id": "0000ab110f83c3641467c59ae7daec0c26e9537d",
  "time": "2015-08-21T06:35:29",
  "current_witness": "1.6.72",
  "next_maintenance_time": "2015-08-21T06:40:00",
  "witness_budget": 95817007,
  "accounts_registered_this_interval": 0,
  "recently_missed_count": 0,
  "dynamic_flags": 0
}

Code: [Select]

2344668ms p2p        node.cpp:4404                 dump_node_status     ] ----------------- PEER STATUS UPDATE --------------------
2344668ms p2p        node.cpp:4407                 dump_node_status     ]  number of peers: 1 active, 0, 0 closing.  attempting to maintain 20 - 200 peers
2344668ms p2p        node.cpp:4412                 dump_node_status     ]        active peer 45.55.6.216:1776 peer_is_in_sync_with_us:true we_are_in_sync_with_peer:true
2344668ms p2p        node.cpp:4425                 dump_node_status     ] --------- MEMORY USAGE ------------
2344668ms p2p        node.cpp:4426                 dump_node_status     ] node._active_sync_requests size: 0
2344669ms p2p        node.cpp:4427                 dump_node_status     ] node._received_sync_items size: 3588
2344669ms p2p        node.cpp:4428                 dump_node_status     ] node._new_received_sync_items size: 0
2344669ms p2p        node.cpp:4429                 dump_node_status     ] node._items_to_fetch size: 0
2344669ms p2p        node.cpp:4430                 dump_node_status     ] node._new_inventory size: 0
2344669ms p2p        node.cpp:4431                 dump_node_status     ] node._message_cache size: 2
2344669ms p2p        node.cpp:4434                 dump_node_status     ]   peer 45.55.6.216:1776
2344669ms p2p        node.cpp:4435                 dump_node_status     ]     peer.ids_of_items_to_get size: 0
2344669ms p2p        node.cpp:4436                 dump_node_status     ]     peer.inventory_peer_advertised_to_us size: 5
2344670ms p2p        node.cpp:4437                 dump_node_status     ]     peer.inventory_advertised_to_peer size: 104
2344670ms p2p        node.cpp:4438                 dump_node_status     ]     peer.items_requested_from_peer size: 0
2344670ms p2p        node.cpp:4439                 dump_node_status     ]     peer.sync_items_requested_from_peer size: 0
2344670ms p2p        node.cpp:4441                 dump_node_status     ] --------- END MEMORY USAGE ------------
2345990ms p2p        node.cpp:1340                 terminate_inactive_c ] Sending a keepalive message to peer 45.55.6.216:1776 who hasn't sent us any messages in the last 37 seconds

[betax]

Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

you can vote me in to test @ betaxtrade

[betax]

Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

[xeroc]

I am getting this error after a while:

Code: [Select]

10 assert_exception: Assert Exception
item->num < _head->num + MAX_BLOCK_REORDERING:
    {}
    th_a  fork_database.cpp:70 _push_block

    {"new_block":{"previous":"0000dc531bf16468f148ff973ac29a377c02b82a","timestamp":"2015-08-21T10:19:59","witness":"1.6.91","next_secret_hash":"10afef88b577df92e7c64e01c6813c57deece7f9","previous_secret":"1313e555ed2c3b697736fcb7daf888d53a347ec7","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f78b7eac30a0c237f3cc16ab454f6e51cce267538df0c462a76f7ce59204f55572da90894b55ff90d488b0341c4a885ac043f855d4405e9f243174c5ed0ad6041","transactions":[]}}
    th_a  db_block.cpp:176 _push_block


[ebit]

 

[mudshark79]

Code: [Select]

2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ]    my id is 2a9dd11186ee39434fc36139417a1a83ab671f79cc9a3d112f6c49f8302ccf02a1                  node.cpp:1626
2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ]         active: 176.221.43.130:33323 with 0a69dc25fca6f9e85284deda98c92a51bc0f659adfa976e017ebf61620ab32d2c1   [outbound]                       node.cpp:1633
...
2015-08-21T09:07:57 p2p:message read_loop           on_message ] handling message current_time_reply_message_type 6d669ff6f384895b812201eb0187f850f0bd8224 size 24 from peer 176.221.43.130:33323                       node.cpp:1651
...
2015-08-21T09:08:00 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 176.221.43.130:33323 because they didn't respond to my request for sync item ids after 0000000000000000000000000000000000000000                   node.cpp:1317


Code: [Select]

2015-08-21T09:08:04 p2p:p2p_network_connect_loop display_current_conn ]    handshaking: 176.221.43.130:33323 with 000000000000000000000000000000000000000000000000000000000000000000  [unknown]                 node.cpp:1640
2015-08-21T09:08:04   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 176.221.43.130:33323: 0 exception: unspecified
Cannot assign requested address
    {"message":"Cannot assign requested address"}
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255


OK, then I'm clueless. Sorry for confusing things, of course my logs will also reference your outgoing connections. I could look up the timestamp in my p2p-log but unfortunately now I'm already late for work and won't be able to check back until in 5 hours or so...

[alt]

 
good job abit, add oil

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

[abit]

Code: [Select]

2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ]    my id is 2a9dd11186ee39434fc36139417a1a83ab671f79cc9a3d112f6c49f8302ccf02a1                  node.cpp:1626
2015-08-21T09:07:54 p2p:p2p_network_connect_loop display_current_conn ]         active: 176.221.43.130:33323 with 0a69dc25fca6f9e85284deda98c92a51bc0f659adfa976e017ebf61620ab32d2c1   [outbound]                       node.cpp:1633
...
2015-08-21T09:07:57 p2p:message read_loop           on_message ] handling message current_time_reply_message_type 6d669ff6f384895b812201eb0187f850f0bd8224 size 24 from peer 176.221.43.130:33323                       node.cpp:1651
...
2015-08-21T09:08:00 p2p:terminate_inactive_connections_loop terminate_inactive_c ] Disconnecting peer 176.221.43.130:33323 because they didn't respond to my request for sync item ids after 0000000000000000000000000000000000000000                   node.cpp:1317


Code: [Select]

2015-08-21T09:08:04 p2p:p2p_network_connect_loop display_current_conn ]    handshaking: 176.221.43.130:33323 with 000000000000000000000000000000000000000000000000000000000000000000  [unknown]                 node.cpp:1640
2015-08-21T09:08:04   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 176.221.43.130:33323: 0 exception: unspecified
Cannot assign requested address
    {"message":"Cannot assign requested address"}
    asio  asio.cpp:59 error_handler                     peer_connection.cpp:255


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

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.

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

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. It seems to use a third node to check wether your port is open and reachable and it seems you don't pass this test ? 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?

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

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

Already set it as seed. Maybe it is just because of slow/unstable connection? The node is in China.