[Freeswitch-users] Limit [ERROR] question
djbinter at gmail.com
Tue Oct 19 08:23:00 PDT 2010
Thank you for your clear response.
This issue happened to be on my production server. I can reproduce since it
happened almost every day, but only happened to 1-2 calls max out of many
concurrent calls. Thus, I am not that concern right now until I started to
see more of this error.
I use limit just to keep track of concurrent calls per each gateway similar
<action application="limit" data="db inbound 18.104.22.168 10000"/>
<action application="limit_execute" data="db outbound 22.214.171.124 10000 bridge
My next question would be whether it would generate more of this errors if I
routed more calls to this server, and if there is any recommendation on how
to prevent it.
On Tue, Oct 19, 2010 at 5:56 AM, Rupa Schomaker <rupa at rupa.com> wrote:
> This is a "shouldn't happen" sanity check you are tripping over -- I
> probably should have worded the error message better.
> Immediate cause is that the list of backends (hash, sql, etc) that have
> registered interest in this call is empty. This shouldn't happen because
> we register the handler at the same time that we set the channel var of
> interested backends.
> Can you find a way to reproduce this reliably?
> The effect of this would be to (potentially) not decrement a counter when
> we should have.
> On Mon, Oct 18, 2010 at 7:31 PM, DJB International <djbinter at gmail.com>wrote:
>> I have noticed once in a while in the log file with the following error:
>> [ERR] switch_limit.c:86 Unset limit backendlist!
>> What exactly would cause this error?
>> Thank you,
>> Dorn B.
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the FreeSWITCH-users