Hello,
I write directly to you in case you can grant access to the system.
Otherwise I need also the output of 'p *dead_cell' for the core that has
the frame 0:
#0 0x7f6af0b90b70 in free_cell_helper (dead_cell=0x7f6ab0a6baa8,
silent=0, fname=0x7f6af0c8f630 "timer.c", fline=654) at h_table.c
Hi Daniel,
This happens randomly. It is not a testbed and never reproducible on the
test server. I can still give you access if you wish to analyse the core
files to check whats happening here exactly.
It simply feels like on heavy load the evapi socket gives up. Earlier I was
running 5.0.2 and in
Hello,
are you able to reproduce it somehow? Or just happens randomly?
Is it on a testbed where I could get access to investigate the
corefiles? If not, then I will ask for more details from cores over
email, first would be 'bt full' for both cores and 'p *dead_cell' for
the second one.
Cheers,
Hi Daniel,
Have got these core dumps. Let me know if I should be doing a bt full. I'll
pastebin and send. Thanks,
Core was generated by `/usr/local/kamailio/sbin/kamailio -P
/var/run/siptrunk.pid -f /usr/local/carrie'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00505
Hello,
the backtrace doesn't show any hint about kamailio, only from closelog() up.
It may be the core generated by shutdown procedure, have you enabled one
core file per pid/process? If not, do it and reproduce the issue again,
you may get two core files, one being the runtime issue and the othe
Hello,
I'm using kamailio 5.1.5 with evapi. I have a node.js connecting with
kamailio evapi to which I send events and also consume events based on
which I do the routing. I have 8 evapi workers defined in the config.
The problem is that kamailio randomly crashes on high load. I'm assuming
that it
