Actions
Bug #5735
openctl client disconnect doesn't re-set timeslot state
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/01/2022
Due date:
% Done:
0%
Spec Reference:
Description
When a ctl client socket gets closed (client disconnects/crashes), we are cleaning up that ctl socket, but we don't clean up other state, such as
- the fact that a given timeslot is no longer open (subsequent open of that TS gets a "cannot re-open unless FORCE option is used" error)
- the socketpair() file-descriptors for the per-timeslot data are not closed
It's currently not possible to fix this directly, as nothing in osmo-e1d tracks the relationship of client<->timeslot. So without that state, we cannot clean up.
Actions
