wmasilva
commented
2 months ago after applying the pr #2390 the issue is better but it still have limit hash entries that are not deleted. To detect invalid values, i use "hash_dump limit" and "show channels" and the result is:
ERROR found invalid account limit: 200@lab.local limit:1 channels:0
I've implemented a method to delete limit entries without having to restart the entire FS, #2518 the system is recording calls so i apply the pr #2218.
So far is running ok and i'm collecting more debug to try to fetch the source of the problem.
I'm using mod_hash as backend to limit simultaneous calls per user/account, from time to time i see the counter associated to an user not release and I've to increase the limit or restart freeswitch to reset the counter.
Initial i thought it could be an issue with mod_hash not deleting the entry, but i find out that the problem is the sofia channel not getting destroy, so the resource remains active.
If i manually kill the channel, using uuid_kill, i see the message "success" but the counter remains active and the channel is still present in database. I then try to uuid_dump or uuid_kill and i got the message "no such channel".
I did a gcore dump on freeswitch process and find out that the channel was lock in the function "sofia_receive_message".
Attach the BT for the thread associated to the zombie channel: