Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Bogdan, You’re more than warm! Thanks for the quick turnaround on these fixes! I’ve tested and verified each of them. I’ve not run into any more issues so far. Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Wednesday, February 28, 2018 at 6:27 AM To: Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, This new crash was also fixed - see https://github.com/OpenSIPS/opensips/commit/34f81b223fb466ecddf648f72f615ab24d4a86dc<https://github.com/OpenSIPS/opensips/commit/34f81b223fb466ecddf648f72f615ab24d4a86dc> . Do you have any more crashes on the pipe to report :D ? I'm getting warm :) Thanks and 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/28/2018 06:19 AM, Ben Newlin wrote: I was able to reproduce and capture a core dump of the crash. Backtrace is available here: https://pastebin.com/WtBB6cKm<https://pastebin.com/WtBB6cKm> Thanks, Ben Newlin From: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 10:47 PM To: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Unfortunately, I have had another crash during testing. I was not able to capture the core, but I did get this log: Feb 28 03:35:22 [359] CRITICAL:core:qm_debug_frag: qm_*: prev. fragm. tail overwritten(c0c0c0c0c0c0c020, abcdefedabcdefed)[0x7fa6cd6c46b8:0x7fa6cd6c46f0] (del_uri_param, checks.c:242)! Feb 28 03:35:23 [353] INFO:core:handle_sigs: child process 359 exited by a signal 6 I am making adjustments to be able to collect the core if the crash occurs again. Thanks, Ben Newlin From: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:47 PM To: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I found this previous thread that has this error: http://lists.opensips.org/pipermail/users/2016-October/035635.html<http://lists.opensips.org/pipermail/users/2016-October/035635.html> The fix suggested there worked. When I removed the quotes around the regexp used in re.subst the crash did not occur. Ben Newlin From: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:20 PM To: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg<https://pastebin.com/Fk2BRnsg> Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org> Date: Tuesday, February 27, 2018 at 12:55 PM To: OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Tha
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Hi Ben, This new crash was also fixed - see https://github.com/OpenSIPS/opensips/commit/34f81b223fb466ecddf648f72f615ab24d4a86dc . Do you have any more crashes on the pipe to report :D ? I'm getting warm :) Thanks and 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/28/2018 06:19 AM, Ben Newlin wrote: I was able to reproduce and capture a core dump of the crash. Backtrace is available here: https://pastebin.com/WtBB6cKm Thanks, Ben Newlin *From: *Ben Newlin <ben.new...@genesys.com> *Date: *Tuesday, February 27, 2018 at 10:47 PM *To: *Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Unfortunately, I have had another crash during testing. I was not able to capture the core, but I did get this log: Feb 28 03:35:22 [359] CRITICAL:core:qm_debug_frag: qm_*: prev. fragm. tail overwritten(c0c0c0c0c0c0c020, abcdefedabcdefed)[0x7fa6cd6c46b8:0x7fa6cd6c46f0] (del_uri_param, checks.c:242)! Feb 28 03:35:23 [353] INFO:core:handle_sigs: child process 359 exited by a signal 6 I am making adjustments to be able to collect the core if the crash occurs again. Thanks, Ben Newlin *From: *Ben Newlin <ben.new...@genesys.com> *Date: *Tuesday, February 27, 2018 at 2:47 PM *To: *Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I found this previous thread that has this error: http://lists.opensips.org/pipermail/users/2016-October/035635.html The fix suggested there worked. When I removed the quotes around the regexp used in re.subst the crash did not occur. Ben Newlin *From: *Ben Newlin <ben.new...@genesys.com> *Date: *Tuesday, February 27, 2018 at 2:20 PM *To: *Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> *Date: *Tuesday, February 27, 2018 at 12:55 PM *To: *OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Ben for the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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/26/2018 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging.
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Hi Ben Thanks for more testing :). I managed to identify the bug for this crash - even if the regexp is bogus, opensips should not crash. See https://github.com/OpenSIPS/opensips/commit/37eab9a8c2dd19a17f2617057ca2014e9ffee263 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/27/2018 09:47 PM, Ben Newlin wrote: Bogdan, I found this previous thread that has this error: http://lists.opensips.org/pipermail/users/2016-October/035635.html The fix suggested there worked. When I removed the quotes around the regexp used in re.subst the crash did not occur. Ben Newlin *From: *Ben Newlin <ben.new...@genesys.com> *Date: *Tuesday, February 27, 2018 at 2:20 PM *To: *Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> *Date: *Tuesday, February 27, 2018 at 12:55 PM *To: *OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Ben for the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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/26/2018 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
I was able to reproduce and capture a core dump of the crash. Backtrace is available here: https://pastebin.com/WtBB6cKm Thanks, Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 10:47 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Unfortunately, I have had another crash during testing. I was not able to capture the core, but I did get this log: Feb 28 03:35:22 [359] CRITICAL:core:qm_debug_frag: qm_*: prev. fragm. tail overwritten(c0c0c0c0c0c0c020, abcdefedabcdefed)[0x7fa6cd6c46b8:0x7fa6cd6c46f0] (del_uri_param, checks.c:242)! Feb 28 03:35:23 [353] INFO:core:handle_sigs: child process 359 exited by a signal 6 I am making adjustments to be able to collect the core if the crash occurs again. Thanks, Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:47 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I found this previous thread that has this error: http://lists.opensips.org/pipermail/users/2016-October/035635.html The fix suggested there worked. When I removed the quotes around the regexp used in re.subst the crash did not occur. Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:20 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Tuesday, February 27, 2018 at 12:55 PM To: OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Ben for the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Unfortunately, I have had another crash during testing. I was not able to capture the core, but I did get this log: Feb 28 03:35:22 [359] CRITICAL:core:qm_debug_frag: qm_*: prev. fragm. tail overwritten(c0c0c0c0c0c0c020, abcdefedabcdefed)[0x7fa6cd6c46b8:0x7fa6cd6c46f0] (del_uri_param, checks.c:242)! Feb 28 03:35:23 [353] INFO:core:handle_sigs: child process 359 exited by a signal 6 I am making adjustments to be able to collect the core if the crash occurs again. Thanks, Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:47 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I found this previous thread that has this error: http://lists.opensips.org/pipermail/users/2016-October/035635.html The fix suggested there worked. When I removed the quotes around the regexp used in re.subst the crash did not occur. Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:20 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Tuesday, February 27, 2018 at 12:55 PM To: OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Ben for the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Bogdan, I found this previous thread that has this error: http://lists.opensips.org/pipermail/users/2016-October/035635.html The fix suggested there worked. When I removed the quotes around the regexp used in re.subst the crash did not occur. Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Tuesday, February 27, 2018 at 2:20 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Tuesday, February 27, 2018 at 12:55 PM To: OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Ben for the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Bogdan, I just tested it and that crash is no longer occurring. However I am now seeing a different crash, but it seems to still be related to regexp. Feb 27 19:07:17 [369] ERROR:core:subst_parser: string too short Feb 27 19:07:17 [369] ERROR:core:tr_eval_re: Can't compile regexp Feb 27 19:07:17 [369] WARNING:core:do_assign: no value in right expression at /opensips/control.cfg:1952 Feb 27 19:07:17 [361] INFO:core:handle_sigs: child process 369 exited by a signal 11 Feb 27 19:07:17 [361] INFO:core:handle_sigs: core was generated Feb 27 19:07:17 [361] INFO:core:handle_sigs: terminating due to SIGCHLD The do_assign error makes it seem like there may be something wrong in my script, but I can’t see what it is. And I’m not sure what the “string too short” error is either or why the regexp could not be compiled. It looks valid to me. Backtrace: https://pastebin.com/Fk2BRnsg Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Tuesday, February 27, 2018 at 12:55 PM To: OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, I just committed the fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Ben for the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Hi Ben, I just committedthe fix for this - could you update from GIT and give it a new try ? Thanks and 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/27/2018 06:19 PM, Bogdan-Andrei Iancu wrote: Thanks Benfor the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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/26/2018 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Thanks Benfor the support in investigating this. The bug was identified and confirm, let me work on a fix right now. I will shortly ping you for testing ;) 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/27/2018 12:12 AM, Bogdan-Andrei Iancu wrote: OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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/26/2018 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> *Date: *Monday, February 26, 2018 at 4:14 PM *To: *Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK OK, but check the exact file you pass to Opensips - according to the debug info is /opensips/control.cfg like 435. Also, do you use the $DLG_dir variable in your cfg ? 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/26/2018 08:10 PM, Ben Newlin wrote: Hmm, no. Line 435 of my config is a return statement. return(-1); Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 12:16 PM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Could you off-list past me the line 435 of your cfg - I guess you use some $DLG_dir there ? 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/26/2018 07:04 PM, Ben Newlin wrote: Here you go: https://pastebin.com/rpUjaHBG <https://pastebin.com/rpUjaHBG> Thanks, Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:45 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@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 OpenSIPS Summit 2018 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 <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:40 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
OK, to be more precise, the crash is around an "If" statement where you have in the condition an REGEXP test (=~) with a left operand translated into "downstream" (maybe a $DLG_dir ??). Does it sound familiar to you :) ? 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/26/2018 11:32 PM, Ben Newlin wrote: Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> *Date: *Monday, February 26, 2018 at 4:14 PM *To: *Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK OK, but check the exact file you pass to Opensips - according to the debug info is /opensips/control.cfg like 435. Also, do you use the $DLG_dir variable in your cfg ? 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/26/2018 08:10 PM, Ben Newlin wrote: Hmm, no. Line 435 of my config is a return statement. return(-1); Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 12:16 PM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Could you off-list past me the line 435 of your cfg - I guess you use some $DLG_dir there ? 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/26/2018 07:04 PM, Ben Newlin wrote: Here you go: https://pastebin.com/rpUjaHBG <https://pastebin.com/rpUjaHBG> Thanks, Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:45 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@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 OpenSIPS Summit 2018 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 <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:40 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Yes, that is from that exact file, line 435. It’s just a return statement. I can send you the file off-list if you’d like. I do use the $DLG_dir in my script in a few places, but the only one this crash would have hit is in some logging. Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Monday, February 26, 2018 at 4:14 PM To: Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK OK, but check the exact file you pass to Opensips - according to the debug info is /opensips/control.cfg like 435. Also, do you use the $DLG_dir variable in your cfg ? 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 08:10 PM, Ben Newlin wrote: Hmm, no. Line 435 of my config is a return statement. return(-1); Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org> Date: Monday, February 26, 2018 at 12:16 PM To: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Could you off-list past me the line 435 of your cfg - I guess you use some $DLG_dir there ? 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 07:04 PM, Ben Newlin wrote: Here you go: https://pastebin.com/rpUjaHBG<https://pastebin.com/rpUjaHBG> Thanks, Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org> Date: Monday, February 26, 2018 at 10:45 AM To: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@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 <bog...@opensips.org><mailto:bog...@opensips.org> Date: Monday, February 26, 2018 at 10:40 AM To: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
OK,but check the exact file you pass to Opensips - according to the debug info is /opensips/control.cfg like 435. Also, do you use the $DLG_dir variable in your cfg ? 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/26/2018 08:10 PM, Ben Newlin wrote: Hmm, no. Line 435 of my config is a return statement. return(-1); Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> *Date: *Monday, February 26, 2018 at 12:16 PM *To: *Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Could you off-list past me the line 435 of your cfg - I guess you use some $DLG_dir there ? 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/26/2018 07:04 PM, Ben Newlin wrote: Here you go: https://pastebin.com/rpUjaHBG <https://pastebin.com/rpUjaHBG> Thanks, Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:45 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@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 OpenSIPS Summit 2018 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 <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:40 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Hmm, no. Line 435 of my config is a return statement. return(-1); Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Monday, February 26, 2018 at 12:16 PM To: Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Could you off-list past me the line 435 of your cfg - I guess you use some $DLG_dir there ? 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 07:04 PM, Ben Newlin wrote: Here you go: https://pastebin.com/rpUjaHBG<https://pastebin.com/rpUjaHBG> Thanks, Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org><mailto:bog...@opensips.org> Date: Monday, February 26, 2018 at 10:45 AM To: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@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 <bog...@opensips.org><mailto:bog...@opensips.org> Date: Monday, February 26, 2018 at 10:40 AM To: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Could you off-list pastme the line 435 of your cfg - I guess you use some $DLG_dir there ? 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/26/2018 07:04 PM, Ben Newlin wrote: Here you go: https://pastebin.com/rpUjaHBG <https://pastebin.com/rpUjaHBG> Thanks, Ben Newlin *From: *Bogdan-Andrei Iancu <bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:45 AM *To: *Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@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 OpenSIPS Summit 2018 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 <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:40 AM *To: *Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Here you go: https://pastebin.com/rpUjaHBG Thanks, Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Monday, February 26, 2018 at 10:45 AM To: Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@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 <bog...@opensips.org><mailto:bog...@opensips.org> Date: Monday, February 26, 2018 at 10:40 AM To: Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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 <bog...@opensips.org><mailto:bog...@opensips.org> Date: Thursday, February 22, 2018 at 5:26 AM To: OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@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_
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 OpenSIPS Summit 2018 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 <bog...@opensips.org> *Date: *Monday, February 26, 2018 at 10:40 AM *To: *Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> *Subject: *Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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 <bog...@opensips.org> <mailto:bog...@opensips.org> *Date: *Thursday, February 22, 2018 at 5:26 AM *To: *OpenSIPS users mailling list <users@lists.opensips.org> <mailto:users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com> <mailto:ben.new...@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 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
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Bogdan, Unfortunately I am not at all familiar with gdb. How do I change frames? Ben Newlin From: Bogdan-Andrei Iancu <bog...@opensips.org> Date: Monday, February 26, 2018 at 10:40 AM To: Ben Newlin <ben.new...@genesys.com>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Hi Ben, The backtrace points to the script interpreter :DPlease 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 <bog...@opensips.org><mailto:bog...@opensips.org> Date: Thursday, February 22, 2018 at 5:26 AM To: OpenSIPS users mailling list <users@lists.opensips.org><mailto:users@lists.opensips.org>, Ben Newlin <ben.new...@genesys.com><mailto:ben.new...@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@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users> ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Hi Ben, The backtrace points to the script interpreter :DPlease 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 <bog...@opensips.org> *Date: *Thursday, February 22, 2018 at 5:26 AM *To: *OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@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 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 Users@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Any progress on this? I’m happy to provide more information if needed. Ben Newlin From: Ben Newlin <ben.new...@genesys.com> Date: Thursday, February 22, 2018 at 12:33 PM To: Bogdan-Andrei Iancu <bog...@opensips.org>, OpenSIPS users mailling list <users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK Bogdan, Here is the backtrace: 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 <bog...@opensips.org> Date: Thursday, February 22, 2018 at 5:26 AM To: OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@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@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users> ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS crashing on 200 OK
Bogdan, Here is the backtrace: 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 <bog...@opensips.org> Date: Thursday, February 22, 2018 at 5:26 AM To: OpenSIPS users mailling list <users@lists.opensips.org>, Ben Newlin <ben.new...@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@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users> ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
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 Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] OpenSIPS crashing on 200 OK
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 Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users