Hello,
according to the trace, the crash trace is:
#0 0x7f544c119801 in _IO_default_xsputn_internal () from
/lib64/libc.so.6
No symbol table info available.
#1 0x7f544c0e93a9 in vfprintf () from /lib64/libc.so.6
No symbol table info available.
#2 0x7f544c0f4368 in fprintf () from /
Hi Daniel,
yes, Kamailio 4.1 using syslog:
log_facility=LOG_LOCAL4
# modules
loadmodule "xlog.so"
# kamailio -v
version: kamailio 4.1.6 (x86_64/linux) 010d57
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, P
I looked at the last gdb trace you sent and the crash is inside syslog()
function, which prints a message with static text, if I matched it with
the right version of the sources.
Is the trace from running kamailio 4.1? What is the output of:
kamailio -v
Cheers,
Daniel
On 04/12/14 17:23, Daniel-
On 05/12/14 04:38 AM, Juha Heinanen wrote:
what has been the motivation that rtpengine control protocol is using
udp instead of tcp or ssl?
we have noticed that reply to delete containing stats is too large for a
single udp packet over ethernet and causes udp fragmentation and
fragmentation need
what has been the motivation that rtpengine control protocol is using
udp instead of tcp or ssl?
we have noticed that reply to delete containing stats is too large for a
single udp packet over ethernet and causes udp fragmentation and
fragmentation needed requests.
-- juha
__
