Skip to content
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.

keybase-redirector doesn't die/reload after run_keybase #1510

Open
PresGas opened this issue Mar 11, 2018 · 5 comments
Open

keybase-redirector doesn't die/reload after run_keybase #1510

PresGas opened this issue Mar 11, 2018 · 5 comments
Labels

Comments

@PresGas
Copy link

PresGas commented Mar 11, 2018

On Debian/Ubuntu Linux, subsequent runnings of run_keybase results in more than one keybase-redirector.

Either the restart does not kill the child process or it just doesn't get cleaned up. No noticable performance issues, but could be problematic. Could it be because it is run as root and run_keybase is as a normal user?

rmday@cacodaemon:~$ ps -aux |grep keybase-redirector root 7870 0.0 0.0 759336 4592 ? Sl 09:33 0:00 keybase-redirector /keybase root 8155 0.0 0.0 685348 4260 ? Sl 09:33 0:00 keybase-redirector /keybase root 8383 0.0 0.0 609952 4304 ? Sl 09:34 0:00 keybase-redirector /keybase rmday 8819 0.0 0.0 14352 1068 pts/4 R+ 09:38 0:00 grep --color=auto keybase-redirector

Attaching log shortly.

@PresGas
Copy link
Author

PresGas commented Mar 11, 2018

Success! Your log ID is:

7241292499e970e279ca531c

@strib strib added the acked label Mar 11, 2018
@strib
Copy link
Contributor

strib commented Mar 11, 2018

Thanks, I'll look into it tomorrow. run_keybase is not supposed to kill one that's already running, but the new one it tries to start is supposed to stop on its own, leaving the original one running.

@PresGas
Copy link
Author

PresGas commented Mar 13, 2018

Anything else you need from me or testing subsequent releases, let me know.

@strib
Copy link
Contributor

strib commented Mar 13, 2018

No I'm good, just busy. lots of issues came in this weekend. This one is still in my queue, will get to it as soon as I can.

strib added a commit that referenced this issue Mar 14, 2018
Having an entry here will prevent other mounts from mounting over it,
since it will be non-empty.  That means future `run_keybase` calls
won't keep spinning up new redirector processes, due to the fact that
the running-as-root mount process sees an empty mountpoint.

For now, I just did the simplest thing: a symlink called
"KBFS_NOT_RUNNING" that points to /dev/null.  In the future, it might
be nice to have it point to a README file somewhere on disk, but that
would be a bigger undertaking.

Issue: #1510
strib added a commit that referenced this issue Mar 14, 2018
Having an entry here will prevent other mounts from mounting over it,
since it will be non-empty.  That means future `run_keybase` calls
won't keep spinning up new redirector processes, due to the fact that
the running-as-root mount process sees an empty mountpoint.

For now, I just did the simplest thing: a symlink called
"KBFS_NOT_RUNNING" that points to /dev/null.  In the future, it might
be nice to have it point to a README file somewhere on disk, but that
would be a bigger undertaking.

Issue: #1510
@strib
Copy link
Contributor

strib commented Mar 14, 2018

Should be fixed with #1511. Thanks for the report!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants