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. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html