You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Run boundary connect to initialize a session.
Run ps aux | grep boundary connect to get the PID of the boundary session related process.
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.
The text was updated successfully, but these errors were encountered:
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:
boundary connect
to initialize a session.ps aux | grep boundary connect
to get the PID of the boundary session related process.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.
The text was updated successfully, but these errors were encountered: