Re: [OpenSIPS-Devel] OpenSIPS Crash

Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Oh, just do in gdb: f 2 p *((struct qm_frag*)((char*)(p)-sizeof(struct qm_frag))) In regards to async, I was more talking about the script async() (to try to remove it) , not about the async in the protocols. Best regards, Bogdan-Andrei Iancu

Re: [OpenSIPS-Devel] OpenSIPS Crash

Reply-To: OpenSIPS devel mailling list Date: Tuesday, July 9, 2019 at 5:20 PM To: OpenSIPS devel mailling list , Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Any updates on this? Would you like me to open a ticket or does one already exist for the issue? Ben Newlin From

Re: [OpenSIPS-Devel] OpenSIPS Crash

mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Bogdan, I was able to reproduce this crash on the newer 2.4 commit. Backtrace: https://pastebin.com/RaMXTZA4 # opensips -V version: opensips 2.4.6 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC

Re: [OpenSIPS-Devel] OpenSIPS Crash

: Re: [OpenSIPS-Devel] OpenSIPS Crash Bogdan, I am glad the cause is known at least. :) Is there a ticket I can follow for more information and to be notified of resolution? Ben Newlin From: Bogdan-Andrei Iancu Date: Wednesday, June 26, 2019 at 7:37 AM To: Ben Newlin , OpenSIPS devel mailling

Re: [OpenSIPS-Devel] OpenSIPS Crash

Andrei Iancu *Date: *Wednesday, June 26, 2019 at 11:34 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash As per ticket, the issue you reported was already fixed, so going for the latest version in 2.4 branch should be fine with you. Regards,

Re: [OpenSIPS-Devel] OpenSIPS Crash

To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash As per ticket, the issue you reported was already fixed, so going for the latest version in 2.4 branch should be fine with you. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https

Re: [OpenSIPS-Devel] OpenSIPS Crash

Iancu , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Bogdan, Strange, I got no notification of your update on that ticket. Still I cannot see how it was fixed a month ago? I was using the 2.4.6 release when I encountered the crash. 2.4.6 was only released 15 days

Re: [OpenSIPS-Devel] OpenSIPS Crash

*Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Thank you Ben, This backtrace confirms the initial suspicion - I'm trying to find out a way to get it fixed in a more generic way; what you experience is just one face of the problem (with many faces :P) and there are other related reports

Re: [OpenSIPS-Devel] OpenSIPS Crash

o:bog...@opensips.org> Date: Friday, June 7, 2019 at 9:15 AM To: Ben Newlin <mailto:ben.new...@genesys.com>, OpenSIPS devel mailling list <mailto:devel@lists.opensips.org> Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often/easy is to reproduce this crash (if possible) ? Br

Re: [OpenSIPS-Devel] OpenSIPS Crash

AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash As per ticket, the issue you reported was already fixed, so going for the latest version in 2.4 branch should be fine with you. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer

Re: [OpenSIPS-Devel] OpenSIPS Crash

] https://github.com/OpenSIPS/opensips/issues/1736 <https://github.com/OpenSIPS/opensips/issues/1736> Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Wednesday, June 26, 2019 at 10:56 AM *To: *OpenSIPS devel mailling list , Ben Newlin *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben,

Re: [OpenSIPS-Devel] OpenSIPS Crash

Newlin From: Bogdan-Andrei Iancu Date: Wednesday, June 26, 2019 at 10:56 AM To: OpenSIPS devel mailling list , Ben Newlin Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, While re-checking some of some data related to your report, I noticed that your opensips version (revision d025b4f61

Re: [OpenSIPS-Devel] OpenSIPS Crash

this occurs? [1] https://pastebin.com/n0Ph8XH5 <https://pastebin.com/n0Ph8XH5> Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Friday, June 7, 2019 at 9:15 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often/easy is to rep

Re: [OpenSIPS-Devel] OpenSIPS Crash

with the TLS calls? Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Wednesday, June 26, 2019 at 5:25 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, In any of the corefile, in frame 2 could you print p *((struct qm_frag*)((char*)(p

Re: [OpenSIPS-Devel] OpenSIPS Crash

Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, In any of the corefile, in frame 2 could you print p *((struct qm_frag*)((char*)(p)-sizeof(struct qm_frag))) Now, I see that the backtrace via libcurl & libcrypto may go via some error cleanup - see frame #7 and #8 - so , do you see

Re: [OpenSIPS-Devel] OpenSIPS Crash

lists.opensips.org>, Ben Newlin <mailto:ben.new...@genesys.com> *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, Thanks for "another" report :). Questions: 1) do you do any async for the INVITE in this crash ? 2) if it is an YES to (1), i

Re: [OpenSIPS-Devel] OpenSIPS Crash

n *From: *Bogdan-Andrei Iancu <mailto:bog...@opensips.org> *Date: *Tuesday, June 25, 2019 at 11:39 AM *To: *Ben Newlin <mailto:ben.new...@genesys.com>, OpenSIPS devel mailling list <mailto:devel@lists.opensips.org> *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash

Re: [OpenSIPS-Devel] OpenSIPS Crash

To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often/easy is to reproduce this crash (if possible) ? Brainstorming with Razvan, we suspect a race (on the msg save in shmem in transaction) between the process doing the cleanup after

Re: [OpenSIPS-Devel] OpenSIPS Crash

applications which : support various cryptographic algorithms and protocols. Ben Newlin From: Bogdan-Andrei Iancu Date: Tuesday, June 25, 2019 at 2:54 PM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Thank you Ben :) The backtraces report

Re: [OpenSIPS-Devel] OpenSIPS Crash

OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, The backtrace + corefile should do it ;). Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019A

Re: [OpenSIPS-Devel] OpenSIPS Crash

://pastebin.com/hptH9yiA [4] https://pastebin.com/GfYYZxzB [5] https://pastebin.com/CzYiNAch Ben Newlin From: Bogdan-Andrei Iancu Date: Tuesday, June 25, 2019 at 11:39 AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, The backtrace + corefile

Re: [OpenSIPS-Devel] OpenSIPS Crash

at 12:15 PM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, This looks like very generic - a crash due a previous memory corruption - is it possible for you to run with QM_MALLOC + DBG_MALLOC ? otherwise it is rather impossible to identify

Re: [OpenSIPS-Devel] OpenSIPS Crash

, June 20, 2019 at 12:15 PM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, This looks like very generic - a crash due a previous memory corruption - is it possible for you to run with QM_MALLOC + DBG_MALLOC ? otherwise it is rather impossible

Re: [OpenSIPS-Devel] OpenSIPS Crash

Newlin *Date: *Wednesday, June 19, 2019 at 2:38 PM *To: *OpenSIPS devel mailling list , Bogdan-Andrei Iancu *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash The Github issue has the version info for that, for all the other crashes the version is below. $ opensips -V version: opensips 2.4.5

Re: [OpenSIPS-Devel] OpenSIPS Crash

We have had another crash this morning: https://pastebin.com/dmXYbhzC OpenSIPS version is the same as below. Ben Newlin From: Ben Newlin Date: Wednesday, June 19, 2019 at 2:38 PM To: OpenSIPS devel mailling list , Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash The Github

Re: [OpenSIPS-Devel] OpenSIPS Crash

19, 2019 at 2:30 PM To: Bogdan-Andrei Iancu , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Bogdan, I’m continuing to try to reproduce the timing for that crash. In the meantime, we’ve had quite a few more crashes, but they don’t seem to be the same cause. I opened

Re: [OpenSIPS-Devel] OpenSIPS Crash

://pastebin.com/0VaQfX5B [9] https://pastebin.com/LYUW0AqH Ben Newlin From: Bogdan-Andrei Iancu Date: Monday, June 10, 2019 at 2:41 AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Ben, With what we have so far it is too less data to get to a conclusion

Re: [OpenSIPS-Devel] OpenSIPS Crash

-Andrei Iancu *Date: *Friday, June 7, 2019 at 9:15 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often/easy is to reproduce this crash (if possible) ? Brainstorming with Razvan, we suspect a race (on the msg save in shmem

Re: [OpenSIPS-Devel] OpenSIPS Crash

To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often/easy is to reproduce this crash (if possible) ? Brainstorming with Razvan, we suspect a race (on the msg save in shmem in transaction) between the process doing the cleanup after the async

Re: [OpenSIPS-Devel] OpenSIPS Crash

e) the ACK twice. Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Thursday, June 6, 2019 at 11:42 AM *To: *OpenSIPS devel mailling list , Ben Newlin *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, Thanks for "another" report :). Questions: 1) do you do any async for the INVI

Re: [OpenSIPS-Devel] OpenSIPS Crash

ubject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, Thanks for "another" report :). Questions: 1) do you do any async for the INVITE in this crash ? 2) if it is an YES to (1), is the caller party generating the "503 Service Unavailable" (which triggers the crash) - 10.32.2

Re: [OpenSIPS-Devel] OpenSIPS Crash

ate: Friday, May 10, 2019 at 6:31 PM To: OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash I found this in the log at the time of the crash: kernel: opensips[5003]: segfault at 30 ip 7fbd4c8f59d0 sp 7ffcaa850c80 error 6 in tm.so[7fbd4c887000+8e000] Ben Newlin

Re: [OpenSIPS-Devel] OpenSIPS Crash

: *Devel on behalf of Ben Newlin *Reply-To: *OpenSIPS devel mailling list *Date: *Friday, May 10, 2019 at 6:31 PM *To: *OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash I found this in the log at the time of the crash: kernel: opensips[5003]: segfault at

Re: [OpenSIPS-Devel] OpenSIPS Crash

> > > Please let me know if any further information can be useful. > > Ben Newlin > > From: Devel on behalf of Ben Newlin > > Reply-To: OpenSIPS devel mailling list > Date: Friday, May 10, 2019 at 6:31 PM > To: OpenSIPS devel mailling list > Subjec

Re: [OpenSIPS-Devel] OpenSIPS Crash

From: Devel on behalf of Ben Newlin Reply-To: OpenSIPS devel mailling list Date: Friday, May 10, 2019 at 6:31 PM To: OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash I found this in the log at the time of the crash: kernel: opensips[5003]: segfault at 30 ip

Re: [OpenSIPS-Devel] OpenSIPS Crash

To: OpenSIPS devel mailling list Subject: [OpenSIPS-Devel] OpenSIPS Crash Hello, We had a crash today of our OpenSIPS instance. Backtrace is here: https://pastebin.com/QbRJimwx # opensips -V version: opensips 2.4.5 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC

[OpenSIPS-Devel] OpenSIPS Crash

Hello, We had a crash today of our OpenSIPS instance. Backtrace is here: https://pastebin.com/QbRJimwx # opensips -V version: opensips 2.4.5 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024,

Re: [OpenSIPS-Devel] OpenSIPS Crash

Yes, Liviu provided the specific commit in another message and I have upgraded. Thanks again! Ben Newlin From: Bogdan-Andrei Iancu Date: Tuesday, November 20, 2018 at 7:38 AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, The fix is now

Re: [OpenSIPS-Devel] OpenSIPS Crash

Newlin wrote: Bogdan, That is excellent news! Thank you very much for your work on this and Liviu as well! Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Monday, November 19, 2018 at 9:03 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi

Re: [OpenSIPS-Devel] OpenSIPS Crash

Hi Ben, Not sure if you noticed yet, but the fix is already available here [1].  Thank you for all the help! Cheers, [1]: https://github.com/OpenSIPS/opensips/commit/e25895624b1c815dd8 Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 19.11.2018 17:31, Ben Newlin wrote:

Re: [OpenSIPS-Devel] OpenSIPS Crash

