Hi Ryan,
On 16.11.2010, at 18:17, thrillerbee wrote:
> John,
>
> I appreciate the suggestion, but, unfortunately, I don't use t_newtran().
> What led you to remove that?
Hm, sorry…
I was removing some functions from my opensips.cfg, then running various stress
tests (REGISTER, INVITE etc.)
Bogdan,
Are these memlogs useful? Please let me know if I can provide any other
info.
Thanks again.
On Sat, Nov 13, 2010 at 4:20 PM, thrillerbee wrote:
> Bogdan,
>
> Since I made those changes, it doesn't core dump anymore - it just runs out
> of memory and stops processing packets. It happe
John,
I appreciate the suggestion, but, unfortunately, I don't use t_newtran().
What led you to remove that?
Thanks,
Ryan
On Tue, Nov 16, 2010 at 9:08 AM, John Khvatov wrote:
> Hello.
>
> On 10.11.2010, at 19:19, thrillerbee wrote:
>
> Well, I spoke too soon - it's not just an issue with the
Hello.
On 10.11.2010, at 19:19, thrillerbee wrote:
> Well, I spoke too soon - it's not just an issue with the opensipsctl fifo
> calls - looks more like a memory leak. It crashed again today, but I did get
> some errors in the syslog this time right before the crash:
> Nov 10 15:42:32 core1 /us
Hi,
opensipsctl takes care that each command takes a separate fifo reply, so
here it should be no problem. But the problem may be when comes with
sending multiple commands (via FIFO) in the same time - this translates
into parallel writes to the same file and depends on the atomicity of
the w
Bogdan,
Since I made those changes, it doesn't core dump anymore - it just runs out
of memory and stops processing packets. It happened on both of my proxies -
the mem dump can be downloaded here:
http://www.starviewconnect.com/tmp/core1_mem_dump_20101112.gz
http://www.starviewconnect.com/tmp/cor
Bogdan,
I had already increased the PKG_MEM_POOL_SIZE by *10. I'm making the
changes suggested in the link you provided to try to narrow down the memory
issue. I'll send over as soon as I have another crash with mem info.
Thanks.
On Thu, Nov 11, 2010 at 5:10 AM, Bogdan-Andrei Iancu wrote:
>
This last crash had the same bt as the one from previous email ? the
prev fix I made reports this:
ERROR:db_flatstore:flat_db_insert: uninitialized connection
and does not crash, so this time the crash may be in a different place.
Now, it seams after all that the root of your problem is
My other proxy crashed as well with these ERRORs in the syslog:
Nov 10 22:01:02 core2 /usr/local/sbin/opensips[22959]:
ERROR:db_flatstore:get_name: pkg memory allocation failure
Nov 10 22:01:02 core2 /usr/local/sbin/opensips[22959]:
ERROR:db_flatstore:flat_reopen_connection: failed to get_name
Nov
Bogdan,
Well, I spoke too soon - it's not just an issue with the opensipsctl fifo
calls - looks more like a memory leak. It crashed again today, but I did
get some errors in the syslog this time right before the crash:
Nov 10 15:42:32 core1 /usr/local/sbin/opensips[27044]:
ERROR:db_flatstore:new_
Bogdan,
It seems the issue is with 'opensipsctl fifo' - it's very sensitive to
simultaneous calls. Basically, I've combined all my scripts to prevent
'opensipsctl fifo' from being called too frequently and that seems (so far)
to have mitigated the issue. Is there anything one should know about h
Hi,
strange if you do not have any errors :(
I just made a fix on both trunk and 1.6 to extend some checks in
flatstore and prevent crashing (even if the DB op will not be executed).
Could you update from SVN and see if stops crashing ?
Regards,
Bogdan
thrillerbee wrote:
> Bogdan,
>
> I
Bogdan,
I am not seeing any other errors in the logs. Is there anything else I can
look at? Both proxies are crashing everyday.
Thanks.
On Wed, Nov 3, 2010 at 4:21 AM, Bogdan-Andrei Iancu
wrote:
> I got some clue about what is happening - as you are using flatstore for
> acc, the acc module d
I got some clue about what is happening - as you are using flatstore for
acc, the acc module does not check the success of the "use_table" DB
operation - in 90% of the cases (for mysql, postgres, etc) this function
cannot fail, but it seams that for flatstore can. And if it fails, the
h->tail i
Bogdan,
One more detail that may help - I added another OpenSIPS proxy in parallel
with this one (& load balancing between the two) and now both OpenSIPS
proxies crash at the same time (within a couple seconds).
I can provide more core dumps if it will help.
Thanks.
On Tue, Nov 2, 2010 at 9:02
Bogdan,
Below is the info requested:
(gdb) frame 0
#0 0x7f51999f221f in flat_db_insert (h=0x7f0978, k=0x7f5198732a60,
v=0x7f5198732d20, n=19) at flatstore.c:165
165 f = CON_FILE(h);
(gdb) print h
$1 = (const db_con_t *) 0x7f0978
(gdb) print h->tail
$2 = 0
(gdb) print ((struct flat
Hi,
in frame 0, could you print:
h
h->tail
((struct flat_con*)(h->tail))->file
Also, before crash, do you see in the logs any errors from the
db_flatstore module ?
Regards,
Bogdan
thrillerbee wrote:
> Bogdan,
>
> It crashed again tonight. I've attached the backtrace.
>
> Thanks.
>
Bogdan,
It crashed again tonight. I've attached the backtrace.
Thanks.
On Mon, Nov 1, 2010 at 9:32 AM, thrillerbee wrote:
> Bogdan,
>
> Yes, I've attached 2 to my response - one was a crash from 10/29. The
> other occurred a few minutes ago.
>
> Thanks.
>
> On Fri, Oct 22, 2010 at 11:41 AM,
Bogdan,
Yes, I've attached 2 to my response - one was a crash from 10/29. The
other occurred a few minutes ago.
Thanks.
On Fri, Oct 22, 2010 at 11:41 AM, Bogdan-Andrei Iancu <
bog...@voice-system.ro> wrote:
> Any chance with the backtraces ?
>
> Regards,
> Bogdan
>
> Anca Vamanu wrote:
> > Hi
Any chance with the backtraces ?
Regards,
Bogdan
Anca Vamanu wrote:
> Hi,
>
> You need to inspect them with gdb, run: gdb
> path_to_opensips_executable path_to_corefile, and then run 'bt full'
> and send the output.
>
> Regards,
> --
> Anca Vamanu
> www.voice-system.ro
>
>
> On 10/14/2010 10:1
Hi,
You need to inspect them with gdb, run: gdb path_to_opensips_executable
path_to_corefile, and then run 'bt full' and send the output.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/14/2010 10:12 PM, thrillerbee wrote:
I have this info from dmesg:
[1985853.285221] opensips[30865]:
I have this info from dmesg:
[1985853.285221] opensips[30865]: segfault at 10 ip 7f43899ce21f sp
7fff8de1cf40 error 4 in db_flatstore.so[7f43899cb000+5000]
[1985856.379671] opensips[30858]: segfault at 10 ip 7f43899ce21f sp
7fff8de1cf40 error 4 in db_flatstore.so[7f43899cb000+5000]
[1985896.961279
When OpenSIPS crashes, three corefiles are generated that are 2.1GB in size.
How do I use these files to understand what's causing the crash?
Thanks.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/user
23 matches
Mail list logo
