keybase / bot-sshca

A chat bot that can manage your team's SSH accounts
BSD 3-Clause "New" or "Revised" License
222 stars 30 forks source link

timeout issues #90

Closed blaggacao closed 4 years ago

blaggacao commented 4 years ago

Looks like on RPI appliances the arbitrary timeout of 3 seconds is not always enough to get up all services correctly. Therefore the might fail.

I therefore suggest to inspect health and readiness of kbfsfuse and keybase service rather than relying on the timeout. And if they don't expose health parameters modify those libraries so that they do.

blaggacao commented 4 years ago

Oho, it even seems as if keybase itself is not checking for proper background service setup, see:

2020-04-17T20:18:23.010001Z ▶ [INFO keybase fork_server.go:74] 001 Starting background server with pid=39
2020-04-17T20:18:27.029891Z ▶ [ERRO keybase main.go:87] 002 dial unix /home/keybase/.config/keybase/keybased.sock: connect: connection refused
Logged in and ready!
2020-04-17T20:18:29.095781Z ▶ [ERRO keybase main.go:87] 001 dial unix /home/keybase/.config/keybase/keybased.sock: connect: connection refused

keybase version: Client: 5.3.1

blaggacao commented 4 years ago

trying to fix this: https://github.com/jitesoft/docker-keybase-sshca/issues/2#issuecomment-615456547