Connection: error calling OnConnect handler: connection auth error
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I've was playing with Keybase on Linux, but it is stuck when I'm trying to logout.
$ keybase logout -f
▶ WARNING (CONN foo bar) Connection: error calling OnConnect handler: connection auth error: msg: failed to check logged in status shouldRetry: false
▶ WARNING (CONN foo bar) Connection: error calling OnConnect handler: connection auth error: msg: failed to check logged in status shouldRetry: false
▶ WARNING (CONN foo bar) Connection: error calling OnConnect handler: connection auth error: msg: failed to check logged in status shouldRetry: false
I've tried to following, but it didn't work:
$ keybase service
▶ INFO Service#Run() exiting with error error locking /run/user/1000/keybase/keybased.pid: server already running (code 0)
▶ ERROR error locking /run/user/1000/keybase/keybased.pid: server already running
$ kill $(cat /run/user/1000/keybase/keybased.pid)
$ keybase service
▶ INFO Service#Run() exiting with error resource temporarily unavailable (code 0)
$ keybase logout
▶ INFO Starting keybase.service.
▶ WARNING (CONN foo bar) Connection: error calling OnConnect handler: connection auth error: msg: failed to check logged in status shouldRetry: false
This worked as workaround:
$ sudo apt-get install keybase
$ sudo apt install ~/Downloads/keybase_amd64.deb
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with keybase logout -f and keybase service on Linux, then inspect how the service handles /run/user/1000/keybase/keybased.pid and the reported connection authentication error. Done means logout completes without repeated OnConnect warnings or requiring package reinstallation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100