-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/keybase mount, on linux, behaves poorly - hangs ls /
#26864
Comments
Can confirm this is the case. It also causes all Flatpaks to hang or not start at all while Keybase is running. |
I also believe that this same issue causes |
Same issue on Ubuntu 24.04 I need to start keybase -> kill it -> umount /keybase -> run keybase again |
Ah. Interesting. I have one server still on Ubuntu 22.04.4. For a while now (a few weeks?), there has been an issue in mounting What happens when you do a In my case, I get the following: × keybase-redirector.service - Keybase Root Redirector for KBFS
Loaded: loaded (/usr/lib/systemd/user/keybase-redirector.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-06-05 13:00:14 WEST; 53s ago
Process: 1199828 ExecStartPre=/usr/bin/keybase --use-root-config-file config get --direct --assert-false --assert-ok-on-nil disable-root-redirector (code=exited, status=2)
CPU: 41ms
Jun 05 13:00:14 myServer systemd[1093]: keybase-redirector.service: Scheduled restart job, restart counter is at 5.
Jun 05 13:00:14 myServer systemd[1093]: Stopped Keybase Root Redirector for KBFS.
Jun 05 13:00:14 myServer systemd[1093]: keybase-redirector.service: Start request repeated too quickly.
Jun 05 13:00:14 myServer systemd[1093]: keybase-redirector.service: Failed with result 'exit-code'.
Jun 05 13:00:14 myServer systemd[1093]: Failed to start Keybase Root Redirector for KBFS. The journal is not very informative, either (
My quick hack was to turn it off, and simply look for my files at |
Keybase reliably causes
ls /
to hang.ls /
-> hangsudo ls /
-> oksudo ls -l /
-> hangsudo strace -l /
-> hang, atstatx(..., "/keybase",...)
Additionally, when I "Quit Keybase", which is unreasonably hidden and discouraged, echoes of dark pattern fashion, it doesn't clean up the mount, and the same issue still occurs!
Start with debugging
[sudo] systemctl status keybase*
->keybase.mount
is the only systemd service installed.$ sudo systemctl status keybase.mount ● keybase.mount - /keybase Loaded: loaded (/proc/self/mountinfo) Active: active (mounted) since Wed 2024-05-15 13:31:38 PDT; 1h 22min ago Where: /keybase What: keybase-redirector CPU: 8ms
After quitting keybase, not merely closing it, the
keybase.mount
is still mounted, but now throws errors,Resolve this with
systemctl stop keybase.mount
, only after keybase has been quit.System Information
The text was updated successfully, but these errors were encountered: