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
OpenSIPS Summit 2018
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 <[email protected]>
*Date: *Thursday, February 22, 2018 at 5:26 AM
*To: *OpenSIPS users mailling list <[email protected]>, Ben
Newlin <[email protected]>
*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
OpenSIPS Summit 2018
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
Call logs: https://pastebin.com/vY5crK8U
I also have the core dump if any more information is needed from that.
Thanks,
Ben Newlin
_______________________________________________
Users mailing list
[email protected]<mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
