<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Artem,<br>
<br>
In the uac_registrant DB, do you define registrar servers /
outbound proxies using DNS (FQDN names) instead of IPs ?<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 24.02.2016 02:50, Чалков Артём
wrote:<br>
</div>
<blockquote cite="mid:2432061456275007@web20o.yandex.ru" type="cite">
<div>Hi all!</div>
<div> </div>
<div>My opensips version:</div>
<div>opensips 2.1.2 (x86_64/linux)</div>
<div>git revision: 44cc594</div>
<div> </div>
<div>I use opensips with uac_registrant module and sometimes in
log appears these warnings (2-3 warnings every hour):</div>
<div> </div>
<div>Feb 17 21:34:56 opensips-uac /usr/sbin/opensips[12971]:
WARNING:core:timer_ticker: timer task <uac_reg_check>
already schedualed for 62923880 ms (now 62924880 ms), itmay
overlap..</div>
<div> </div>
<div>Timer offset leads me to approx. (with some little offset
like 1-10 minutes) time, when my opensips restarting every day
(via service opensips restart).</div>
<div> </div>
<div>In particular rare cases (1-2 times in month or rarely) it
leads to flood with below warnings:</div>
<div>
<p>Feb 17 21:59:36 opensips-uac /usr/sbin/opensips[12971]:
WARNING:core:timer_ticker: timer task <tm-timer> already
schedualed for 64393870 ms (now 64395870 ms), it may o<br>
verlap..<br>
Feb 17 21:59:36 opensips-uac /usr/sbin/opensips[12971]:
WARNING:core:utimer_ticker: utimer task <tm-utimer>
already schedualed for 64395870 ms (now 64395970 ms), it ma<br>
y overlap..<br>
Feb 17 21:59:36 opensips-uac /usr/sbin/opensips[12971]:
WARNING:core:utimer_ticker: utimer task <tm-utimer>
already schedualed for 64395970 ms (now 64396060 ms), it ma<br>
y overlap..</p>
<p>But every time it happens, warnings with uac_reg_check
appears first in large quantities. While it happens, opensips
starts to ignore most incoming traffic. In log with debug=4 i
doesn't see any unusual entrys before it starts. After some
time (2-3 hours) flood stops and problem disappears itself
without any workaround on my side. </p>
<p>I know about similar issue with radius (<a
moz-do-not-send="true"
href="http://comments.gmane.org/gmane.comp.voip.opensips.user/31415"><a class="moz-txt-link-freetext" href="http://comments.gmane.org/gmane.comp.voip.opensips.user/31415">http://comments.gmane.org/gmane.comp.voip.opensips.user/31415</a></a>),
but i'm not using radius in my configuration, so can it be
some new issue or it is a same issue and it would be resolved,
as planned, in v.2.2?</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>