25 Jun
2012
25 Jun
'12
10 a.m.
Yes, I'll bt if it will appear again...
Here is a version:
# /opt/kamailio/sbin/kamailio -V
version: kamailio 3.2.3 (x86_64/linux)
flags: STATS: Off, USE_IPV6, 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: unknown
compiled on 15:37:11 Jun 9 2012 with gcc 4.4.3
2012/6/25 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
when it occurs again, get the backtrace with gdb using the PIDs from all
kamailio processes eating lot of CPU.
Btw, what version are you using (kamailio -V)?
Cheers,
Daniel
On 6/25/12 9:43 AM, Konstantin M. wrote:
do you have heavy traffic on that instance? How
many children have you
configured?
Yes, but only a voip. There are over 10k calls per day.
fork=yes
children=4
This configuration is working during 1.5 months without any issues till
now...
What you can do is to attach with gdb to a
process using lot of CPU and
do the backtrace:
gdb /path/to/kamailio __pid__
Replace __pid__ with the PID of process eating the CPU. Then run bt
It may be a deadlock/infinite loop somewhere. I saw three processes in
top, others
were down with no much cpu usage.
Is the SIP routing going fine anyhow when CPU
usage is high?
It hard to say 'yes', when looking to call graphs (rrd) I saw that the
calls throughput was slow down...
Looking to logs/PCAP's/etc I'm seeing that some of calls were processed
though (perhaps some of working forks).
But there were > 75-80% of failed calls with 478 Request Terminated.
Also by analyzing a PCAP flows I saw that more than 70% of calls were
de-jittered, de-sync'ed in RTP timestamps, etc...
How do you solve it, by restart or it just
appears from time to time and
solves itself periodically?
I did not restarted kamailio during 20 days, following a charts this
problem was re-appeared during 2 days.
After restart of kamailio -- I can't see any issues for now, there is 0.00
on CPU by all of kamailio instance/forks/etc...
Cheers,
Daniel
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw