> >> 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=3D65536, max=3D65536 }
> >> 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=3D65536, max=3D65536 }
> >> 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=3D65536, max=3D65536 }
> >> 4013 relayd RET getrlimit 0
> >> 4013 relayd CALL recvmsg(550,0x7f7ffffbb6a0,0)
> >> 4013 relayd RET recvmsg -1 errno 35 Resource temporarily unavailable
This probably means the process has run out of file descriptors.
fstat might expose what is going on. If that's the case, roll your
sleeves up and study the code. As usual, the circumstances that
create this event are not being completely documented - I MEAN, what
I'm seeing here isn't a bug report including a configuration file
that reliably reproduces it.