Bogdan, That is excellent news! Thank you very much for your work on this and Liviu as well! Ben Newlin From: Bogdan-Andrei Iancu Date: Monday, November 19, 2018 at 9:03 AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, With some

Re: [OpenSIPS-Devel] OpenSIPS Crash

mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, DO you have the backtraces from more similar crashes ? may there is a pattern there. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com<http://www.opensips-solutions.

Re: [OpenSIPS-Devel] OpenSIPS Crash

that would resolve the issue? Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Tuesday, November 13, 2018 at 9:13 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, Thanks for the info. The crash happens when you try to set an acc extra

Re: [OpenSIPS-Devel] OpenSIPS Crash

*Date: *Thursday, November 15, 2018 at 7:06 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often this crash happens ? are you able to reproduce it ? The acc extra should work in the branch route, no problem. Out of curiosity, I

Re: [OpenSIPS-Devel] OpenSIPS Crash

, November 15, 2018 at 7:06 AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, How often this crash happens ? are you able to reproduce it ? The acc extra should work in the branch route, no problem. Out of curiosity, I will try to reproduce you case

Re: [OpenSIPS-Devel] OpenSIPS Crash

: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, Thanks for the info. The crash happens when you try to set an acc extra variable in branch route (when a creating a new branch via failure route, on timeout). Now, do you use the drop accounting in your script ? and considering the above scenario

Re: [OpenSIPS-Devel] OpenSIPS Crash

the call, so I’m not sure how that would resolve the issue? Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Tuesday, November 13, 2018 at 9:13 AM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, Thanks for the info. The crash happens whe

Re: [OpenSIPS-Devel] OpenSIPS Crash

reproduced today. Backtrace is available here: https://pastebin.com/CZxQnZdR. Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Wednesday, November 7, 2018 at 6:18 AM *To: *OpenSIPS devel mailling list , Ben Newlin *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, The BT indicates a double

Re: [OpenSIPS-Devel] OpenSIPS Crash

November 1, 2018 at 1:19 PM To: Ben Newlin <mailto:ben.new...@genesys.com>, OpenSIPS devel mailling list <mailto:devel@lists.opensips.org> Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, According to the backtrace, the memory debugger was not activated. Do an "opensips

Re: [OpenSIPS-Devel] OpenSIPS Crash

Cwq> Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Thursday, November 1, 2018 at 1:19 PM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, According to the backtrace, the memory debugger was not activated. Do an "opensips -

Re: [OpenSIPS-Devel] OpenSIPS Crash

://pastebin.com/KTQjkCwq <https://pastebin.com/KTQjkCwq> Ben Newlin *From: *Bogdan-Andrei Iancu *Date: *Thursday, November 1, 2018 at 1:19 PM *To: *Ben Newlin , OpenSIPS devel mailling list *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, According to the backtrace, the memory de

Re: [OpenSIPS-Devel] OpenSIPS Crash

Date: Thursday, November 1, 2018 at 1:19 PM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, According to the backtrace, the memory debugger was not activated. Do an "opensips -V" to check the resulting compile flags - do you see the

Re: [OpenSIPS-Devel] OpenSIPS Crash

m: *Bogdan-Andrei Iancu <mailto:bog...@opensips.org> *Date: *Friday, October 26, 2018 at 4:59 AM *To: *OpenSIPS devel mailling list <mailto:devel@lists.opensips.org>, Ben Newlin <mailto:ben.new...@genesys.com> *Subject: *Re: [OpenSIPS-Devel] OpenSIPS

Re: [OpenSIPS-Devel] OpenSIPS Crash

if that is expected or not. Ben Newlin From: Bogdan-Andrei Iancu Date: Monday, October 29, 2018 at 8:11 AM To: Ben Newlin , OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, You can change the compile flags via the Makefile.conf file - the menuconfig is also

Re: [OpenSIPS-Devel] OpenSIPS Crash

*To: *OpenSIPS devel mailling list , Ben Newlin *Subject: *Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, all the BT's points to crashes while doing memory ops. I suspect a memory corruption that randomly triggers crashes in different parts of the code. Could you try to re-compile with memory

