search

keybase / client

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

[KBFS] ls: cannot open directory '.': Input/output error #3668

Open emilstahl opened 8 years ago

emilstahl commented 8 years ago 
emil@hostname:/keybase/private/another,user,emilstahl$ ls
ls: cannot open directory '.': Input/output error

my log id: 6f9af43d7306171b5f51361c

cjb commented 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?

cjb commented 8 years ago

(To be more precise: either you don't track them, or some of their proofs have broken since you first tracked them.)

emilstahl commented 8 years ago

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 😄

emilstahl commented 8 years ago

I just ran run_keybasenow 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

cjb commented 8 years ago

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.)

strib commented 8 years ago

Hi @emilstahl, thanks for the report. In your log it looks like KBFS has started three times. With local timestamps:

  1. 2016-07-29 18:03:47.043887
    • During this run, your local device keys weren't unlocked. Presumably because you didn't run 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.
  2. 2016-07-29 19:09:20.442259
    • During this run, you had the same authentication problem until about 19:20:50, when the keys became unlocked (looks like you entered your secret key at that point). Once this happened, it seemed like you were able to create and edit files for a while, up until the end of this run.
    • I can't tell why this run ended. It doesn't appear to have been a crash caused by code inside the KBFS binary, since nothing weird appears in the log. As @cjb said, maybe there is a clue in your dmesg? Something killed the process in an unkind way.
  3. 2016-07-29 20:18:02.726514
    • Here again you had the authentication problem, I assume because you did 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.

maxtaco commented 8 years ago

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

strib commented 8 years ago

Thanks for the clarification. By "login/unlock" I meant either/or, but that wasn't very clear, not both; sorry.