Skip to content
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

Graceful timeouts if slave becomes unresponsive #131

Open
briantully opened this issue Dec 6, 2022 · 0 comments
Open

Graceful timeouts if slave becomes unresponsive #131

briantully opened this issue Dec 6, 2022 · 0 comments
Labels
feature-request Unaccepted feature request

Comments

@briantully
Copy link

Feature request

I find that teleport tends to hang when waking up my slave machine, where if the slave freezes, the master also becomes unresponsive and there's no way to force quit teleport on the master machine.

Steps to reproduce:

On master, move cursor to edge of screen to control slave machine. Master machine shows the bezel "Mac Pro - Pasteboard sent", however the slave machine is frozen (doesn't fully wake from sleep). At that point both machines are unresponsive and there is no way to force quit teleport or retake control of the cursor on the master machine. I have to force reboot my slave machine which takes several minutes. During the reboot, teleport on the master still thinks it is controlling the slave machine and is unresponsive. The only time the master machine becomes responsive is when the slave machine is fully rebooted and teleport is loaded on the slave machine.

Ideally there would be some kind of timeout setting for teleport, where it pings the remote host every X seconds, and if it doesn't get a response teleport will disconnect and give cursor control back to the master.

The motivation for the feature

I find myself repeatedly waiting long periods of time for teleport to relinquish control of an unresponsive slave machine, where both my machines are unresponsive.

How the feature would be relevant to at least 90% of Teleport users

I would imagine that this is a common issue?

What alternatives to the feature have been considered

None. I can't think of an alternative as I think the timeout/check needs to happen within teleport's networking connections.

@briantully briantully added the feature-request Unaccepted feature request label Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Unaccepted feature request
Projects
None yet
Development

No branches or pull requests

1 participant