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
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
: 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: Devel on
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
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
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,
: 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
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
list
*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
relat
mailto: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)
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
] 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,
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) is
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
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
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
lto:devel@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
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
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
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 a
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
://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
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
, 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 to
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
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
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
://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
ogdan-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 shme
: 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
ptrace) 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 INV
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
: 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
: *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
>
>
> 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
> Subject:
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
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
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, MAX_RECV_BUFF
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
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
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:
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
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.
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
*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
, 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
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, it
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
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
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 -V&q
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 -V&qu
://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
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
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 Cra
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
*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 m
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 su
n.com/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
/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
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 one.
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 appe
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:
https://github.com/OpenSIPS/opensips/issues/821#issuecomme
Hello Bogdan
No I can not reproduce it. I will send you a pm for access.
Regards
---
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#issuecomment-198005149___
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 ma
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:
https://github.com/OpenSIPS/opensips/issues/821#issuecomment-198308415__
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, i=i@entry=21) at val.c:
@46labs confirmed the patch fixed his crash.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/723#issuecomment-172511655___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/ma
Closed #723.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/723#event-517848993___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
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
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
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 =
@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 list
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
"/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/l
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:
https://github.com/OpenSIPS/opensips/issues/723#issuecomment-164814684__
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 FU
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
http://lists.opensips.org/cgi-bin
opensips 2.1.1
git revision: 139415b
Program terminated with signal 11, Segmentation fault.
#0 0x7f3f5e0c93bd in check_and_split_time_list (uticks=122135690,
set=) at timer.c:809
809 while( tl!=end && tl->time_out <= time)
(gdb) print tl
$1 = (struct timer_link *) 0x0
(g
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
Devel@lis
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
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
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, FAST_LOC
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
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:
https://github.com/OpenSIPS/opensips/issues/589#issuecomment-129483
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:
https://github.com/OpenSIPS/opensips/issues/589#issuecomment-129484192_
@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
Devel@lists.o
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 m
ok, so a->parent->id is crashing...let me check on it
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/589#issuecomment-128421511___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/c
```
(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:
https://github.com/OpenSIPS/opensips/issues/589#issuecomment-128420950
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
http://lists.opensips.org/cgi
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 connecti
@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 direct
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
Hi @dbeskoek , are you using the latest 2.1 code from GIT ?
can you recompile without optimization (see Makefile.defs, line 722, removing
-O9) and check in the corefile the a variable ?
Regards, Bogdan
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/
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 source-
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
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
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
http://lists.opensips.org/cgi-
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 GitHu
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
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 direc
1 - 100 of 118 matches
Mail list logo