Re: [OpenSIPS-Devel] OpenSIPS Crash

settings we can change ourselves and bypass menuconfig? Ben Newlin From: Bogdan-Andrei Iancu Date: Friday, October 26, 2018 at 4:59 AM To: OpenSIPS devel mailling list , Ben Newlin Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Hi Ben, all the BT's points to crashes while doing memory ops. I suspect

Re: [OpenSIPS-Devel] OpenSIPS Crash

/Gmk1m4NT <https://pastebin.com/Gmk1m4NT> This crash follows the pattern of the original crash I reported. Ben Newlin *From: *Devel on behalf of Ben Newlin *Reply-To: *OpenSIPS devel mailling list *Date: *Monday, October 22, 2018 at 4:45 PM *To: *OpenSIPS devel mailling list *Subject: *Re: [Op

Re: [OpenSIPS-Devel] OpenSIPS Crash

/Gmk1m4NT This crash follows the pattern of the original crash I reported. Ben Newlin From: Devel on behalf of Ben Newlin Reply-To: OpenSIPS devel mailling list Date: Monday, October 22, 2018 at 4:45 PM To: OpenSIPS devel mailling list Subject: Re: [OpenSIPS-Devel] OpenSIPS Crash Here is a better

Re: [OpenSIPS-Devel] OpenSIPS Crash

Here is a better trace of the call: https://pastebin.com/gWpQR8E7 Ben Newlin From: Ben Newlin Date: Monday, October 22, 2018 at 4:34 PM To: OpenSIPS devel mailling list Subject: OpenSIPS Crash Hello, We have been having sporadic crashes and I was recently able to recover a core dump for

[OpenSIPS-Devel] OpenSIPS Crash

Hello, We have been having sporadic crashes and I was recently able to recover a core dump for one. I have uploaded it here: https://pastebin.com/ABktcYcH. I picked out a Call-ID from the crash data and took a look in our tracing. I have uploaded it here: https://pastebin.com/ZEzUUKZ5. It

