Topic: Peer discovery failure, No peer discovery returned any results (Read 745 times)
same here been going on for days
December 12, 2016, 08:18:36 AM
Hi,
Multibit isn't connecting to the network. It sits for hours spamming into the log.
[2016-12-12 13:09:45,210] ERROR [PeerGroup Thread] o.b.c.PeerGroup - Peer discovery failure, class:org.bitcoinj.net.discovery.PeerDiscoveryException, message:No peer discovery returned any results: check internet connection?
My internet connection is wide open. I can connect to arbitrary sites on 8333 as http://portquiz.net:8333/ validates
Clients like bitcoin-qt find peers and connect just fine.
Digging what I believe to be the dnsseed entries (given the bitcoinj core source https://github.com/bitcoinj/bitcoinj/blob/master/core/src/main/java/org/bitcoinj/params/MainNetParams.java) gives results for some but not for others.
jon@whiptail:~$ dig seed.bitcoin.sipa.be
; <<>> DiG 9.9.5-9+deb8u8-Debian <<>> seed.bitcoin.sipa.be
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59266
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 8192
;; QUESTION SECTION:
;seed.bitcoin.sipa.be. IN A
;; AUTHORITY SECTION:
seed.bitcoin.sipa.be. 40000 IN SOA wps.sipa.be. sipa.ulyssis.org. 1481548541 604800 86400 2592000 604800
;; Query time: 40 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Dec 12 13:15:41 GMT 2016
;; MSG SIZE rcvd: 105
jon@whiptail:~$ dig dnsseed.bluematt.me
; <<>> DiG 9.9.5-9+deb8u8-Debian <<>> dnsseed.bluematt.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41079
;; flags: qr rd ra; QUERY: 1, ANSWER: 42, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 8192
;; QUESTION SECTION:
;dnsseed.bluematt.me. IN A
;; ANSWER SECTION:
dnsseed.bluematt.me. 60 IN A 91.107.64.143
dnsseed.bluematt.me. 60 IN A 91.240.141.169
dnsseed.bluematt.me. 60 IN A 94.209.99.88
dnsseed.bluematt.me. 60 IN A 104.163.144.6
dnsseed.bluematt.me. 60 IN A 104.255.64.3
dnsseed.bluematt.me. 60 IN A 106.172.156.135
dnsseed.bluematt.me. 60 IN A 108.44.238.26
dnsseed.bluematt.me. 60 IN A 109.201.183.125
dnsseed.bluematt.me. 60 IN A 111.217.187.232
dnsseed.bluematt.me. 60 IN A 121.254.173.23
dnsseed.bluematt.me. 60 IN A 123.57.37.201
dnsseed.bluematt.me. 60 IN A 138.68.91.138
dnsseed.bluematt.me. 60 IN A 149.56.19.212
dnsseed.bluematt.me. 60 IN A 162.249.6.109
dnsseed.bluematt.me. 60 IN A 173.22.198.249
dnsseed.bluematt.me. 60 IN A 173.51.177.2
dnsseed.bluematt.me. 60 IN A 174.119.223.16
dnsseed.bluematt.me. 60 IN A 176.215.0.66
dnsseed.bluematt.me. 60 IN A 178.175.129.18
dnsseed.bluematt.me. 60 IN A 178.238.224.242
dnsseed.bluematt.me. 60 IN A 182.149.158.208
dnsseed.bluematt.me. 60 IN A 192.99.224.132
dnsseed.bluematt.me. 60 IN A 209.188.18.142
dnsseed.bluematt.me. 60 IN A 5.199.130.228
dnsseed.bluematt.me. 60 IN A 23.94.247.149
dnsseed.bluematt.me. 60 IN A 24.56.190.76
dnsseed.bluematt.me. 60 IN A 24.148.52.93
dnsseed.bluematt.me. 60 IN A 46.17.103.64
dnsseed.bluematt.me. 60 IN A 46.101.197.155
dnsseed.bluematt.me. 60 IN A 47.17.59.108
dnsseed.bluematt.me. 60 IN A 47.149.79.131
dnsseed.bluematt.me. 60 IN A 52.11.78.254
dnsseed.bluematt.me. 60 IN A 68.99.142.213
dnsseed.bluematt.me. 60 IN A 69.196.134.134
dnsseed.bluematt.me. 60 IN A 70.67.194.0
dnsseed.bluematt.me. 60 IN A 70.68.73.137
dnsseed.bluematt.me. 60 IN A 73.3.202.189
dnsseed.bluematt.me. 60 IN A 79.201.100.118
dnsseed.bluematt.me. 60 IN A 80.223.134.5
dnsseed.bluematt.me. 60 IN A 82.1.62.112
dnsseed.bluematt.me. 60 IN A 85.25.109.4
dnsseed.bluematt.me. 60 IN A 86.238.131.227
;; Query time: 168 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Dec 12 13:16:43 GMT 2016
;; MSG SIZE rcvd: 720
So what, exactly, is Multibits problem? Is it trying the first (seed.bitcoin.sipa.be) and giving up? Why isn't it connecting? Are there any command line options I can give that'll force it to try a certain IP as a peer so I can bootstrap it manually past something that's breaking?
Help?
Could any devs here please comment as this is a huge problem. I've got bitcoins in this wallet and need to be able to spend them and can't cos it isn't connecting to the network.
Multibit isn't connecting to the network. It sits for hours spamming into the log.
[2016-12-12 13:09:45,210] ERROR [PeerGroup Thread] o.b.c.PeerGroup - Peer discovery failure, class:org.bitcoinj.net.discovery.PeerDiscoveryException, message:No peer discovery returned any results: check internet connection?
My internet connection is wide open. I can connect to arbitrary sites on 8333 as http://portquiz.net:8333/ validates
Clients like bitcoin-qt find peers and connect just fine.
Digging what I believe to be the dnsseed entries (given the bitcoinj core source https://github.com/bitcoinj/bitcoinj/blob/master/core/src/main/java/org/bitcoinj/params/MainNetParams.java) gives results for some but not for others.
jon@whiptail:~$ dig seed.bitcoin.sipa.be
; <<>> DiG 9.9.5-9+deb8u8-Debian <<>> seed.bitcoin.sipa.be
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59266
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 8192
;; QUESTION SECTION:
;seed.bitcoin.sipa.be. IN A
;; AUTHORITY SECTION:
seed.bitcoin.sipa.be. 40000 IN SOA wps.sipa.be. sipa.ulyssis.org. 1481548541 604800 86400 2592000 604800
;; Query time: 40 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Dec 12 13:15:41 GMT 2016
;; MSG SIZE rcvd: 105
jon@whiptail:~$ dig dnsseed.bluematt.me
; <<>> DiG 9.9.5-9+deb8u8-Debian <<>> dnsseed.bluematt.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41079
;; flags: qr rd ra; QUERY: 1, ANSWER: 42, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 8192
;; QUESTION SECTION:
;dnsseed.bluematt.me. IN A
;; ANSWER SECTION:
dnsseed.bluematt.me. 60 IN A 91.107.64.143
dnsseed.bluematt.me. 60 IN A 91.240.141.169
dnsseed.bluematt.me. 60 IN A 94.209.99.88
dnsseed.bluematt.me. 60 IN A 104.163.144.6
dnsseed.bluematt.me. 60 IN A 104.255.64.3
dnsseed.bluematt.me. 60 IN A 106.172.156.135
dnsseed.bluematt.me. 60 IN A 108.44.238.26
dnsseed.bluematt.me. 60 IN A 109.201.183.125
dnsseed.bluematt.me. 60 IN A 111.217.187.232
dnsseed.bluematt.me. 60 IN A 121.254.173.23
dnsseed.bluematt.me. 60 IN A 123.57.37.201
dnsseed.bluematt.me. 60 IN A 138.68.91.138
dnsseed.bluematt.me. 60 IN A 149.56.19.212
dnsseed.bluematt.me. 60 IN A 162.249.6.109
dnsseed.bluematt.me. 60 IN A 173.22.198.249
dnsseed.bluematt.me. 60 IN A 173.51.177.2
dnsseed.bluematt.me. 60 IN A 174.119.223.16
dnsseed.bluematt.me. 60 IN A 176.215.0.66
dnsseed.bluematt.me. 60 IN A 178.175.129.18
dnsseed.bluematt.me. 60 IN A 178.238.224.242
dnsseed.bluematt.me. 60 IN A 182.149.158.208
dnsseed.bluematt.me. 60 IN A 192.99.224.132
dnsseed.bluematt.me. 60 IN A 209.188.18.142
dnsseed.bluematt.me. 60 IN A 5.199.130.228
dnsseed.bluematt.me. 60 IN A 23.94.247.149
dnsseed.bluematt.me. 60 IN A 24.56.190.76
dnsseed.bluematt.me. 60 IN A 24.148.52.93
dnsseed.bluematt.me. 60 IN A 46.17.103.64
dnsseed.bluematt.me. 60 IN A 46.101.197.155
dnsseed.bluematt.me. 60 IN A 47.17.59.108
dnsseed.bluematt.me. 60 IN A 47.149.79.131
dnsseed.bluematt.me. 60 IN A 52.11.78.254
dnsseed.bluematt.me. 60 IN A 68.99.142.213
dnsseed.bluematt.me. 60 IN A 69.196.134.134
dnsseed.bluematt.me. 60 IN A 70.67.194.0
dnsseed.bluematt.me. 60 IN A 70.68.73.137
dnsseed.bluematt.me. 60 IN A 73.3.202.189
dnsseed.bluematt.me. 60 IN A 79.201.100.118
dnsseed.bluematt.me. 60 IN A 80.223.134.5
dnsseed.bluematt.me. 60 IN A 82.1.62.112
dnsseed.bluematt.me. 60 IN A 85.25.109.4
dnsseed.bluematt.me. 60 IN A 86.238.131.227
;; Query time: 168 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Dec 12 13:16:43 GMT 2016
;; MSG SIZE rcvd: 720
So what, exactly, is Multibits problem? Is it trying the first (seed.bitcoin.sipa.be) and giving up? Why isn't it connecting? Are there any command line options I can give that'll force it to try a certain IP as a peer so I can bootstrap it manually past something that's breaking?
Help?
Could any devs here please comment as this is a huge problem. I've got bitcoins in this wallet and need to be able to spend them and can't cos it isn't connecting to the network.
Jump to: