[Freeswitch-users] Freeswitch stops handling register requests

[Peter Steinbach]

>But maybe it has to do with the esl library like too many open threads
or something like that.

Hello Markus,

I remember, we had some issues a while ago, when Freeswitch fired a huge
amount of esl events under heavy load, and we could not handle them in
time. Therefore we built an ESL process which simply and quickly pushed
the events to some Queues on a Redis Server. This process worked much
quicker, than Freeswitch could fire events, so events may not be stuck
inside Freeswitch waiting to be processed. On the other side we then had
workers for each Redis Queue, who pulled the events and processed them.
That way we can process all events from Freeswitch in time without
losing any events.

Maybe you experience something similar?

Best regards
Peter

On 05/06/17 09:31, Markus Bönke wrote:
> I just checked the logs of our esl client and this was not the case. There is only one parrallel bridge to 8 destinations near the time where the problem occurred. Also the esl socket continued to receive and send events after freeswitch stopped to answer on register events. But maybe it has to do with the esl library like too many open threads or something like that. We recently updated the system from 1.4.26 to 1.6.17, everything was running for 2 days with around 150-200 calls parallel before the problem occurred. I’ve increased debug and monitoring, let’s see if it appears again in the next days.
>
> Thanks and regards
>
> Markus
>
>
>> Am 05.05.2017 um 19:03 schrieb Michael Jerris <mike at jerris.com>:
>>
>> What you describe could happen if your esl script suddenly sent many thousands of originate commands.
>>
>>> On May 5, 2017, at 11:58 AM, Markus Bönke <mbodbg at gmx.net> wrote:
>>>
>>> Hello,
>>>
>>> We faced today the following situation:
>>>
>>> Freeswitch suddenly stopped to respond to answer to REGISTER requests.
>>> At the same time it created more and more channels. A lot of them „hung" in status „RINGING“, after some time all calls were rejected with 503 Maximum Calls In Progress.
>>>
>>> After a restart, everything went back to normal
>>>
>>> I cannot find any WARNING or ERRROR/CRIT messages in the log.
>>> Also there is nothing special in the syslog at the time the issue appeared.
>>>
>>> We are using freeswitch 1.6.17 on debian jessie installed from debian packages. Calls are handled via esl / mod_event socket.
>>>
>>> Is there any known issue with this version? Is there anything else I can check?
>>>
>>> Thanks and Regards
>>>
>>> Markus
>>>
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services: 
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://confluence.freeswitch.org
>> http://www.cluecon.com
>>
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services: 
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://confluence.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org


-- 
With kind regards
Peter Steinbach 

Telefaks Services GmbH
mailto:lists (att) telefaks.de
Internet: www.telefaks.de