Well, I can't really say what limits selinux puts in place or other CentOS
specific apps, but I encountered various strange situations where no centos
sysadmin I interacted with could give a solution, even with selinux
disabled, so could be something else...
Coming in my mind: limit on number of new TCP connections per second or
number of forked processes per second - they are the reason for these
"delay" core parameters for mod/child init.
Using Debian stable was always smooth an without such strange limits...
Cheers,
Daniel
On Tue, 28 Aug 2018, 13:45 Alex Balashov, <abalashov(a)evaristesys.com> wrote:
On Tue, Aug 28, 2018 at 01:31:04PM +0200,
Daniel-Constantin Mierla wrote:
if you have performance issues just with a very
simple config sending
a stateless sip reply, then check your system/firewall
configuration/limits. Specially on centos, I have seen a lot of
restrictive traffic rates limits set by selinux. Also, if you run in a
virtual machine, there can be limits enforced by the vm platform.
Really? When did SELinux get into the PPS enforcement business?
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web:
http://www.evaristesys.com/,
http://www.csrpswitch.com/
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users