Re: relayd: high CPU usage by one or two proc. of many

2017-10-11 Thread Maxim Bourmistrov
Ok, ktrace showed up that processes having problems to grab a socket. e.g. out of fds. Question: How far can I rise kern.maxfiles having following conditions: 16G RAM total prefork 16 relayd procs openfiles-max=65536 in login.conf for relayd class. Out of my calc it is 16*65536 just to accommod

Re: relayd: high CPU usage by one or two proc. of many

2017-09-27 Thread Maxim Bourmistrov
My intention with this mail is to gather more qualitative help to, hopefully, ever solve this or to have more info so it can be provided to someone whom can solve this, if it is a bug. What I know for sure is that those boxes (dual-node setup) are exposed to a large HTTP PUT/POST requests. Large

Re: relayd: high CPU usage by one or two proc. of many

2017-09-27 Thread Theo de Raadt
> >> ktrace gives me following: > >> 4013 relayd CALL getdtablecount() > >> 4013 relayd RET getdtablecount 101/0x65 > >> 4013 relayd CALL getrlimit(RLIMIT_NOFILE,0x7f7bb630) > >> 4013 relayd STRU struct rlimit { cur=3D65536, max=3D65536 } > >> 4013 relayd RET getrlimit 0 >

Re: relayd: high CPU usage by one or two proc. of many

2017-09-27 Thread Maxim Bourmistrov
Hey, had to bring this up again as I’m facing the same problem. Exactly with the same ’error 35’ in trace. This time it is a 6.0-stable. Anything else can be done to track this down? Br Maxim > 24 feb. 2016 kl. 10:53 skrev Stuart Henderson : > > On 2016-02-24, mxb mailto:m...@alumni.chalmers.se

Re: relayd: high CPU usage by one or two proc. of many

2016-02-24 Thread Stuart Henderson
On 2016-02-24, mxb wrote: > Hey, > I have a strange behavior of relayd running on 5.8. > This machine almost exclusively terminates TLS traffic. > Exceptions are forwards which are in backup state (listen on CARP). > > Some times one or two relayd processes out of many consumes a lot of CPU > and

relayd: high CPU usage by one or two proc. of many

2016-02-24 Thread mxb
Hey, I have a strange behavior of relayd running on 5.8. This machine almost exclusively terminates TLS traffic. Exceptions are forwards which are in backup state (listen on CARP). Some times one or two relayd processes out of many consumes a lot of CPU and stays like this until I restart relayd.