I've got a client's server running FreeRADIUS 2.1.10 from source. Linux kernel 2.6.35.7, heavily customized Slackware 13.0 So far, not using chroot, running as root. It's a EAP-TLS setup with OpenSSL verifying via 'client = ', tmpdir = /tmp/radiusd Everything has been fine for weeks, but this morning: Jan 3 08:04:32 dns1 radiusd[22737]: Invalid user: [xxxxxx/<no User-Password attribute>] (from client xxxx port 0 cli xx-xx-xx-xx-xx-xx) Jan 3 08:04:36 dns1 radiusd[22737]: [auth_log] rlm_detail: Couldn't open file /var/log/radius/radacct/x.x.x.x/auth-detail-20110103: Too many open files I checked 'lsof -p' against the running radiusd and the line count of it's output was 1054. Other than the typical linked libraries, socket, etc. at the top, the rest was "(deleted)" lines like this one: radiusd 22737 root 1022u REG 104,2 1334 404429 /tmp/radiusd/radiusd.client.XXGcdadx (deleted) In the meantime, I raised the limit with ulimit and restarted. I'm open to further (late night) testing, patching, whatever... Thanks, Jason -- Jason Englander <jason@englanders.us> 394F 7E02 C105 7268 777A 3F5A 0AC0 C618 0675 80CA
Jason Englander wrote:
It's a EAP-TLS setup with OpenSSL verifying via 'client = ', tmpdir = /tmp/radiusd
OK...
Everything has been fine for weeks, but this morning:
Jan 3 08:04:32 dns1 radiusd[22737]: Invalid user: [xxxxxx/<no User-Password attribute>] (from client xxxx port 0 cli xx-xx-xx-xx-xx-xx) Jan 3 08:04:36 dns1 radiusd[22737]: [auth_log] rlm_detail: Couldn't open file /var/log/radius/radacct/x.x.x.x/auth-detail-20110103: Too many open files
That's bad...
I checked 'lsof -p' against the running radiusd and the line count of it's output was 1054. Other than the typical linked libraries, socket, etc. at the top, the rest was "(deleted)" lines like this one:
radiusd 22737 root 1022u REG 104,2 1334 404429 /tmp/radiusd/radiusd.client.XXGcdadx (deleted)
In the meantime, I raised the limit with ulimit and restarted.
I'm open to further (late night) testing, patching, whatever...
The odd thing is that the code which writes that file does: open file write data close file It's a little hard to understand how those files are left open. Alan DeKok.
Alan DeKok wrote:
The odd thing is that the code which writes that file does:
open file write data close file
It's a little hard to understand how those files are left open.
Never mind... reading the "man" pages would be a good idea. I've pushed a fix to the git repository, branch v2.1.x. Alan DeKok.
On Mon, 3 Jan 2011, Alan DeKok wrote:
Never mind... reading the "man" pages would be a good idea.
I've pushed a fix to the git repository, branch v2.1.x.
Thanks much for the speedy fix. Only one authentication thus far, but that seems to have done the trick. Jason -- Jason Englander <jason@englanders.us> 394F 7E02 C105 7268 777A 3F5A 0AC0 C618 0675 80CA
participants (2)
-
Alan DeKok -
Jason Englander