Hi Egor, On Tue, Feb 24, 2026 at 06:43:33PM +0000, Egor Shestakov wrote: > In the ENFILE and ENOMEM cases, when accept() fails, an irrelevant > global.maxsock value was printed that doesn't reflect system limits.
That's a good point, however it will not help the users locate the right tunable either. I think it can be useful to print actconn, which is the number of active front connections and can definitely give a hint about a limit that might have been encountered (e.g. if you see 125000, it instantly rules out any lower threshold). You can log it as "actconn=" since it's already mentioned in the doc about log formats. thanks, Willy
