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

[Bug]: The server stopped responding to certain requests after starting to terminate an instance #1241

Closed
peterschmidt85 opened this issue May 17, 2024 · 0 comments · Fixed by #1251
Labels
bug Something isn't working

Comments

@peterschmidt85
Copy link
Contributor

No certain steps to reproduce.

Once, when terminating an instance, the server stopped responding to certain requests.

The last server logs:

{
    "message": "run(22afe2)curly-robin-1: run status has changed PROVISIONING -> TERMINATING",
    "logger": "dstack._internal.server.background.tasks.process_runs",
    "timestamp": "2024-05-17 13:47:13,146",
    "level": "INFO"
}

After that, there were no server logs despite other requests to the server.

The run got stuck in the terminating state.

The command dstack stop -x <run-name> hanged.

Other requests such as dstack ps worked as usual.

After a restart of the server, the problem has gone.

@peterschmidt85 peterschmidt85 added the bug Something isn't working label May 17, 2024
This was referenced May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant