<div dir="ltr"><div dir="ltr">Thanks Bogdan, <div><br><div>After more analysis, I noticed that the recv-queue buildup occurs only after the OpenSIPS service crashes. I’ve looked in all expected directories, but the core dump file is not present.</div><div><br>Below are the logs showing the sequence of events during the crash:<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1595]: CRITICAL:core:sig_usr: segfault in process pid: 1595, id: 46<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1503]: INFO:core:handle_sigs: child process 1595 exited by a signal 11<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1503]: INFO:core:handle_sigs: core was generated<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1503]: INFO:core:handle_sigs: terminating due to SIGCHLD<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1550]: INFO:core:sig_usr: signal 15 received<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1552]: INFO:core:sig_usr: signal 15 received<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1551]: INFO:core:sig_usr: signal 15 received<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1503]: INFO:core:shutdown_opensips: process 1(1550) [MI FIFO] terminated, still waiting for 51 more<br>Nov 22 11:46:58 opensips-3-1 /usr/local/sbin/opensips[1503]: INFO:core:shutdown_opensips: process 2(1551) [time_keeper] terminated, still waiting for</div></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Nov 11, 2025 at 4:13 PM Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@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"><u></u>
<div>
<font face="monospace">Hi,<br>
<br>
Have you checked the internal load of opensips, by running the
`ps` and `get_statistics load:` MI cmds ?<br>
<br>
I suspect some blocking I/O operation is blocking the OpenSIPS
timer processes, resulting in the reported warning logs.<br>
<br>
Also, if possible (not sure in docker) you should run
`opensips-cli -x trap` to get an instant x-ray of what the
opensips processes are doing, maybe this will help spotting the
problem.<br>
<br>
Regards,<br>
</font>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="https://www.opensips-solutions.com" target="_blank">https://www.opensips-solutions.com</a>
<a href="https://www.siphub.com" target="_blank">https://www.siphub.com</a></pre>
<div>On 04.11.2025 16:10, inderjeet sharma
wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div dir="auto">
<div>version:<br>
opensips 3.1.11<br>
(x86 64/linux)<br>
٧-<br>
flags: STATS: On,<br>
DISABLE_NAGLE, USE MCAST,<br>
PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC,
FAST_LOCK ADAPTIVE_WAIT<br>
ADAPTIVE WAIT LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144,
MAX_LISTEN 16, MAX_URI_SIZE 1024,<br>
BUF_SIZE 65535<br>
poll method support: poll, epoll, sigio_rt, select. git
revision: c51486e3a<br>
main.c compiled on 09:20:17 Nov 20 2024 with gcc 11</div>
<br>
</div>
<div dir="auto">
<div dir="auto">OpenSSL 3.0.2 </div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div>PRETTY_NAME="Ubuntu 22.04.5 LTS"<br>
NAME="Ubuntu"<br>
VERSION_ID="22.04"<br>
VERSION="22.04.5 LTS (Jammy Jellyfish)™<br>
VERSION CODENAME=] ammy</div>
<br>
</div>
<br>
</div>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 4 Nov 2025 at
1:50 pm, inderjeet sharma <<a href="mailto:inder.itpro@gmail.com" target="_blank">inder.itpro@gmail.com</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>
<div dir="auto">Hi all,</div>
<div dir="auto"><br>
I've been running OpenSIPS (v3.x) in a Docker container
for the past 1-2 years as a WebSocket (WSS) registrar
handling SIP registrations.<br>
It has been stable until recently — for the past few
weeks, I'm seeing severe performance stalls.</div>
<div dir="auto"><br>
• OpenSIPS suddenly stops responding to SIP REGISTER
requests.<br>
• ss -unap shows high Recv-Q values on the listening
ports (UDP + WSS).<br>
• The log is flooded with warnings like:<br>
<div dir="auto">08:55:31 opensips-3-1
/usr/local/sbin/opensips[79638]:<br>
WARNING: core: utimer_ticker: utimer task
<tm-utimer> already<br>
117150 ms ago (now<br>
336619940 ms), delaying execution<br>
Nov 3 08:55:31
opensips-3-1/usr/local/sbin/opensips[79638]: WARNING:
core: utimer_ticker: timer task ‹tm-utimer> already<br>
scheduled 117280 ms ago (now<br>
336620070 ms), delaying execution<br>
Nov<br>
308:55:32 opensips-3-1/us/local/sbin/opensips[79638]:
WARNING: core: utimer_ticker: utimer task
<tm-utimer> already<br>
scheduled 117350 ms ago (now<br>
336620140 ms), delaying execution<br>
NOT<br>
3 08:55:32
opensips-3-1/usr/local/sbin/opensips[79638]: WARNING:
core: timer_ ticker: timer task <1b-pinger>
already scheduled ms ago (now 336620140 ms), delaying
execution<br>
08:55:32 opensips-3-1/us/local/sbin/opensips[79638]:
WARNING: core: timer_ticker: timer task ‹nh-timer>
already scheduled ms ago (now 336620140 ms), delaying
execution<br>
308:55:32 opensips-3-1/us/local/sbin/opensips[79638]:
WARNING: core:timer_ticker: timer task
<pg-chk-timer> already<br>
scheduled 54750 ms ago (now 336620140 ms), delaying
execution<br>
NOV<br>
308:55:32 opensips-3-1/usr/local/sbin/opensips[79638]:
WARNING: core: timer_ticker: timer task ‹ul-timer>
already scheduled<br>
79650 ms ago (now 336620140 ms), delaying execution<br>
Nov<br>
308:55:32 opensips-3-1/us/local/sbin/opensips [79638]:
WARNING: core: timer_ticker: timer task
<d1g-reinvite-pinger> already<br>
scheduled 54750 ms ago (now 336620140 ms), delaying
execution<br>
Nov 308:55:32
opensips-3-1/us/local/sbin/opensips[79638]: WARNING:
core:timer_ticker: timer task ‹dig-options-pinger>
already<br>
308:55:32 opensips-3-1/us/local/sbin/opensips[79638]:
WARNING: core: timer_ticker: timer task ‹dlg-timer>
already scheduled<br>
115460 ms ago (now 336620140 ms), delaying execution<br>
Nov 308:55:32
opensips-3-1/usr/local/sbin/opensips[79638]: WARNING:
core: timer_ticker: timer task <EBR timeout>
already scheduled 54750 ms ago (now 336620140 ms),
skipping execution<br>
308:55:32 opensips-3-1/usr/local/sbin/opensips[79638]:
WARNING: core: timer_ticker: timer task ‹tm-timer>
already </div>
<br>
• Killing the process or restarting the container
sometimes does not help immediately.<br>
• CPU and memory usage inside Docker appear normal.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks</div>
</div>
<div>
<div dir="auto">Inderjeet</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div></div>