search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.88k stars 1.23k forks source link

Keybase error log after unsuccessful opening. #7044

Open simonforget opened 7 years ago

simonforget commented 7 years ago

Error message appeared in Notification Center (macOS Sierra). Failed to start Keybase after graceful stop. Not sure if the following file contains the same log information as the one that just been automatically uploaded. Keybase user: @simonforget.

201705181359_KeybaseErrorLog.txt

2017-05-18_16-53-45

my log id: 437690ada1862c08dec5ae1c

strib commented 7 years ago

Hi @simonforget, looks like you can't connect to our servers:

2017-05-18T16:51:44.538679-04:00 ▶ [WARN kbfs(BSR) connection.go:395] 46d1 (CONN BlockServerRemotePut 049d0a30) Connection: error dialing transport: dial tcp: lookup bserver.kbfs.keybase.io: no such host
2017-05-18T16:51:44.538772-04:00 ▶ [WARN kbfs(BSR) connection.go:560] 46d2 BlockServerRemotePut: connection error: dial tcp: lookup bserver.kbfs.keybase.io: no such host; retrying in 2s

Maybe you're behind a firewall that needs to whitelist our servers?

simonforget commented 7 years ago

Hi Jeremy,

It’s the very first time this happens since I use Keybase. Firewall configuration is fine on my end. I’m using TunnelBear to anonymize all my public IP traffic from this workstation.

Here is the current route table of my workstation.

Destination Gateway Flags Refs Use Netif Expire 0/1 172.18.10.117 UGSc 18 0 utun2 default 172.31.201.1 UGSc 6 2 en0 17 172.31.201.1 UGSc 4 0 en0 127 localhost UCS 0 0 lo0 localhost localhost UH 25 11202474 lo0 128.0/1 172.18.10.117 UGSc 6 0 utun2 162.243.231.207/32 172.31.201.1 UGSc 1 0 en0 169.254 link#4 UCS 0 0 en0 172.18.10.1/32 172.18.10.117 UGSc 1 0 utun2 172.18.10.117 172.18.10.118 UHr 28 0 utun2 172.31.201/24 link#4 UCS 5 0 en0 172.31.201.1/32 link#4 UCS 1 0 en0 172.31.201.1 0:d:b9:35:8f:44 UHLWIir 9 519 en0 389 172.31.201.6 30:5:5c:bb:3a:af UHLWI 0 48 en0 488 172.31.201.8 6c:f3:7f:ce:b2:98 UHLWI 0 750 en0 1177 172.31.201.144/32 link#4 UCS 0 0 en0 172.31.201.210 6c:f3:7f:ce:b2:98 UHLWI 0 0 en0 554 172.31.201.220 d0:3:4b:2e:86:41 UHLWIi 1 1812 en0 620 172.31.201.255 ff:ff:ff:ff:ff:ff UHLWbI 0 5 en0 224.0.0/4 link#4 UmCS 2 0 en0 224.0.0.251 1:0:5e:0:0:fb UHmLWI 0 0 en0 239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 1112 en0 255.255.255.255/32 link#4 UCS 1 0 en0 broadcasthost ff:ff:ff:ff:ff:ff UHLWbI 0 7 en0

I’ll try tonight to set a split tunnel tonight, although I’m not sure how to do it for Keybase specifically.

Keep up your good work,

Simon Forget simon.forget@davm.ca

Le 18 mai 2017 à 17:14, Jeremy Stribling notifications@github.com a écrit :

Hi @simonforget https://github.com/simonforget, looks like you can't connect to our servers:

2017-05-18T16:51:44.538679-04:00 ▶ [WARN kbfs(BSR) connection.go:395] 46d1 (CONN BlockServerRemotePut 049d0a30) Connection: error dialing transport: dial tcp: lookup bserver.kbfs.keybase.io: no such host 2017-05-18T16:51:44.538772-04:00 ▶ [WARN kbfs(BSR) connection.go:560] 46d2 BlockServerRemotePut: connection error: dial tcp: lookup bserver.kbfs.keybase.io: no such host; retrying in 2s Maybe you're behind a firewall that needs to whitelist our servers??

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/7044#issuecomment-302543727, or mute the thread https://github.com/notifications/unsubscribe-auth/AHBa6RxAm7wi6c2zRSj8ZkmXl__h0Hjzks5r7LTFgaJpZM4NfzTe.

strib commented 7 years ago

Ok, thanks for the info. I have no idea why you can't connect. Specifically, the error message above seems related to DNS, so you might want to try something like ping bserver.kbfs.keybase.io to see if you can even resolve the name.

(By the way, there are no logs ever automatically uploaded, you always need to run keybase log send explicitly.)

simonforget commented 7 years ago

The only reason that I can think of to explain this problem is a short DNS downtime at TunnelBear.

I am able to ping the Keybase server.

Diva:~ sforget$ ping bserver.kbfs.keybase.io
PING bserver-elb-207251293.us-east-1.elb.amazonaws.com (52.5.236.99): 56 data bytes
64 bytes from 52.5.236.99: icmp_seq=0 ttl=239 time=26.862 ms
64 bytes from 52.5.236.99: icmp_seq=1 ttl=239 time=28.800 ms
64 bytes from 52.5.236.99: icmp_seq=2 ttl=239 time=28.381 ms
64 bytes from 52.5.236.99: icmp_seq=3 ttl=239 time=29.081 ms
64 bytes from 52.5.236.99: icmp_seq=4 ttl=239 time=28.284 ms
64 bytes from 52.5.236.99: icmp_seq=5 ttl=239 time=27.319 ms

These aren't the greatest latency I've seen but way better than other online services.

Thanks for the precision about the logs.