Bitcoin Forum
December 07, 2024, 03:27:10 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Multibit HD does not connect anymore, help !  (Read 1438 times)
doc12 (OP)
Legendary
*
Offline Offline

Activity: 1284
Merit: 1042


View Profile
July 11, 2015, 07:48:52 PM
Last edit: July 11, 2015, 10:51:28 PM by doc12
 #1

Hi,

my Multibit HD client does not find peers anymore. Two days ago it was all fine, computer was off since then.

Somebody has the same problem ?


Seems like the client tries to connect to seed.bitcoinstats.com and then a error occures.

OS Linux Mint 17.1:

Quote
[2015-07-11 22:45:46,344] DEBUG [safe-fixed-bitcoin-network-0] o.m.h.c.s.BitcoinNetworkService - Downloading block chain...
[2015-07-11 22:45:46,348] DEBUG [safe-fixed-bitcoin-network-0] o.m.h.c.s.BitcoinNetworkService - Starting blockchain download . . .
[2015-07-11 22:45:51,450] WARN  [PeerGroup Thread] o.b.n.d.MultiplexingDiscovery - Seed seed.bitcoinstats.com: failed to look up: org.bitcoinj.net.discovery.PeerDiscoveryException: java.net.UnknownHostException: seed.bitcoinstats.com: unknown error
[2015-07-11 22:45:51,450] WARN  [PeerGroup Thread] o.b.n.d.MultiplexingDiscovery - Seed seed.bitnodes.io: timed out
[2015-07-11 22:46:01,517] WARN  [PeerGroup Thread] o.b.n.d.MultiplexingDiscovery - Seed seed.bitcoinstats.com: failed to look up: org.bitcoinj.net.discovery.PeerDiscoveryException: java.net.UnknownHostException: seed.bitcoinstats.com
[2015-07-11 22:46:01,517] WARN  [PeerGroup Thread] o.b.n.d.MultiplexingDiscovery - Seed seed.bitnodes.io: timed out
jim618
Legendary
*
Offline Offline

Activity: 1708
Merit: 1066



View Profile WWW
July 12, 2015, 09:47:57 AM
 #2

Looks like network connectivity problems.

Can you ping the machines mentioned ?
I just pinged then successfully:

Code:
jims-macbook-91:multibit-commons jim$ ping seed.bitcoinstats.com
PING seed.bitcoinstats.com (128.199.107.63): 56 data bytes
64 bytes from 128.199.107.63: icmp_seq=0 ttl=46 time=455.668 ms
64 bytes from 128.199.107.63: icmp_seq=1 ttl=46 time=609.779 ms
64 bytes from 128.199.107.63: icmp_seq=2 ttl=46 time=440.006 ms
64 bytes from 128.199.107.63: icmp_seq=3 ttl=46 time=377.882 ms
64 bytes from 128.199.107.63: icmp_seq=4 ttl=46 time=741.916 ms
64 bytes from 128.199.107.63: icmp_seq=5 ttl=46 time=363.018 ms
^C
--- seed.bitcoinstats.com ping statistics ---
7 packets transmitted, 6 packets received, 14.3% packet loss
round-trip min/avg/max/stddev = 363.018/498.045/741.916/135.273 ms
jims-macbook-91:multibit-commons jim$ ping seed.bitnodes.io
PING seed.bitnodes.io (184.107.180.2): 56 data bytes
64 bytes from 184.107.180.2: icmp_seq=0 ttl=52 time=127.426 ms
64 bytes from 184.107.180.2: icmp_seq=1 ttl=52 time=126.821 ms
64 bytes from 184.107.180.2: icmp_seq=2 ttl=52 time=135.518 ms
^C
--- seed.bitnodes.io ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 126.821/129.922/135.518/3.965 ms

If not then it is most likely something to do with your local network.

MultiBit HD   Lightweight desktop client.                    Bitcoin Solutions Ltd   Bespoke software. Consultancy.
doc12 (OP)
Legendary
*
Offline Offline

Activity: 1284
Merit: 1042


View Profile
July 12, 2015, 01:32:11 PM
 #3

I'm also able to ping the machines and connect to them on port 8333.  

My network seems ok so far.  

Now and then the client connects to the network, but then I restart and it fails again...
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!