20 Oct
2014
20 Oct
'14
6:11 a.m.
What are the differences between the server that works and the one that
doesn't? I mean hardware and operating system details?
Checking quickly the source code and comparing with logs, it doesn't
reveal any problem -- it is about allocation of the next fragment, which
was not used at all before, after the one allocated previously. The only
reason I can think of it right now is corrupted memory or faulty OS.
Daniel
On 20/10/14 11:56, 张顺通 wrote:
4.2 have the same problem.
at begin i use 4.1, i think this is a bug in 4.1; then i use 4.2 to
check to see if the problem is solved. problems still in.
see ka_4_2_0.log
ka_4_2_0.log
<https://docs.google.com/file/d/0B5x1TDtoeVvAckdMbDRmT3E3UjA/edit?usp=drive_web>
2014-10-20 17:48 GMT+08:00 张顺通 <shuntongzhang(a)gmail.com
<mailto:shuntongzhang@gmail.com>>:
ka.log is genrate by kamailio 4.1.6.
2014-10-20 17:44 GMT+08:00 Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>>:
Are you using 4.1 or 4.2?
Because the subject mentioned 4.2 but the version of kamailio
is 4.1
Daniel
On 20/10/14 11:39, 张顺通 wrote:
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
-M 12 can not help. all config is same.
see ka.log in attachment, kamailio version is 4.1.6
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,
PKG_MALLOC,
DBG_QM_MALLOC, USE_FUTEX,
FAST_LOCK-ADAPTIVE_WAIT,
USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST,
HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144,
MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT
PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 010d57
compiled on 16:48:03 Oct 20 2014 with gcc 4.1.2
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda
<http://twitter.com/#%21/miconda> -
http://www.linkedin.com/in/miconda