Re: [OpenSIPS-Devel] [opensips] Crash on MySQL ACC Insert (#821)

Hi @apsaras , please provide me, off line, the access to investigate. Can you reproduce the crash ? Regards, Bogdan --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] Crash on MySQL ACC Insert (#821)

Closed #821 via d837ed865db8dbcf09ce5eac0ce0f160c2ec0e55. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/821#event-595832446___ Devel

Re: [OpenSIPS-Devel] [opensips] Crash on MySQL ACC Insert (#821)

Thank you @apsaras for the help - the bug was found and currently @apsaras is testing the fix. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[OpenSIPS-Devel] [opensips] Crash on MySQL ACC Insert (#821)

Hello I get few core dumps per day on a pre-production system based on latest 2.1.2 git revision: 6d126a1. OS: Debian 7 64bit MySQL: 5.5.47 Installed on VMWare. #0 0x7fc043b0c789 in db_mysql_val2bind (v=v@entry=0x7fc041a33da0 , binds=binds@entry=0x7fc043fae078,

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

The fix is available on GIT repo. @46labs please update if the fix holds for you --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/723#issuecomment-171277652___ Devel mailing list Devel@lists.opensips.org

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

It is optimized out ``` (gdb) bt full #0 0x7f3f5e0c93bd in check_and_split_time_list (uticks=122135690, set=) at timer.c:809 tl = 0x0 end = 0x7f3f5812b858 ret = #1 utimer_routine (uticks=122135690, set=) at timer.c:1075 tl = tmp_tl =

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

@ovidiusas , in your crash, is frame 1 utimer_routine too ? if yes, can you check the id you have there ? --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/723#issuecomment-169319687___ Devel mailing

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

thanks @ovidiusas --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/723#issuecomment-169343561___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

[OpenSIPS-Devel] [opensips] crash in dlg_hash +791 (#730)

Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fa0585613ea in unref_dlg (dlg=0x7fa0609fcea8, cnt=1) at dlg_hash.c:791 791 d_entry = &(d_table->entries[dlg->h_entry]); Traceback (most recent call last): File

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

I noticed there is some code already there that tries to debug this issue. Can you please try to compile the ```tm``` module with the ```TM_TIMER_DEBUG``` flag set? --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

I can confirm this is happening in 2.2 as well. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/723#issuecomment-164775504___ Devel mailing list Devel@lists.opensips.org

Re: [OpenSIPS-Devel] [opensips] crash on tm/timer.c (#723)

BT from 2.2 (gdb) bt full #0 0×7f5800362cc9 in check_and_split_time_list (timer_list=0×7f58017dec50, time=time@entry=4717000) at timer.c:809 tl = 0×0 end = 0×7f58017dec80 ret = #1 0×7f5800365751 in utimer_routine (uticks=4717000, set=) at timer.c:1075 tl = tmp_tl = id = 6

Re: [OpenSIPS-Devel] [opensips] crash if initial db connection is failing (#683)

Closed #683. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/683#event-463703046___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] crash if initial db connection is failing (#683)

fixed with https://github.com/OpenSIPS/opensips/commit/c4ebfc87fea74bcb3ab7b544e02fd5f68edf6e54 --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/683#issuecomment-156463414___ Devel mailing list

[OpenSIPS-Devel] [opensips] crash if initial db connection is failing (#683)

latest opensips 2.1 tcp_start_process() is called with startup_done set to NULL and then when init_child() failed, an initialization to -1 is attempted. ``` (gdb) bt full #0 tcp_start_processes (chd_rank=chd_rank@entry=0x84d7d0 , startup_done=startup_done@entry=0x0) at net/net_tcp.c:1723

[OpenSIPS-Devel] OpenSIPS crash

Hello OpenSIPS developers, We had OpenSIPS crashed. Please, find attached crash full stack trace from core file attached. OpenSIPS version: version: opensips 1.11.5-notls (x86_64/linux) flags: STATS: On, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC,

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

@dbeskoek , I sent you on last Friday, by email, a patch to be tested. Any luck with that ? --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/589#issuecomment-129476611___ Devel mailing list

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

sorry, for the delay. I did several tests with the patch, all of them were fine, no crash appears. I reverted to GIT-version and the crash occurs again. Patch is working :-) --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

Great @dbeskoek , especially that the faulty line was the log line itself, not the useful code. I will commit and backport asap Thanks and regards, Bogdan --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

Closed #589. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/589#event-378117425___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

@dbeskoek , could you do a list in gdb, to see what is your line 766 ? In my case it is a LM_WARN : LM_WARN(alias already present and points to another connection (%d : %d and %d : %d)\n, a-parent-id, port, c-id, port); Is this correct ? --- Reply to this email directly or

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

thats correct: ``` 761 LM_ERR(no connection found for id %d\n,id); 762 return -1; 763 error_sec: 764 TCPCONN_UNLOCK(id); 765 LM_WARN(possible port hijack attempt\n); 766 LM_WARN(alias already present and points to another connection

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

Is there any chance to get direct access to the corefile (ssh?) the debugging gets a bit more complex at this stage. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/589#issuecomment-128424797___ Devel

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

ok, try printing in gdb the vars: a, a-parent, c --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/589#issuecomment-128418538___ Devel mailing list Devel@lists.opensips.org

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

``` (gdb) p a $1 = (struct tcp_conn_alias *) 0x7f31115f35d8 (gdb) p a-parent $2 = (struct tcp_connection *) 0x0 (gdb) p c $3 = (struct tcp_connection *) 0x7f311a308470 ``` --- Reply to this email directly or view it on GitHub:

[OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

During running a sipp-scenario against an opensips2.1 doing tls-udp traversing we are able to easily crash this opensips within seconds. As soon as we disable tcp_accept_aliases the crashes are gone. We are heavily generating new tls-sessions (around 1000 per second), so we will reuse

Re: [OpenSIPS-Devel] [opensips] crash issue in tcpconn_add_alias (2.1) (#589)

Hi Bogdan, yes, latest 2.1code from GIT was used. requested output: ``` #0 0x0052247a in tcpconn_add_alias (id=1358, port=5063, proto=3) at net/net_tcp.c:766 c = 0x7f311a308470 hash = 938 a = 0x7f31115f35d8 __FUNCTION__ = tcpconn_add_alias ``` --- Reply

Re: [OpenSIPS-Devel] [opensips] Crash with poorly given var (#529)

Closed #529. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/529#event-319737566___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

[OpenSIPS-Devel] [opensips] Crash with poorly given var (#529)

Although core variables correctly handle this error, OpenSIPS will segfault when a module variable is given instead: startup_route { #works $(ru(foo)) = foo; #crashes $(DLG_dir(foo)) = 5; line 9: 5074 Segmentation fault (core dumped) ./opensips -m

Re: [OpenSIPS-Devel] [opensips] Crash with nested $param variables (#412)

Closed #412 via f3ed4db9903d85cba7d7d491c931b550e29932d1. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/412#event-245330670___ Devel mailing list Devel@lists.opensips.org

[OpenSIPS-Devel] [opensips] Crash with nested $param variables (#412)

Present in OpenSIPS 1.9+. route [route_b] { # Evaluating $param(1) leads to infinite recursion! xlog(This should not crash: $param(1)\n); } route [route_a] { route(route_b, $param(1)); } route { route(route_a, test); ... } --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] crash in v1.11.3 using fifo pres_phtable_list (#382)

Hi @bogdan-iancu you are right, I only need pua for pua_dialoginfo and pua_usrloc. Include presence modules was my mistake, are not necesary, thanks for the point. Nowadays i think your patch is essential because avoid the crash, I will apply it. Thank you so much --- Reply to this email

Re: [OpenSIPS-Devel] [opensips] crash in v1.11.3 using fifo pres_phtable_list (#382)

Closed #382. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/382#event-187888632___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

[OpenSIPS-Devel] [opensips] crash in v1.11.3 using fifo pres_phtable_list (#382)

Hello Devels: Making some tests with version 1.11.3 I've just discover how to casue a crash simply calling pres_phtable_list using fifo (opensipsctl fifo pres_phtable_list). I execute this command in a proxy that is not acting as presence server, but must have the presence modules loaded

Re: [OpenSIPS-Devel] [opensips] crash in v1.11.3 using fifo pres_phtable_list (#382)

Hi @telematico - I uploaded a commit to fix the crash ; the fix disables the MI commands in presence module when used in library mode. Still, if you want to use pua_dialoginfo, only pua module is required; presence module is not (if you have another OpenSIPS acting as presence server..What

Re: [OpenSIPS-Devel] [opensips] crash while creating avp (#230)

Closed #230. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/230#event-134145317___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] Crash in pua_dialoginfo (#70)

Closed #70. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/70#event-122372695___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Re: [OpenSIPS-Devel] [opensips] crash while creating avp (#230)

@ovidiusas , could you email me please the complete backtrace (all stacks). @liviuchircu mentioned that this is related to B2B usage - is it right ? --- Reply to this email directly or view it on GitHub:

[OpenSIPS-Devel] [opensips] crash while creating avp (#230)

Latest trunk: version: opensips 1.12.0dev-notls (x86_64/linux) git revision: 0338917 Relevant info: ``` #0 0x005157b2 in fm_remove_free (n=0x7fb977efa590, qm=0x7fb977b1d000) at mem/f_malloc.c:172 172 *pf=n-u.nxt_free; (gdb) bt #0 0x005157b2 in fm_remove_free

Re: [OpenSIPS-Devel] [opensips] Crash in pua_dialoginfo (#70)

@nikbyte , do you still have the corefile (available for inspection) ? or can you reproduce it and get a new core ? I would need some more info from the corefile, just to validate a theory of mine on how this crash happens. Thanks, Bogdan --- Reply to this email directly or view it on GitHub:

  1   2   >