It’s Never the Firewall
This last Thursday I had the privilege of giving a talk at our local Linux User Group about diagnosing firewall issues on Linux entitled “It’s Never the Firewall: Diagnosing Linux Firewall Issues”. I really enjoyed giving the talk, however, I left a few questions unanswered. While I may do a more extensive post on everything that I went through in the talk (I have been lax on writing content for this blog), this post is more to answer the outstanding questions and of course to make my slides available.
As far as I remember the only question I wasn’t able to answer was about file descriptors related to TCP connections. It isn’t exactly a firewall issue but exhaustion of file descriptors is one of the issues I’ve seen blamed on the firewall (which in turn was relevant to the talk).
Established TCP connections consume file descriptors on Linux systems. Each user session is restricted by a limit defined by the system administrator (or more likely using the distribution’s defaults). Some services consume a large number of file descriptors for their basic operations before any network connections are involved (Redis and Elasticsearch being two common services that both recommend increasing this limit).
When file descriptors are exhausted there are two common behaviors of applications depending on how they’re written. The first and more common behavior will an immediately terminated connection, which to the user will look quite similar to a iptables REJECT response. The less common behavior is waiting until a file descriptor to become available before accepting the connection, which will result in a hanging incomplete connection much like an iptables DROP target.
An important caveat here is that I’m talking about user perception. If you look at the packets being exchanged, it’s clear that this isn’t the case.
A quick way to diagnose if this is an issue is to compare the current number of open file descriptors by a user to their limit. In my experience most of these commands are available to unprivileged users which is also handy if there is a complicated process for using or executing commands with elevated privileges.
First let’s check what the total number of open file descriptors are on the system:
[user@sample-host] ~ $ lsof | wc -l 185779
If it is under 10,000 there is a very good chance this is not the problem you’re looking for. If you see a large number like the output above, it is worth investigating more. The host that I sampled that from currently has no file descriptor issues.
First you’ll want to identify the main process of the application that is having issues. Make sure you note the user that the application is running as. Identify the current configured limits for that process (replace with the pid you just found):
[user@sample-host] ~ $ grep 'open files' /proc/<PID>/limits Max open files 1024 4096 files
This tells the process is currently operating with a soft limit of 1,024 file descriptors and a hard limit of 4,096. This is where the diagnostics can get a little fuzzy. File descriptors are limited by user session not by process or user which is what we can directly query on. To get a rough idea of where we’re at lets query those two specifics.
[user@sample-host] ~ $ lsof -p <PID> | wc -l 5 [user@sample-host] ~ $ lsof -u <USER> | wc -l 721
This particular example is enough for us to clearly see file descriptors are not an issue. The current number of file descriptors open for the user (721) is below the process’s soft limit of 1,024. If the number of file descriptors is closer to our limits you’ll have to get an exact count of what is going on. Unfortunately I don’t know an easy one liner to check this.
To get an exact count you need to enumerate all processes with the same session identifier (SID) as your target process, query them all for the current file descriptor consumption, and add them up into a total. As a rule of thumb I recommend leaving about a 25% overhead for your service during peak load which can be set in your system limits file for that service’s user.