jkephart at safetynetaccess.com
Fri Mar 13 17:03:43 CET 2015
Thanks, Alan. We'll try out the truncate method as a start, and see
about upgrading to a newer version, which will likely mean a new server
build, just to ensure our service doesn't go down while we build it.
What's curious to me, after further review, is that it took that entire
2+ hours before FR appeared even to attempt connecting to its database.
Would the HUP possibly cause that?
On 03/13/2015 11:34 AM, A.L.M.Buxey at lboro.ac.uk wrote:
>> We're running on a CentOS 6.6 system, with FR v2.1.12, which is the
>> package that is distributed by CentOS/RH. Each day, the logrotate
>> routing rotates the radius.log (and compresses it), and then restarts
>> FR. This morning, however, the radius log showed that the process
>> restarted, but that it did absolutely nothing for the next two hours and
>> 13 minutes.
> dont restart the FR process...just use copytruncate as the method in logrotate
> - thus meaning that if you are using eg EAP cache, the cache stays... also, looks
> like you are not restarting the service fully but just HUP'ing - 2.1.12 is very very old
> and so many things have been fixed since that release. if not using 3.0.7 then
> at least look at upgrading to 2.2.6 (which is actually config compatible to your version so
> minor work to change)
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users