possible radutmp problem in 2.1.4 and/or 2.1.5-git(2009-04-17 state)?

Alan DeKok aland at deployingradius.com
Sun Apr 19 18:00:51 CEST 2009


Rozsahegyi Bela wrote:
...         = 0
> open("/usr/local/freeradius/var/log/radius/radutmp", O_RDWR|O_CREAT,
> 0600) = 127
> flock(127, LOCK_EX
> 
> ...and this point freeze the process, rarely only the kill -9 the
> solution for stop.

  That looks like another process is locking the file.

> When delete the radutmp, and start the radius, the authentication is
> very fast, a custom, radclient style monitoring system say about 10-12
> msec for a login.
> If the radutmp file grow, this time going over 30 msec, when the radutmp
> file in the /dev/shm "ramdisk". If the radutmp file on standard
> filesystem, had similar effect, but a little slower respond.

  OK... so what kind of file system are you using when it stops working?
 NFS?

> Could someone help, what should I do? Ran out of ideas...

  Don't put any of the server files on NFS.

> The radutmp file usage better me, than the sql backend, because  the
> radrelay do a little delay.

  If you're using radrelay, the delay doesn't matter.  Use SQL for user
logins, not radutmp.

  Alan DeKok.



More information about the Freeradius-Users mailing list