Stop Response PJSIP Asterisk

Asterisk Asterisk SIP
1

Asterisk 18.12.1

I have a situation. sometime PJSIP stop answer requests.

For return, I need stop asterisk process and start again

In full log I saw this warnings:

I don’t know if this message can Help a solved.

[Apr 3 12:05:46] WARNING[17635] taskprocessor.c: The ‘stasis/m:devicestate:all-00003751’ task processor queue reached 500 scheduled tasks again.
[Apr 3 12:06:46] WARNING[17635] taskprocessor.c: The ‘stasis/m:devicestate:all-00003751’ task processor queue reached 500 scheduled tasks again.
[Apr 3 12:07:01] WARNING[29222] taskprocessor.c: The ‘stasis/m:devicestate:all-00003751’ task processor queue reached 500 scheduled tasks again.
[Apr 3 12:07:42] WARNING[19021][C-000041b4] taskprocessor.c: The ‘stasis/p:channel:all-0000f31d’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:07:42] WARNING[42972][C-00004807] taskprocessor.c: The ‘stasis/p:channel:all-0000f0a3’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:07:42] WARNING[10074][C-00004758] taskprocessor.c: The ‘stasis/p:channel:all-0000f2b7’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:07:42] WARNING[4835][C-00004734] taskprocessor.c: The ‘stasis/p:channel:all-0000f091’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:07:42] WARNING[42984][C-000046ca] taskprocessor.c: The ‘stasis/p:channel:all-0000f2c7’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:07:42] WARNING[43669][C-00004815] taskprocessor.c: The ‘stasis/p:channel:all-0000efe9’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:07:43] WARNING[42418][C-00004807] taskprocessor.c: The ‘stasis/m:manager:core-00000007’ task processor queue reached 3000 scheduled tasks.
[Apr 3 12:08:24] WARNING[37347] taskprocessor.c: The ‘stasis/m:devicestate:all-000037c0’ task processor queue reached 500 scheduled tasks.
[Apr 3 12:08:24] WARNING[37347] taskprocessor.c: The ‘stasis/m:devicestate:all-00000003’ task processor queue reached 500 scheduled tasks.

2

You’ve either got a deadlock or an overload. I don’t think there is enough information to decide between those.

For a deadlock, you should try 18.17.1

3

Hello David , tks your answer.

I will try the lasted version, and return

4

Today I received Crash in asterisk .

Version 18.17.1

I don’t know if this crash have relationship with “stop sip response”

traps: asterisk[31487] general protection ip:7f0b9edd7ed5 sp:7f0b4cb4f3e0 error:0 in res_pjsip_session.so[7f0b9edc3000+19000]

5

https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

6

Hi learbia

We are also in the same situation, Could you please tell what are the application/modules you using in asterisk.

7

My configuration is all files .conf

I have to many endpoints (5k a 6k) per server
But I have a big machines, with 80 a 90 cores in processors and 128G ram memory

I use all “asterisk” but the principal modules
PJSIP (all transports, udp, tcp and wss for webrtc)
CEL

Initially I thought it was processing or ram memory, but I discarted this options, because I have many CPU avaliable when the problem happens

When I have a problem my processors and memory its OK,

I think the problem is related to the pjsip webrtc connection, is there any undiscovered problem, when the internet connection oscillates it happens more often

8

https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

9

How can I Get backtrace when asterisk don’t crash, ?

I always get backtraces in crash of asterisk, but in this case pjsip stop response invites,register …

I started asterisk with -g and I wait any crash, but when pjsip stop response many times we dont have a crash in asterisk process

10

You would use the instructions for getting a backtrace from a deadlock[1].

[1] Getting a Backtrace - Asterisk Project - Asterisk Project Wiki.

11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.