Debugging accept4 / socket -- too many open files

I have a quite busy web service here. From time to time I get a “too many open files” on accepting connections.
When I check the process in /proc there are about 8 open file descriptors.

Nothing that can be thought of as too many.

How can a “too many open files” can happen on a socket, when there are not that many files open. I mean I will debug this up the stream now (from accept4 syscalls towards the go routines). I just ask here, because somebody might have had a similar situation?

Hmm, on first sight I would guess, as I cannot provide a proof now, that this is related to massive AWS cloudwatchlogs transfers, that seem to open several connections to the destination from the AWS api.

I will try to find some proof for this…

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.