Closed fomosapiens closed 7 years ago
this worked for me http://ethereum.stackexchange.com/questions/11852/how-can-i-find-etc-nodes-to-pass-their-enode-uri-to-reserved-peers-because-t
not sure how this can be updated more efficiently at the mist level but this stuff should be automated or improved.
f2cc34d34e1df41317de0ce613a201d1660a788a03e2: leveldb: not found I0310 16:16:08.063688 p2p/discover/table.go:473] Bonding 48e063a6cf5f335b: known=false, fails=0 age=413648h1 I0310 16:16:08.064688 p2p/discover/table.go:473] Bonding ffea3b01c000cdd8: known=false, fails=0 age=413648h1 I0310 16:16:08.064688 p2p/discover/table.go:473] Bonding 217ebe27e89bf4fe: known=false, fails=0 age=413648h1 I0310 16:16:08.066688 p2p/discover/udp.go:453] >>> 159.203.255.59:30303 discover.ping I0310 16:16:08.064688 p2p/discover/table.go:473] Bonding 921cf8e4c345fe8d: known=false, fails=0 age=413648h1 I0310 16:16:08.066688 p2p/discover/udp.go:453] >>> 188.138.1.237:30303 discover.ping I0310 16:16:08.065688 p2p/discover/table.go:473] Bonding fa20444ef991596c: known=false, fails=0 age=413648h1 I0310 16:16:08.065688 p2p/discover/table.go:473] Bonding 687be94c3a7beaa3: known=false, fails=0 age=413648h1 I0310 16:16:08.066688 p2p/discover/udp.go:453] >>> 51.255.49.170:30303 discover.ping I0310 16:16:08.065688 p2p/discover/table.go:473] Bonding ee3da491ce6a155e: known=false, fails=0 age=413648h1 I0310 16:16:08.067688 p2p/discover/udp.go:453] >>> 50.149.116.182:30303 discover.ping I0310 16:16:08.065688 p2p/discover/table.go:473] Bonding 6e538e7c1280f0a3: known=false, fails=0 age=413648h1 I0310 16:16:08.067688 p2p/discover/udp.go:453] >>> 91.121.65.179:40404 discover.ping I0310 16:16:08.066688 p2p/discover/udp.go:453] >>> 128.199.93.177:3030 discover.ping I0310 16:16:08.064688 p2p/discover/table.go:473] Bonding ca5ae4eca09ba678: known=false, fails=0 age=413648h1 I0310 16:16:08.065688 p2p/discover/table.go:473] Bonding 4bd6a4df3612c718: known=false, fails=0 age=413648h1 I0310 16:16:08.067688 p2p/discover/udp.go:453] >>> 95.183.51.229:30303 discover.ping I0310 16:16:08.065688 p2p/discover/table.go:473] Bonding e809c4a2fec7daed: known=false, fails=0 age=413648h1 I0310 16:16:08.064688 p2p/discover/table.go:473] Bonding 08c7ee6a4f861ff0: known=false, fails=0 age=413648h1 I0310 16:16:08.068689 p2p/discover/udp.go:453] >>> 71.178.232.20:30304 discover.ping I0310 16:16:08.068689 p2p/discover/udp.go:453] >>> 138.68.1.16:30303 discover.ping I0310 16:16:08.069689 p2p/discover/udp.go:453] >>> 45.32.7.81:30303 discover.ping I0310 16:16:08.069689 p2p/discover/udp.go:453] >>> 174.112.32.157:30303 discover.ping I0310 16:16:08.067688 p2p/discover/udp.go:453] >>> 52.206.67.235:30303 discover.ping I0310 16:16:08.568717 p2p/discover/table.go:389] no seed nodes found I0310 16:16:08.568717 p2p/server.go:469] <-taskdone: discovery lookup I0310 16:16:08.568717 p2p/server.go:430] new task: discovery lookup I0310 16:16:09.932795 eth/downloader/downloader.go:1512] Quality of service: rtt 20s, conf 1.000, ttl 1m0s
System information
Please check the already existing issues to keep duplicates at a minimum.
Furthermore several work-arounds have been collected in the Mist-Troubleshooting-Guide.
If possible add the following to your report:
Screenshots
Check the console, of Mist (
CTRL/CMD + ALT + i
) and take a screenshotLog files (Go to
menu -> accounts -> backup -> application data
and upload as zip-archive):~/Library/Application Support/Mist/node.log
%APPDATA%/Roaming/Mist/node.log
~/.config/Mist/node.log