[Freeswitch-users] 2017-08-09 06:06:29.494827 [CRIT] switch_core_session.c:1755 LUKE: I'm hit, but not bad.

[Michael Jerris]

you get this when we are unable to start threads.  This can happen for a number of reasons, such as system limits, out of ram, etc.

> On Aug 9, 2017, at 1:22 AM, Jurijs Ivolga <jurijs.ivolga at gmail.com> wrote:
> 
> Hi,
> 
> I'm constantly getting following error after around 1 week running freeswitch on quite a low amount of traffic and freeswitch stops to replying to any traffic:
> 
> 7fcf13e5-4529-464c-87af-67dca8a2eca8 2017-08-09 06:06:06.454889 [NOTICE] switch_channel.c:1104 New Channel sofia/internal/xxxx at myip [7fcf13e5-4529-464c-87af-67dca8a2eca8]
> 2017-08-09 06:06:06.454889 [CRIT] switch_core_session.c:1799 Thread Failure!
> 83f02a66-630e-4f59-8716-12a107478059 2017-08-09 06:06:29.494827 [NOTICE] switch_channel.c:1104 New Channel sofia/internal/xxxx at myip [83f02a66-630e-4f59-8716-12a107478059]
> 2017-08-09 06:06:29.494827 [CRIT] switch_core_session.c:1799 Thread Failure!
> 2017-08-09 06:06:29.494827 [CRIT] switch_core_session.c:1755 LUKE: I'm hit, but not bad.
> 2017-08-09 06:06:29.494827 [CRIT] switch_core_session.c:1756 LUKE'S VOICE: Artoo, see what you can do with it. Hang on back there....
> Green laserfire moves past the beeping little robot as his head turns.  After a few beeps and a twist of his mechanical arm,
> Artoo reduces the max sessions to 101 thus, saving the switch from certain doom.
> 
> fs_cli stops to work and freeswitch replies with:
> 
> SIP/2.0 503 Maximum Calls In Progress
> 
> Cpu usage is 0.
> 
> Any hints?
> 
> Jurijs