[OpenSIPS-Users] OpenSIPS crashing on 200 OK

Mon Feb 26 12:04:13 EST 2018

Here you go: https://pastebin.com/rpUjaHBG

Thanks,

Ben Newlin

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Date: Monday, February 26, 2018 at 10:45 AM
To: Ben Newlin <Ben.Newlin at genesys.com>, OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK

OK, once you started GDB like "gdb /path/to/opensips /path/to/core", run step by step:

f 0
p *s1
f 5
p *a

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

  http://www.opensips-solutions.com<http://www.opensips-solutions.com>

OpenSIPS Summit 2018

  http://www.opensips.org/events/Summit-2018Amsterdam<http://www.opensips.org/events/Summit-2018Amsterdam>
On 02/26/2018 05:43 PM, Ben Newlin wrote:
Bogdan,

Unfortunately I am not at all familiar with gdb. How do I change frames?

Ben Newlin

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Date: Monday, February 26, 2018 at 10:40 AM
To: Ben Newlin <Ben.Newlin at genesys.com><mailto:Ben.Newlin at genesys.com>, OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK

Hi Ben,

The backtrace points to the script interpreter :D....Please do the followings (assuming you are a bit faimilar with GDB :) ) :

in frame 0, please do "print *s1"
and in frame 5 do "print *a"

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

  http://www.opensips-solutions.com<http://www.opensips-solutions.com>

OpenSIPS Summit 2018

  http://www.opensips.org/events/Summit-2018Amsterdam<http://www.opensips.org/events/Summit-2018Amsterdam>
On 02/22/2018 07:33 PM, Ben Newlin wrote:
Bogdan,

Here is the backtrace: https://pastebin.com/6tZhrWek<https://pastebin.com/6tZhrWek>

I am not using TCP, BIN, or HEP in this configuration. I am not using anything, to my knowledge, which should be causing TCP worker threads to be spawned.

Ben Newlin

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Date: Thursday, February 22, 2018 at 5:26 AM
To: OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>, Ben Newlin <Ben.Newlin at genesys.com><mailto:Ben.Newlin at genesys.com>
Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK

Hi Ben,

Do you have a full backtrace extracted from the core ?

In regards to the TCP processes, the TCP layer will automatically enabled itself depending on what protocols (tcp-based) you are using in script. Maybe you do not use SIP with TCP, but do you use BIN or HEP ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

  http://www.opensips-solutions.com<http://www.opensips-solutions.com>

OpenSIPS Summit 2018

  http://www.opensips.org/events/Summit-2018Amsterdam<http://www.opensips.org/events/Summit-2018Amsterdam>
On 02/22/2018 12:38 AM, Ben Newlin wrote:
Hi,

I am currently upgrading to 2.3.3 and am running off the HEAD of the 2.3 branch. My OpenSIPS is consistently crashing when trying to process the ACK to an initial INVITE request. I am testing with SIPp using a simple single call scenario. I see the following in the logs:

Feb 21 21:32:27 [383] DBG:core:io_wait_loop_epoll: [TCP_main] EPOLLHUP on IN ->connection closed by the remote peer!
Feb 21 21:32:27 [383] CRITICAL:core:receive_fd: EOF on 33
Feb 21 21:32:27 [383] DBG:core:handle_worker: dead child 9, pid 370 (shutting down?)
Feb 21 21:32:27 [383] DBG:core:io_watch_del: [TCP_main] io_watch_del op on index 8 33 (0x8d4e80, 33, 8, 0x0,0x1) fd_no=29 called
Feb 21 21:32:27 [361] DBG:core:handle_sigs: status = 139
Feb 21 21:32:27 [361] INFO:core:handle_sigs: child process 370 exited by a signal 11
Feb 21 21:32:27 [361] INFO:core:handle_sigs: core was generated
Feb 21 21:32:27 [361] INFO:core:handle_sigs: terminating due to SIGCHLD

I also notice that OpenSIPS is starting up a number of TCP processes even though I do not use TCP in my script. I do not even have the proto_tcp module loaded. I used to use the “disable_tcp” global parameter in 1.11, but that has been removed in 2.3.

Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [375] DBG:core:io_watch_add: [TCP_worker] io_watch_add op (3 on 53) (0x8d4e80, 3, 1, (nil),1), fd_no=0/209715
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"
Feb 21 22:03:56 [361] DBG:core:internal_fork: forking new process "SIP receiver TCP"

Initialization logs: https://pastebin.com/nsJQGkdy<https://pastebin.com/nsJQGkdy>
Call logs: https://pastebin.com/vY5crK8U<https://pastebin.com/vY5crK8U>

I also have the core dump if any more information is needed from that.

Thanks,
Ben Newlin

_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180226/c5493894/attachment-0001.html>