search

keybase / client

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

Cannot look up any keybase.io hostnames #3139

Open djmitche opened 8 years ago

djmitche commented 8 years ago 
dustin@ramanujan ~ $ keybase id wcosta
▶ ERROR API network error: Get https://api.keybase.io/_/api/1.0/user/lookup.json?fields=basics%2Cpublic_keys%2Cpictures&multi=1&username=wcosta: dial tcp: lookup api.keybase.io: No address associated with hostname (error 1601)

any operation I preform gives me this sort of error.

dustin@ramanujan ~ $ keybase version
Client:  1.0.16
Service: 1.0.16
dustin@ramanujan ~ $ host api.keybase.io
api.keybase.io has address 54.84.82.15

I'm guessing something in the go resolver is failing? I have seen this on many networks now.

cjb commented 8 years ago

Thanks for the report! I've never seen anything like this. If it's reproducible, do you think you could.. I don't know.. use strace/wireshark to see which DNS server Go is asking and what response it's getting? I'm not sure how else we can investigate, but maybe someone else here will have ideas.

keybase id wcosta is working for me at the moment.

cjb commented 8 years ago

Are you on OS X?

Mac OS X NOTICE The host command does not use the host name and address resolution or the DNS query routing mechanisms used by other processes running on Mac OS X. The results of name or address queries printed by host may differ from those found by other processes that use the Mac OS X native name and address resolution mechanisms. The results of DNS queries may also differ from queries that use the Mac OS X DNS routing library.

It sounds like you might have a busted libc resolver, but a working "host" command because it doesn't use the same mechanism. I think it's likely to be a local machine issue.

Does ping api.keybase.io work? That one uses the libc resolver AIUI.

djmitche commented 8 years ago

No, not on OS X. And ping and host both use the same (system) resolver, so ping works.

I didn't see anything when stracing the client. Stracing the server only showed futex calls. However, restarting the server seems to have fixed this.

Let's see if that changes when the server finds itself on a new network, maybe?

Dustin

Pablohn26 commented 8 years ago

I guess it is due to you are logged out into keybase with graphical interface (maybe an upgrade, timeout or cache was not gotten). I had also this error:

▶ ERROR API network error: doRetry failed, attempts: 6, timeout 11.390625s, last err: Get https://api.keybase.io/_/api/1.0/sesscheck.json: dial tcp: lookup api.keybase.io: No address associated with hostname (error 1601)

when running

keybase follow somebody

and graphical interface showed me I was logged out. While the error, keybase CLI status was:

0 pablo:1@~$ keybase status
Username:      pablohn
Logged in:     yes
Session:       no session
    is valid:  yes
    keys:      locked

Key status:
    stream:    not cached
    secret:    not stored
    dev sig:   not cached
    dev enc:   not cached
    paper sig: not cached
    paper enc: not cached
    prompt:    show
    tsec:      not cached

KBFS:
    status:    running
    version:   1.0.2-20161003160026+feb9d3a
    log:       /home/pablo/.cache/keybase/keybase.kbfs.log

Service:
    status:    running
    version:   1.0.17-20161003160026+ecdaf34
    log:       /home/pablo/.cache/keybase/keybase.service.log

Updater:
    log:       /home/pablo/.cache/keybase/keybase.updater.log

Platform Information:
    OS:        linux
    OS vers:   Linux 4.7.5-200.fc24.x86_64 x86_64-"Fedora release 24 (Twenty Four)"
    Runtime:   go1.7
    Arch:      amd64

Client:
    version:   1.0.17-20161003160026+ecdaf34

Desktop app:
    status:    running
    version:   1.0.17-20161003160026+ecdaf34
    log:       /home/pablo/.cache/keybase/Keybase.app.log

Config path:   /home/pablo/.config/keybase/config.json
Default user:  pablohn
Other users:   

command-line client:
    keybase status [pid: 3077, version: 1.0.17-20161003160026+ecdaf34]

