<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="monospace">Hi Richard,<br>
      <br>
      Those warning means that a certain timer is really busy,
      overlapping between executions - here is about the tm-utimer,
      responsible for performing the stateful retransmissions (upon 
      missing replies). Such a timer may get slow due to TCP stuff, like
      trying to retransmit to disconnected connections. <br>
      <br>
      Best regards,<br>
    </font>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
  <a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
    <div class="moz-cite-prefix">On 26.06.2025 01:24, Richard Revels via
      Users wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAE-NtRfWwiHEKk=upiJpe-Uh-R2YXxEJ3-06=CFr3e_hdv1U8w@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div><br clear="all">
        </div>
        <div>
          <div dir="ltr" class="gmail_signature"
            data-smartmail="gmail_signature">
            <div dir="ltr">
              <div>
                <div dir="ltr">
                  <div>
                    <div dir="ltr">
                      <div>
                        <div dir="ltr">
                          <div>
                            <div dir="ltr"><span>
                                <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"> </p>
                                <div dir="ltr" style="margin-left:0pt">
                                  <div class="gmail_default"
style="font-family:"courier new",monospace">Ah, Thank You. 
                                    Yes, I have come to the
                                    same conclusion that those messages
                                    are after the problem rather than
                                    before.   I didn't take enough time
                                    to really dig into the logs before
                                    send that message I reckon.</div>
                                  <br>
                                </div>
                              </span></div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <div class="gmail_quote gmail_quote_container">
        <div dir="ltr" class="gmail_attr">On Wed, Jun 25, 2025 at
          1:20 PM Gregory Massel via Users <<a
            href="mailto:users@lists.opensips.org"
            moz-do-not-send="true" class="moz-txt-link-freetext">users@lists.opensips.org</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>I get these on my most lightly loaded system, yet none at
              all on my most heavily loaded system...<br>
            </p>
            <p>Although the error is generic enough that, on its own, it
              doesn't really help to determine what the problem is, on
              my system the tm-utimer messages are often accompanied by
              TLS errors such as:<br>
            </p>
            <p>ERROR:tls_wolfssl:_wolfssl_tls_conn_shutdown: no ssl data</p>
            <p>ERROR:tm:msg_send: send() to x.x.x.x:5061 for proto tls/3
              failed</p>
            <p>(Note: While I'm currently using WolfSSL, I previously
              used OpenSSL and experienced similar issues.)</p>
            <div>That's not to say that you're getting the error for the
              same reason as me; just to point out that there should be
              related errors before or after the tm-utimer warnings. It
              may be tricky to find them on a system with your sorts of
              volumes as, in my case, the TLS errors are typically just
              over 2 minutes AFTER the tm-utimer warnings. On a busy
              system, a lot of unrelated log entries are likely to
              generate in between.</div>
            <div><br>
            </div>
            <div>The low-load system with these issue has outbound TLS.
              The high-load system without these issues does no outbound
              TLS; the only TLS it handles are inbound WSS connections.<br>
            </div>
            <div><br>
            </div>
            <div>With regard to your question about threads, take a look
              at:</div>
            <div><a
href="https://www.opensips.org/Documentation/Script-CoreParameters-3-4#tcp_workers"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://www.opensips.org/Documentation/Script-CoreParameters-3-4#tcp_workers</a></div>
            <div><a
href="https://www.opensips.org/Documentation/Script-CoreParameters-3-4#udp_workers"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://www.opensips.org/Documentation/Script-CoreParameters-3-4#udp_workers</a></div>
            <div><br>
            </div>
            <div>--Greg<br>
            </div>
            <div><br>
            </div>
            <div>On 2025-06-24 18:52, Richard Revels via Users wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">
                <div>Greetings,<br>
                  I have started having issues with some proxies running
                  opensips 3.2.19 and some others running 3.4.12<br>
                  With approximately 230 cps and 7300 dialogs the proxy
                  starts emitting log messages like<br>
                  <br>
                  Jun 24 15:42:18 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 150 ms ago (now
                  3671145080 ms), delaying execution<br>
                  Jun 24 15:42:18 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 200 ms ago (now
                  3671145130 ms), delaying execution<br>
                  Jun 24 15:42:18 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 300 ms ago (now
                  3671145230 ms), delaying execution<br>
                  Jun 24 15:42:18 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 400 ms ago (now
                  3671145330 ms), delaying execution<br>
                  Jun 24 15:42:18 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 500 ms ago (now
                  3671145430 ms), delaying execution<br>
                  Jun 24 15:42:19 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 600 ms ago (now
                  3671145530 ms), delaying execution<br>
                  Jun 24 15:42:19 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 700 ms ago (now
                  3671145630 ms), delaying execution<br>
                  Jun 24 15:42:19 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 800 ms ago (now
                  3671145730 ms), delaying execution<br>
                  Jun 24 15:42:19 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:utimer_ticker: utimer task
                  <tm-utimer> already scheduled 900 ms ago (now
                  3671145830 ms), delaying execution<br>
                  Jun 24 15:42:19 sip-proxy.local
                  /usr/local/opensips/sbin/opensips[190328]:
                  WARNING:core:timer_ticker: timer task <tm-timer>
                  already scheduled 1000 ms ago (now 3671145830 ms),
                  delaying execution<br>
                  <br>
                  <br>
                  The cpu usage on the threads goes from 3% - 11%
                  depending on thread to 30% across the board.<br>
                  <br>
                  I have been running these versions of opensips for
                  some time now (months for 3.4 and years for 3.2) and
                  do see occasional latency in db or rest connection
                  responses but only recently have started having this
                  issue.<br>
                  <br>
                  So,<br>
                  <br>
                  How are SIP calls distributed across the processing
                  threads?  I was thinking it would be round robin w/
                  attention given to busy or not.  but it seems like the
                  lower pid threads do a lot more work on these proxies<br>
                  <br>
                  What are possible causes of the timers having trouble
                  completing tasks?  is it cpu use, waiting on some
                  other task to finish, combination or more?<br>
                  <br>
                  Is there tuning that can be done to have more timer
                  handling threads?  i tried this with modparam("tm",
                  "timer_partitions") which seemed to make the problem
                  worse<br>
                  <br>
                  Thank you in advance for any guidance you can give me
                  on troubleshooting this issue.<br>
                  Richard Revels</div>
                <div>
                  <div dir="ltr" class="gmail_signature">
                    <div dir="ltr">
                      <div dir="ltr">
                        <div dir="ltr">
                          <div dir="ltr"><span>
                              <p
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br>
                              </p>
                            </span></div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
              <br>
              <fieldset></fieldset>
              <pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
              target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
            </blockquote>
          </div>
          _______________________________________________<br>
          Users mailing list<br>
          <a href="mailto:Users@lists.opensips.org" target="_blank"
            moz-do-not-send="true" class="moz-txt-link-freetext">Users@lists.opensips.org</a><br>
          <a
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
            rel="noreferrer" target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-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>