Looks like it's an assert-type error. limit_state_handler() is called without the limit_backend variable being set, which is an internal variable for storing limit information used to internally track limit information during the call. The odd thing is that variable should always be set prior to limit_state_handler being registered. I'm guessing it's some sort of race condition... -Steve On 8 February 2013 04:24, Victor Chukalovskiy <victor.chukalovskiy@gmail.com
wrote:
Hello,
I'm getting this error occasionally in the log: [ERR] switch_limit.c:86 Unset limit backendlist!
Seems to happen only after I change the value of CPS limit on the working system. For example, after I change *4* to 3 below and send some more calls: <action application="limit" data="hash cps test *4*/1 !NORMAL_CIRCUIT_CONGESTION" />
Could someone please explain when exactly does this error occur? How to reset it other than restarting FS instance?
What I found is that I'm not the only one who got annoyed, and that loglevel was reduced in later versions:
http://jira.freeswitch.org/browse/FS-4792?page=com.atlassian.streams.streams...
However, I want to figure out how to avoid this error in the first place rather than just update and suppress it. Any help is appreciated.
Thank you, Victor
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org