Hi Slava,

Based on the OpenSIPS logs, did you get that error on the first forking attempt or sometime later after some number of new tcp processes forking ? More or less, my question is : what was the process creation/termination history before getting that bug log ?

Also I just pushed a small commit to improve the date provided by the bug log.

In regards to the "not clear how to calculate"...could you be specific ?

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 03/10/2019 05:12 PM, Slava Bendersky wrote:
Hello Everyone,
Trying test auto scaling feature with following config

auto_scaling_profile = PRF_SIP
     scale up to 24 on 70% for 4 cycles within 5
     scale down to 4 on 20% for 8 cycles

On box 4096 Mb memory and 4 virtual CPU

Getting in log

CRITICAL:core:fork_dynamic_tcp_process: #012>>> trying to fork one more TCP worker but no free slots in the TCP table#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues


*Not clear how to calculate workers for tcp or udp*

*tcp_workers=10* use_auto_scaling_profile PRF_SIP
*listen=udp:lan_ip:5060* use_auto_scaling_profile PRF_SIP


[root@vprx00 ~]# opensips -V
version: opensips 3.0.0-dev (x86_64/linux)
flags: STATS: On, SHM_EXTRA_STATS, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
main.c compiled on 10:06:47 Mar  7 2019 with gcc 8


volga629


_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to