keybase / keybase/client

Error on `keybase log send`

Open
#7,417 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

This is a very odd machine; for example, it’s been Migrated all the way back to the first PPC Mac minis. It’s running Server.app. My network environment is by no means stable over the last few days. Contact me @nopdotcom if you need details not appropriate for GH issues.

Keybase.app has a white, unresponsive window up.

nop@sunk-cost:~$ keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): YES
Enter feedback (or ENTER to send): songgao requested a log of devices calling RegisterForUpdate frequently. I'll do
 this for my two desktop systems. This is the second, sunk-cost.
Enter feedback (or ENTER to send):
▶ INFO ignoring error getting keybase status: API network error: doRetry failed, attempts: 1, timeout 7.5s, last err: Get https://api.keybase.io/_/api/1.0/sesscheck.json: dial tcp: lookup api.keybase.io: no such host (error 1601)
▶ INFO ignoring UI logs: GUI main process wasn't found


------------
Success! Your log ID is:

  248a116397b5bcfd5b44831c

Here's a URL to submit new bug reports containing this ID:

  https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%20248a116397b5bcfd5b44831c

Thanks!
------------

nop@sunk-cost:~$
$ host api.keybase.io strawman
Using domain server:
Name: strawman
Address: 172.16.0.1#53
Aliases:

api.keybase.io has address 54.84.82.15
$ host api.keybase.io
api.keybase.io has address 54.84.82.15
$ 

my log id: 248a116397b5bcfd5b44831c

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start at the keybase log send command entry point and reproduce the report while checking the shown DNS and API network errors; done means identifying why the command reports an error during status or UI-log collection and confirming log submission behavior under that condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.