On Friday 25 June 2010, David wrote:
Using Kamailio 3.0.1 :
My syslog is being flooded with this :
WARNING: <core> [timer_funcs.h:111]: WARNING: timer: add_timeout: 0
expire timer added
Jun 25 12:23:55 kamailio-dev /usr/sbin/kamailio[11259]: DEBUG: pua
[hash.c:54]: ^Ietag= a.1276278619.9322.13398.2 - len= 25
Jun 25 12:23:55 kamailio-dev /usr/sbin/kamailio[11259]: DEBUG: pua
[hash.c:56]: ^Iid= DIALOG_PUBLISH.9b5f4c1c67b65f80(a)192.168.70.127
[..]
Hi David,
this all are debug messages, which are not appropriate to log in a production
setting. If you get too much messages in your logs, just increase the debug
level in your configuration.
Jun 25 12:23:56 kamailio-dev
/usr/sbin/kamailio[11259]: WARNING: <core>
[timer_funcs.h:111]: WARNING: timer: add_timeout: 0 expire timer added
Why is this timer being set to 0? What is this timer ? How do I set it
at a more reasonable value ? Because this is at 0 it is basically
consuming all my server resources cause the timer is completed
instantly, so the message repeats hundreds of times per second.
I'm not an expert with this module, but a quick check in the source code
reveals that there are two timers run:
* one for updating the DB
* one for expiration old hash table entries
They are both run every the update_period/ update_period - 5 seconds. The
update_period default is 100s. So normally this timer should not run that
often. Can you quote the parameter setting in your cfg?
Cheers,
Henning