Bug #3303
closed
Background arv-mount is crashing regularly on the VMs, yielding "Transport endpoint is not connected"
Description
Right now the shell VMs are set up to automatically prepare a Keep mount in $HOME/keep when the user logs in. Unfortunately, most users who try to use it are greeted with this error:
-bash: cd: keep: Transport endpoint is not connected
This means the underlying FUSE process (i.e., arv-mount) is no longer running. It should be, but apparently it's crashing. Please investigate the cause of these crashes and fix it.
For what it's worth, it looks like this might be related to persistence across logins. If the user makes a new Keep mount, it tends to stay alive for as long as they're logged in. It seems like trouble starts when they log out, log in again later, and try to use the mount again.
Updated by Brett Smith over 11 years ago
- Subject changed from Background arv-mount is crashing regularly on the VMs to Background arv-mount is crashing regularly on the VMs, yielding "Transport endpoint is not connected"
Updated by Brett Smith over 11 years ago
- Status changed from New to In Progress
- Assigned To set to Brett Smith
Updated by Brett Smith over 11 years ago
This is apparently an issue with the way we invoke arv-mount from the shell configuration. I can reproduce a similar issue by adding this to my .bashrc:
ping -i 60 google.com >/dev/null 2>&1 & disown
We're going to try invoking arv-mount with nohup and see if that helps. It does for this ping case.
Updated by Brett Smith over 11 years ago
- Status changed from In Progress to Resolved
Adding nohup to the startup script did fix the issue. This is now closed.