Skip to content

Scheduled Shutdown Should Not Shutdown If There Are Active SSH Connections #3191

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.

Sign up for GitHub

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

Jump to bottom
Closed
Mainstay-Noah-Huppert opened this issue Jul 25, 2022 · 5 comments
Closed

Scheduled Shutdown Should Not Shutdown If There Are Active SSH Connections #3191

Mainstay-Noah-Huppert opened this issue Jul 25, 2022 · 5 comments

Comments

@Mainstay-Noah-Huppert
Copy link
Contributor

I was working on my Coder workspace instance which is scheduled to shut down at 5:00 PM. Right as 5:00 PM came by my editor froze up and my SSH terminal closed its connection.

In the future I will give myself an extra hour in the schedule to prevent this. But I feel like if I have established an SSH connection via the Coder CLI and it is still open the instance should not shut down.
@Mainstay-Noah-Huppert
Copy link
Contributor Author

Coder server v0.7.12

@Mainstay-Noah-Huppert
Copy link
Contributor Author

image

@bpmct
Copy link
Member

bpmct commented Jul 25, 2022 •
edited
Loading

We're considering a different model for autostop which stops the workspace after n hours of inactivity, or keeps a workspace alive, despite a schedule being present: #2995. What do you think of this?

@Mainstay-Noah-Huppert
Copy link
Contributor Author

That could be good. I do like the schedule so that my workspace doesn't shut down during lunch or during a meeting heavy day. Mainly because there are some development tasks (👀 webpack) that take a few minutes to start up with a big app. So having the workspace up and the tasks already running saves time. Additionally having the scheduled start at 9:00 AM is nice because I know that by the time I start dev work after standup all those tasks will be running and good to go.

For my particular use case I think being able to configure only having keep alive functionality and not inacitvity shutdown would be nice.

@ammario ammario mentioned this issue Jul 26, 2022
Closed
@ammario
Copy link
Member

ammario commented Jul 26, 2022

@Mainstay-Noah-Huppert thank you for the feedback. Let's move the discussion here.

@ammario ammario closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@misskniss @ammario @bpmct @Mainstay-Noah-Huppert