I have a problem where API sessions are not being full released. “/user active print” will result in thousands of entries created via the API as I monitor certain aspects via an API script every 5 minutes.
I see in v5b this has been addressed:-
Will this fix be back ported into v4.x?
I assume the sessions are actually closed and just the entries are not removed as there is no perceivable CPU or RAM usage from a unit with 10 entries to a unit with over 5000.
Other than a reboot (not possible in productions hardware) I do not see any other way of removing these ‘ghost’ entries.
My concern is that when the active user count reaches an unknown limit the routerboards may lockup!