Open emilstahl opened 8 years ago
This is because you don't track the other users, and because you aren't running the GUI, the GUI can't ask you whether you want to track them.
You could run keybase track
on everyone you want to share with, to make the error go away.
It sounds like your problem with KBFS being unauthenticated went away somehow?
(To be more precise: either you don't track them, or some of their proofs have broken since you first tracked them.)
I just tried tracking them again (broken proofs).
However, suddenly I get this error: Transport endpoint is not connected
– on all folders, public or private.
I tried
keybase login
keybase unlock
keybase ctl restart
Log ID: e1f762f19ae19355b0e2831c
And yes, the other problem is resolved, my comment and close was not saved. It is now 😄
I just ran run_keybase
now I don't get the above error, but I can't list or edit files. Did not help to run keybase ctl restart
Log ID: 9938541c0e1421108f7bb31c
It's looking for your passphrase again.
If you get it working, do you think you could share your output of "dmesg" file with me (/keybase/private/cjb,you)? I don't think you should copy it here because it might have something sensitive in. But it looks like KBFS crashed so I'm wondering if there's anything about that in the dmesg log.
(You could also email the file to me.)
Hi @emilstahl, thanks for the report. In your log it looks like KBFS has started three times. With local timestamps:
keybase login
or keybase unlock
explicitly (due to your lack of GUI). Looks like a call to run_keybase
probably killed this run and restarted it right away.dmesg
? Something killed the process in an unkind way.keybase ctl restart
, which forgets your secret keys again. You would have need to do another login/unlock after the restart to get access again. (Sorry, we've definitely built this flow around the assumption that the GUI is running.)Hope this helps clear things up.
One note @strib: @patrickxb recently changed keybase login
to do what keybase unlock
was previously doing. So a keybase login
should solve all of these issues
Thanks for the clarification. By "login/unlock" I meant either/or, but that wasn't very clear, not both; sorry.
my log id: 6f9af43d7306171b5f51361c