Qtum-cli on Raspberry PI not sync



  • Hello all,

    I'm new in Qtum and raspberry. I follow tuto link text
    But now I have no sync with other node.
    My "cat ~/.qtum/debug.log" show me :
    "
    2018-08-28 06:49:01 Misbehaving: 39.108.127.44:3888 peer=4433 (0 -> 1)
    2018-08-28 06:49:01 ProcessMessages(reject, 42 bytes) FAILED peer=4433
    2018-08-28 06:49:01 ERROR: Requesting unset send version for node: 4434. Using 209
    "
    And this for all nodes.

    I already try to remove peer.dat in order to let qtum-cli recreate it but same problem.
    "qtum-cli getnetworkinfo" tell me :
    "connections": 0,
    and
    "name": "ipv4",
    "limited": false,
    "reachable": true,
    "proxy": "",
    "proxy_randomize_credentials": false

    and for information I already try to add new node (I see this in the forum)
    qtum-cli addnode 92.237.196.43:3888 add
    qtum-cli addnode 101.81.121.148:3888 add
    qtum-cli addnode 218.144.237.250:3888 add
    qtum-cli addnode 96.56.60.146:3888 add
    No result.

    Could you help me please
    (ps I'm not a big boss in linux command line so if you could detail , thx )



  • Hello @aniel,

    Make sure you are running at least version 0.15.2, which has some improvements for connectivity.

    Provided your RPi has a good connection with the Internet, you are on the right track with the addnode command. Try these values which are newer peers (as of August 2018). Copy and paste these as commands one at a time. You can put them all in one after another. The correct response is “null”, and then the wallet will try for a minute or two to connect with each one.

    addnode 35.197.138.163:3888 add
    addnode 35.195.206.119:3888 add
    addnode 120.77.44.105:3888 add
    addnode 35.200.159.68:3888 add
    addnode 73.143.249.155:3888 add
    addnode 35.226.31.206:3888 add
    addnode 35.200.130.53:3888 add
    addnode 35.192.54.161:3888 add
    addnode 35.189.91.155:3888 add
    addnode 35.231.140.221:3888 add
    addnode 96.56.60.146:3888 add
    addnode 45.32.27.157:3888 add
    addnode 59.6.70.65:3888 add

    Then wait 5 to 10 minutes to see if these work.



  • Hello JB ,

    I run an update yesterday now with qtum-cli -version i'm in "Qtum Core RPC client version mainnet-ignition-v0.15.3".

    I try to install qtum wallet on windows and during sync I checked node connected. Today I have connection: 1 in qtum-cli getinfo. only "82.64.XX.XX:3888" is working for the moment. (<=== Edit: i'm stupid ... it's myself )

    I add all your node to try. Do we have a methode tu purge all peer ( remove or rename peer.dat and restart ?)

    Thanks for your answer.
    (how can we know that qtum is currently in sync ?)

    (quick edit: exemple of return in debug.log:
    2018-08-29 11:43:52 ERROR: Requesting unset send version for node: 1049. Using 209
    2018-08-29 11:43:52 Misbehaving: 45.32.27.157:3888 peer=1049 (0 -> 1)
    2018-08-29 11:43:52 ProcessMessages(reject, 42 bytes) FAILED peer=1049

    and after some minutes
    2018-08-29 12:15:15 Misbehaving: 35.195.206.119:3888 peer=113 (0 -> 1)
    2018-08-29 12:15:15 ProcessMessages(reject, 42 bytes) FAILED peer=113
    2018-08-29 12:15:16 ERROR: Requesting unset send version for node: 112. Using 209
    2018-08-29 12:15:16 Misbehaving: 35.197.138.163:3888 peer=112 (0 -> 1)
    2018-08-29 12:15:16 ProcessMessages(reject, 42 bytes) FAILED peer=112
    2018-08-29 12:15:16 ERROR: Requesting unset send version for node: 114. Using 209
    2018-08-29 12:15:16 Misbehaving: 120.77.44.105:3888 peer=114 (0 -> 1)
    2018-08-29 12:15:16 ProcessMessages(reject, 42 bytes) FAILED peer=114
    2018-08-29 12:15:16 ERROR: Requesting unset send version for node: 116. Using 209
    2018-08-29 12:15:16 Misbehaving: 73.143.249.155:3888 peer=116 (0 -> 1)
    2018-08-29 12:15:16 ProcessMessages(reject, 42 bytes) FAILED peer=116
    2018-08-29 12:15:16 ERROR: Requesting unset send version for node: 117. Using 209
    2018-08-29 12:15:16 Misbehaving: 35.226.31.206:3888 peer=117 (0 -> 1)
    2018-08-29 12:15:16 ProcessMessages(reject, 42 bytes) FAILED peer=117
    2018-08-29 12:15:16 ERROR: Requesting unset send version for node: 115. Using 209
    2018-08-29 12:15:16 Misbehaving: 35.200.159.68:3888 peer=115 (0 -> 1)
    2018-08-29 12:15:16 ProcessMessages(reject, 42 bytes) FAILED peer=115
    2018-08-29 12:15:17 ERROR: Requesting unset send version for node: 120. Using 209
    2018-08-29 12:15:17 Misbehaving: 35.189.91.155:3888 peer=120 (0 -> 1)
    2018-08-29 12:15:17 ProcessMessages(reject, 42 bytes) FAILED peer=120
    2018-08-29 12:15:17 ERROR: Requesting unset send version for node: 119. Using 209
    2018-08-29 12:15:17 Misbehaving: 35.192.54.161:3888 peer=119 (0 -> 1)
    2018-08-29 12:15:17 ProcessMessages(reject, 42 bytes) FAILED peer=119
    2018-08-29 12:15:17 ERROR: Requesting unset send version for node: 118. Using 209
    2018-08-29 12:15:17 Misbehaving: 35.200.130.53:3888 peer=118 (0 -> 1)
    2018-08-29 12:15:17 ProcessMessages(reject, 42 bytes) FAILED peer=118
    2018-08-29 12:15:17 ERROR: Requesting unset send version for node: 121. Using 209
    2018-08-29 12:15:17 Misbehaving: 35.231.140.221:3888 peer=121 (0 -> 1)
    2018-08-29 12:15:17 ProcessMessages(reject, 42 bytes) FAILED peer=121
    2018-08-29 12:15:17 ERROR: Requesting unset send version for node: 122. Using 209
    2018-08-29 12:15:17 Misbehaving: 96.56.60.146:3888 peer=122 (0 -> 1)
    2018-08-29 12:15:17 ProcessMessages(reject, 42 bytes) FAILED peer=122
    2018-08-29 12:15:18 ERROR: Requesting unset send version for node: 123. Using 209
    2018-08-29 12:15:18 Misbehaving: 45.32.27.157:3888 peer=123 (0 -> 1)
    2018-08-29 12:15:18 ProcessMessages(reject, 42 bytes) FAILED peer=123
    2018-08-29 12:15:18 ERROR: Requesting unset send version for node: 124. Using 209
    2018-08-29 12:15:18 Misbehaving: 59.6.70.65:3888 peer=124 (0 -> 1)
    2018-08-29 12:15:18 ProcessMessages(reject, 42 bytes) FAILED peer=124

    )



  • Hello Aniel,

    Deleting the peers.dat file is a good way to start over with peer connections, especially if you haven’t run the wallet for several weeks (all the peers carefully saved in the peers.dat file will be older).

    This is a strange error. When peers reach out to connect they exchange their wallet version number, like 0.15.3. They can comfortably communicate with older versions just fine. For this error the source code comment is

    // The send version should always be explicitly set to
    // INIT_PROTO_VERSION rather than using this value until SetSendVersion
    // has been called.
    

    I’m not sure, but the error seems to be saying your wallet can’t set its version number properly. Are you using a config file?

    Try deleting the peers.dat file and restarting the wallet. Also please check the section "Debug.log File for Network Events"
    and the appendix of this blog for the normal log events related to starting the wallet and making peer connections. Do you see this log info in your log file when you restart the wallet?

    https://medium.com/@jb395official/qtum-peer-connections-may-21-2018-ba12bda71e4f



  • Hello Jb

    Thanks for your help, I have the same idea yesterday. so after my work I take a second SD card and install another raspbian on it.
    I put the last version 0.15.3 and my saved-wallet.dat. After install, 23 connections.

    So I think that I'll will save my new wallet.dat in order to install (again) on my new SD card samsung endurance (64Go).

    Thanks for your help.


Log in to reply
 

Looks like your connection to QTUM was lost, please wait while we try to reconnect.