Skip to content

Mist finds no peers #214

@adamnovak

Description

@adamnovak

I've installed Mist with go get -u github.com/ethereum/go-ethereum/mist on Ubuntu 14.04. I can start it up just fine, but it can't find any peers.

My log looks like this:

anovak@hypernova:~/workspace/go/src/github.com/ethereum/go-ethereum/mist$ mist -seed=true -upnp -loglevel=5
2014/12/18 21:43:54 [CLI] identity created
2014/12/18 21:44:04 [SERV] UPnP failedwrite udp4: i/o timeout
2014/12/18 21:44:04 [STATE] (+) 51ba59315b3a95761d0863b05ccc7a7f54703d99
2014/12/18 21:44:04 [STATE] (+) e4157b34ea9615cfbde6b4fda419828124b70c78
2014/12/18 21:44:04 [STATE] (+) b9c015918bdaba24b4ff057a92a3873d6eb201be
2014/12/18 21:44:04 [STATE] (+) 6c386a4b26f73c802f34673f7248bb118f97424a
2014/12/18 21:44:04 [STATE] (+) cd2a3d9f938e13cd947ec05abc7fe734df8dd826
2014/12/18 21:44:04 [STATE] (+) 2ef47100e0787b915105fd5e3f4ff6752079d5cb
2014/12/18 21:44:04 [STATE] (+) e6716f9544a56c530d868e4bfbacb172315bdead
2014/12/18 21:44:04 [STATE] (+) 1a26338f0d905e295fccb71fa9ea849ffa12aaf4
2014/12/18 21:44:04 [CHAIN] Last block (#0) 08436a4d33c77e6acf013e586a3333ad152f25d31df8b68749d85046810e1f4b
2014/12/18 21:44:04 [CLI] Starting Mist/v0.6.7/linux/go1.2.1
2014/12/18 21:44:04 [REACTOR] started
2014/12/18 21:44:04 [STATE] Starting state manager
2014/12/18 21:44:04 [SERV] Ready and accepting connections
2014/12/18 21:44:04 [SERV] Retrieving seed nodes
2014/12/18 21:44:04 [REACTOR] added new subscription to newBlock
2014/12/18 21:44:04 [REACTOR] added new subscription to messages
2014/12/18 21:44:04 [SERV] Found DNS Go Peer:54.72.69.180:30303
2014/12/18 21:44:04 [SERV] Found DNS Bootstrap Peer:54.200.139.158:30303
2014/12/18 21:44:05 [SERV] Server started
2014/12/18 21:44:05 [REACTOR] added new subscription to newBlock
2014/12/18 21:44:05 [JSRE] started
2014/12/18 21:44:05 [PEER] (207.12.89.101:30303) <= Handshake [0 4d6973742f76302e362e372f6c696e75782f676f312e322e31 [657468] 765f d3298d1ea1616700dc8f478ac929bcc6e21e7513597e7b630849590279d83856aa04ba09f0fbee2816a11d862920275b116853ab55b7259623bb760436e26a65]
2014/12/18 21:44:05 plugin.cpp:52: 
WARNING: This project is using the experimental QML API extensions for QtWebKit and is therefore tied to a specific QtWebKit release.
WARNING: The experimental API will change from version to version, or even be removed. You have been warned!

2014/12/18 21:44:05 QtWebContext.cpp:68: Inspector server started successfully. Try pointing a WebKit browser to http://127.0.0.1:99999
2014/12/18 21:44:06 [STATE] (+) 876623607342b7c40563082e620afa50fe0352f4
2014/12/18 21:44:06 [REACTOR] added new subscription to newBlock
2014/12/18 21:44:06 [REACTOR] added new subscription to newTx:pre
2014/12/18 21:44:06 [REACTOR] added new subscription to newTx:post
2014/12/18 21:44:06 [REACTOR] added new subscription to chainSync
2014/12/18 21:44:06 [REACTOR] added new subscription to miner:start
2014/12/18 21:44:06 [REACTOR] added new subscription to miner:stop
2014/12/18 21:44:06 [REACTOR] added new subscription to object:
2014/12/18 21:44:06 [REACTOR] added new subscription to peerList
2014/12/18 21:44:06 [GUI] Starting GUI
2014/12/18 21:44:06 appmenuplatformmenubar.cpp:128: appmenu-qt: handleReparent 128 The given QWindow has no QMenuBar assigned

It doesn't say where it gets the 207.12.89.10 peer from (maybe it's the default one in the ctrl+p box?), but going in with Wireshark that's the only one it manages to connect to. And after connecting it gets an RST from the remote host--it must not like something about my handshake.

Am I running the wrong protocol version or something? How can I find peers that are up to date with the current trunk to test against?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions