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

Killed sessions do not get closed #5047

Open
mehrdad-khojastefar opened this issue Aug 27, 2024 · 0 comments
Open

Killed sessions do not get closed #5047

mehrdad-khojastefar opened this issue Aug 27, 2024 · 0 comments
Labels
bug Something isn't working triage

Comments

@mehrdad-khojastefar
Copy link

Describe the bug
When a boundary session is not gracefully terminated the session remains in the status that it was.

To Reproduce
Steps to reproduce the behavior:

  1. Run boundary connect to initialize a session.
  2. Run ps aux | grep boundary connect to get the PID of the boundary session related process.
  3. Run kill -9 <PID> to kill the process.

Expected behavior
Now since we have not activated any channels for this session the session is stuck in pending state and we should close it manually. If there are any channels active for this session the session remains in the active state.

@mehrdad-khojastefar mehrdad-khojastefar added the bug Something isn't working label Aug 27, 2024
@psekar psekar added the triage label Sep 12, 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 triage
Projects
None yet
Development

No branches or pull requests

2 participants