Author Topic: 20160328cli-wallet Unable to sync up  (Read 3095 times)

0 Members and 1 Guest are viewing this topic.

Offline Fox

Damn the fat fingers. I'm glad to see this resolved.
Witness: fox

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
  • Built a new node from tag 2.0.160328 on Ubuntu 15.10
  • It builds fine, but does not sync the network
  • Used the two seed nodes provided by Xeroc above, but they fail to handshake:

Code: [Select]

2016-05-03T12:33:43   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 208.66.16.68:45967: 0 exception: unspecified

I'm unsure how to troubleshoot further.
Wrong port "208.66.16.68:45967", should be "208.66.16.68:35967" which is working.

By the way, it seems that all public seed nodes were down while you're testing. See https://bitsharestalk.org/index.php/topic,22385.new.html#new
BitShares committee member: abit
BitShares witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
not sure which one of them is actually the seed node port .. that's why I added both of them .. But I managed to sync them nicely with the parameters above ..

Offline Fox

  • Built a new node from tag 2.0.160328 on Ubuntu 15.10
  • It builds fine, but does not sync the network
  • Used the two seed nodes provided by Xeroc above, but they fail to handshake:

Code: [Select]
2016-05-03T12:33:43 p2p:thread invoke for method load_configuration   load_configuration ] generating new private key for this node                     node.cpp:4404
2016-05-03T12:33:43 p2p:thread invoke for method load_configuration trigger_p2p_network_ ] Triggering connect loop now                  node.cpp:988
2016-05-03T12:33:43 p2p:thread invoke for method add_node trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43 p2p:thread invoke for method connect_to_endpoint  connect_to_endpoint ] node_impl::connect_to_endpoint(208.66.16.68:43192)                  node.cp$
2016-05-03T12:33:43 p2p:thread invoke for method add_node trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43 p2p:thread invoke for method connect_to_endpoint  connect_to_endpoint ] node_impl::connect_to_endpoint(208.66.16.68:45967)                  node.cp$
2016-05-03T12:33:43 p2p:thread invoke for method add_node trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 208.66.16.68:43192: 0 exception: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:60 error_handler                     peer_connection.cpp:260
2016-05-03T12:33:43   p2p:connect_to_task display_current_conn ] Currently have 1 of [20/200] connections                       node.cpp:1731
2016-05-03T12:33:43   p2p:connect_to_task display_current_conn ]    my id is e1101e7df032cd84410e8344c0114e7b588b064fe7068e6e553e70d0c3d7bd77b5                 node.cp$
2016-05-03T12:33:43   p2p:connect_to_task display_current_conn ]    handshaking: 208.66.16.68:45967 with 00000000000000000000000000000000000000000000000000000000000000$
2016-05-03T12:33:43   p2p:connect_to_task trigger_p2p_network_ ] Triggering connect loop now                    node.cpp:988
2016-05-03T12:33:43   p2p:connect_to_task schedule_peer_for_de ] scheduling peer for deletion: 208.66.16.68:43192 (this will not block)                 node.cpp:1640
2016-05-03T12:33:43   p2p:connect_to_task schedule_peer_for_de ] asyncing delayed_peer_deletion_task to delete 1 peers                  node.cpp:1645
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task delayed_peer_deletio ] beginning an iteration of delayed_peer_deletion_task with 1 in queue                  node.cp$
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] calling close_connection()                    peer_connection.cpp:127
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] close_connection completed normally                   peer_connection.cpp:129
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] canceling _send_queued_messages task                  peer_connection.cpp:142
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] cancel_and_wait completed normally                    peer_connection.cpp:144
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] canceling accept_or_connect_task                      peer_connection.cpp:157
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task              destroy ] Unexpected exception from peer_connection's accept_or_connect_task : {"code":0,"name":"except$
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task   destroy_connection ] in destroy_connection() for                   message_oriented_connection.cpp:286
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task   destroy_connection ] in destroy_connection() for                   message_oriented_connection.cpp:286
2016-05-03T12:33:43 p2p:delayed_peer_deletion_task delayed_peer_deletio ] leaving delayed_peer_deletion_task                    node.cpp:1607
2016-05-03T12:33:43   p2p:connect_to_task           connect_to ] fatal: error connecting to peer 208.66.16.68:45967: 0 exception: unspecified

I'm unsure how to troubleshoot further.
Witness: fox

Offline Fox

I just built a node using the Microsoft Azure BaaS template (from source) and it failed to make properly:

Code: [Select]
...
[ 96%] Building CXX object tests/CMakeFiles/chain_test.dir/tests/operation_tests                                                                                        2.cpp.o
[ 97%] Building CXX object tests/CMakeFiles/chain_test.dir/common/database_fixtu                                                                                        re.cpp.o
/usr/local/bitshares-2/tests/common/database_fixture.cpp: In constructor ‘graphe                                                                                        ne::chain::database_fixture::database_fixture()’:
/usr/local/bitshares-2/tests/common/database_fixture.cpp:83:22: warning: compari                                                                                        son between signed and unsigned integer expressions [-Wsign-compare]
    for( int i = 0; i < genesis_state.initial_active_witnesses; ++i )
                      ^
Linking CXX executable chain_test
CMakeFiles/chain_test.dir/tests/basic_tests.cpp.o: file not recognized: File tru                                                                                        ncated
collect2: error: ld returned 1 exit status
tests/CMakeFiles/chain_test.dir/build.make:397: recipe for target 'tests/chain_t                                                                                        est' failed
make[2]: *** [tests/chain_test] Error 1
CMakeFiles/Makefile2:2443: recipe for target 'tests/CMakeFiles/chain_test.dir/al                                                                                        l' failed
make[1]: *** [tests/CMakeFiles/chain_test.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2

The complete build script can be found in the build_bitshares.sh file:
https://github.com/Azure/azure-quickstart-templates/tree/master/bitshares-ubuntu-vm
Witness: fox

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I noticed this today as well. Not sure if it is a problem with the seed nodes or the witness_node
try with
Code: [Select]
witness_node --seed-node 208.66.16.68:43192 --seed-node 208.66.16.68:35967

Offline freedom

  • Sr. Member
  • ****
  • Posts: 303
    • View Profile
Please check your connectivity or change the API server in the settings to another one
o,sorry,20160328witness_node unable to sync up
Is this a new build of the witness_node or one that was previously synced to the network? 

If previously synced, you may add --replay-blockchain to the command line sting. Further, if the database became corrupt, you may add --resync-blockchain and this will download from peers starting at block 0.
I tested on four computers. but the new build and previously synced network all unable to sync up。

cd "C:\Program Files\BitShares 2\bin"
witness_node.exe -s 104.200.28.117:61705 --rpc-endpoint 127.0.0.1:8090


ok now   :)

« Last Edit: May 03, 2016, 09:21:04 am by freedom »

Offline Fox

Please check your connectivity or change the API server in the settings to another one
o,sorry,20160328witness_node unable to sync up
Is this a new build of the witness_node or one that was previously synced to the network? 

If previously synced, you may add --replay-blockchain to the command line sting. Further, if the database became corrupt, you may add --resync-blockchain and this will download from peers starting at block 0.
Witness: fox

Offline freedom

  • Sr. Member
  • ****
  • Posts: 303
    • View Profile
Please check your connectivity or change the API server in the settings to another one
o,sorry,20160328witness_node unable to sync up

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Please check your connectivity or change the API server in the settings to another one

Offline freedom

  • Sr. Member
  • ****
  • Posts: 303
    • View Profile
20160328cli-wallet unable to sync up