Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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.

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

IMPOTANT : daytona serve can not be stopped #1209

Open
bryans-go opened this issue Oct 8, 2024 · 5 comments
Open

IMPOTANT : daytona serve can not be stopped #1209

bryans-go opened this issue Oct 8, 2024 · 5 comments
Labels
bug Something isn't working never stale An issue that never goes stale

Comments

@bryans-go
Copy link
Contributor

Describe the bug
daytona serve becomes unstoppable

To Reproduce
Steps to reproduce the behavior:

  1. git clone daytona
  2. cd daytona and go run cmd/daytona/main.go serve
  3. see that the logs start
  4. now press ctrl+c . the logs will say stopping logs but they will not

Expected behavior
It should stop easily when ctrl+c is pressed

Screenshots

image
@bryans-go bryans-go added the bug Something isn't working label Oct 8, 2024
@bryans-go
Copy link
Contributor Author

bryans-go commented Oct 8, 2024 •
edited
Loading

demo.webm

@bryans-go bryans-go changed the title daytona serve can not be stopped IMPOTANT : daytona serve can not be stopped Oct 8, 2024
@Tpuljak Tpuljak added the never stale An issue that never goes stale label Oct 8, 2024
@Tpuljak
Copy link
Member

Tpuljak commented Oct 8, 2024

@bryans-go does this happen every time for you?

Also, do you have workspaces that you created but didn't remove?

@bryans-go
Copy link
Contributor Author

bryans-go commented Oct 8, 2024 •
edited
Loading

I'M on a new Linux machine. I have fresh installed kde neon

@bryans-go
Copy link
Contributor Author

@Tpuljak can you please suggest a quick solution to it

@Tpuljak
Copy link
Member

Tpuljak commented Oct 8, 2024

We're looking into it. For now, the easiest way to stop the server is netstat -plunt, find the daytona process (one that has ports 3986 or 3987) and stop it with kill -9 PID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working never stale An issue that never goes stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Tpuljak @bryans-go