26 Aug
2016
26 Aug
'16
9:18 a.m.
hi
almost all "gdb/bt full" contain:
#13 0x00000000005f916c in parse_disposition (s=0xa75468 tcp_reader_ltimer+228904,
disp=optimized out) at parser/parse_disposition.c:60
disp_p =
new_p =
state = 2
saved_state = 2
tmp = 0x7f161b681fc0 ""
end = 0x4020dd8800000000 error: Cannot access memory at address 0x4020dd8800000000
func = "parse_disposition"A lot of tcp errors in kamailio.log before the crush.
How to solve the issue?
On Tuesday, August 16, 2016 3:19 PM, Dmitry <mbike2000ru(a)yahoo.com> wrote:
hel
From time to time (it does not depend upon traffic) we
see in logs:
ERROR: <core> [tcp_read.c:274]: tcp_read_data(): error reading:
Bad file descriptor (9) ([ip_address]:49832 -> [ip_address]5060) ERROR: <core>
[tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error readingERROR: <core>
[io_wait.h:608]: io_watch_del(): trying to delete already erased entry 3031 in the hash(0,
0, (nil)) flags 10)CRITICAL: <core> [tcp_read.c:1654]: handle_io(): io_watch_del
failed for 0x7f8471c51820 id 867 fd 3031, state 0, flags 4018, main fd 179, refcnt 2
([ip_address]:49832 -> [ip_address]:5060)
there are a lot of such TCP CRITICAL errors and the kamailio crushes
kamailio -vversion: kamailio 4.3.5 (x86_64/linux)flags: STATS: Off, USE_TCP, USE_TLS,
TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP,
PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RESADAPTIVE_WAIT_LOOPS=1024,
MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT
PKG_SIZE 8MBpoll method support: poll, epoll_lt, epoll_et, sigio_rt, select.id:
unknowncompiled on 17:51:55 Mar 8 2016 with gcc 4.4.7
It is still not clear - what exactly causes such behaviour.
I want to recriate it in the lab - so what can cause it.?
May be a process erases the file descriptors of TCP connections?
Any help is appreciated.