desktop:
    /opt/keybase/Keybase [pid: 2231, version: 1.0.17-20161003160026+ecdaf34, description: Main Thread]
    /opt/keybase/Keybase --type=renderer --no-sandbox --primordial-pipe-token=A802B787CE2187C4968A4B22C7E26F6A --lang=en-US --node-integration=true --hidden-page --enable-pinch --num-raster-threads=4 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --disable-accelerated-video-decode --mojo-channel-token=EAAC9E70E8A018D3CBC6F4DC15B0D314 --mojo-application-channel-token=74599E4C59DB71C1FB0BD76073849652 --channel=2231.1.1971547278 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd [pid: 2597, version: 1.0.17-20161003160026+ecdaf34, description: Menubar]
    /opt/keybase/Keybase --type=renderer --no-sandbox --primordial-pipe-token=BA4139A9CCCA1EDDC867F7460E6B2C7E --lang=en-US --node-integration=true --hidden-page --enable-pinch --num-raster-threads=4 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --disable-accelerated-video-decode --mojo-channel-token=7F660E14575B6423A7394FEB59E38A69 --mojo-application-channel-token=E7A687FEA696845FFC1FC414E4B4674D --channel=2231.2.737045363 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd [pid: 2601, version: 1.0.17-20161003160026+ecdaf34, description: Main Renderer]

KBFS:
    kbfsfuse -debug -log-to-file /keybase [pid: 2230, version: 1.0.2-20161003160026+feb9d3a]

and I could not log in on graphical interface dropping me the same error. I exited keybase GUI and once I started again it was automatically logged in, working (I could follow a person) and with next keybase status

0 pablo:1@~$ keybase status
Username:      pablohn
Logged in:     yes

Device:
    name:      MSI-laptop
    ID:        63b87ad8e0f77c9f0fcd7b0b4c807118
    status:    active

Session:       no session
    is valid:  yes
    keys:      unlocked

Key status:
    stream:    not cached
    secret:    stored
    dev sig:   cached
    dev enc:   cached
    paper sig: not cached
    paper enc: not cached
    prompt:    show
    tsec:      not cached

KBFS:
    status:    running
    version:   1.0.2-20161003160026+feb9d3a
    log:       /home/pablo/.cache/keybase/keybase.kbfs.log

Service:
    status:    running
    version:   1.0.17-20161003160026+ecdaf34
    log:       /home/pablo/.cache/keybase/keybase.service.log

Updater:
    log:       /home/pablo/.cache/keybase/keybase.updater.log

Platform Information:
    OS:        linux
    OS vers:   Linux 4.7.5-200.fc24.x86_64 x86_64-"Fedora release 24 (Twenty Four)"
    Runtime:   go1.7
    Arch:      amd64

Client:
    version:   1.0.17-20161003160026+ecdaf34

Desktop app:
    status:    running
    version:   1.0.17-20161003160026+ecdaf34
    log:       /home/pablo/.cache/keybase/Keybase.app.log

Config path:   /home/pablo/.config/keybase/config.json
Default user:  pablohn
Other users:   

command-line client:
    keybase status [pid: 3724, version: 1.0.17-20161003160026+ecdaf34]

desktop:
    /opt/keybase/Keybase [pid: 3592, version: 1.0.17-20161003160026+ecdaf34, description: Main Thread]
    /opt/keybase/Keybase --type=renderer --no-sandbox --primordial-pipe-token=78290ED32E6BBCA84E945754C73E4547 --lang=en-US --node-integration=true --hidden-page --enable-pinch --num-raster-threads=4 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --disable-accelerated-video-decode --mojo-channel-token=C70F14828FCB48C3E20C5755AA270163 --mojo-application-channel-token=98A568302F59F4540A0C7CAAD263F08B --channel=3592.1.169574561 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd [pid: 3657, version: 1.0.17-20161003160026+ecdaf34, description: Menubar]
    /opt/keybase/Keybase --type=renderer --no-sandbox --primordial-pipe-token=C91F562FA46CB8C3D764BC3CFD211A53 --lang=en-US --node-integration=true --hidden-page --enable-pinch --num-raster-threads=4 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --disable-accelerated-video-decode --mojo-channel-token=4C891FF8A2AC05D0D1D60A25A42E931C --mojo-application-channel-token=787B3E7ECABEBFA436551E646640781D --channel=3592.2.919869501 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd [pid: 3661, version: 1.0.17-20161003160026+ecdaf34, description: Main Renderer]

KBFS:
    kbfsfuse -debug -log-to-file /keybase [pid: 3591, version: 1.0.2-20161003160026+feb9d3a]

I hope broken status and working status give a clue to developers. To workaround, just exit keybase GUI client and run it again.

I left this gist with today logs (workaround was applied around 13:50). If personal information is leaked please let me know and I will find another way to post the information.