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

[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.

ktrace gives me following:
4013 relayd   CALL  getdtablecount()
  4013 relayd   RET   getdtablecount 101/0x65
  4013 relayd   CALL  getrlimit(RLIMIT_NOFILE,0x7f7ffffbb630)
  4013 relayd   STRU  struct rlimit { cur=65536, max=65536 }
  4013 relayd   RET   getrlimit 0
  4013 relayd   CALL  recvmsg(550,0x7f7ffffbb6a0,0)
  4013 relayd   RET   recvmsg -1 errno 35 Resource temporarily unavailable
  4013 relayd   CALL  getdtablecount()
  4013 relayd   RET   getdtablecount 101/0x65
  4013 relayd   CALL  getrlimit(RLIMIT_NOFILE,0x7f7ffffbb630)
  4013 relayd   STRU  struct rlimit { cur=65536, max=65536 }
  4013 relayd   RET   getrlimit 0
  4013 relayd   CALL  recvmsg(550,0x7f7ffffbb6a0,0)
  4013 relayd   RET   recvmsg -1 errno 35 Resource temporarily unavailable
  4013 relayd   CALL  getdtablecount()
  4013 relayd   RET   getdtablecount 101/0x65
  4013 relayd   CALL  getrlimit(RLIMIT_NOFILE,0x7f7ffffbb630)
  4013 relayd   STRU  struct rlimit { cur=65536, max=65536 }
  4013 relayd   RET   getrlimit 0
  4013 relayd   CALL  recvmsg(550,0x7f7ffffbb6a0,0)
  4013 relayd   RET   recvmsg -1 errno 35 Resource temporarily unavailable

Human readable file after kdump is filled with those lines.
This as far of my understanding is about limit of openfiles.
Thus login.conf was modified and relayd restarted.

Original problem however is yet there and ktrace looks the same.

relayd:\
        :maxproc-max=31:\
        :openfiles-cur=16384:\
        :openfiles-max=65536:\
        :tc=daemon:

 
Question if there is anything else can be done to trace this down?

Br

//mxb