Hello,
can you do 'top' and see what is the pid of the process using a lot of cpu, then get the backtrace with gdb?
gdb /path/to/kamailio PID bt full
It will help to see what kamailio is trying to do.
Cheers, Daniel
On 22/10/15 10:45, Stefan Kohlhauser wrote:
Hello everyone!
Setup: I am currently using a Kamailio 4.2.3 on an embedded device (low CPU and RAM). The device is not able to store the current date, so after a reboot its 1. Jan 1970 until NTP updates the date.
Problem: If the date is updated after the Kamailio has started (a leap of 45 years) the Kamailio uses up all the CPU and renders the device useless for a very long time.
Notes: There are no incomming requests at the time. (But the Kamailio is not responsive during that time anyway.) Adjusting the internal Kamailio-time seems to take longer when the date update leap is bigger.
My questions:
- Can I prevent the Kamailio from using up the entire CPU after a date update? Or maybe do the internal ticks-update more gracefully?
- For my better understanding: What happens within the Kamailio after adjust_ticks has updated the internal date?
Thanks in advance for your help!
Best regards, Stefan
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users