Hi, it does the first - calling kill -HUP on postrotate: /var/log/freeradius/*.log { weekly rotate 52 compress notifempty postrotate kill -HUP `cat /var/run/freeradius/freeradius.pid` endscript } I checked the init script as well, it does not offer a reload option, just restart and force-reload, doing both the same: calling the stop option and then the start option again... Jan Am 12.04.2012 16:16, schrieb John Dennis:
On 04/12/2012 09:59 AM, Jan Weiher wrote:
Hi,
I've got a strange problem with FR 2.1.12, sometimes (not always) when logrotate ran, freeradius goes bonkers and responds to every pap request with "mschap xlat failed". Restarting FR fixes this magically and all works fine again. I created a small and hackish script, which restarts FR when this happens. The output showed that about every second week (logrotate runs weekly) this happens. Because FR works fine again after a restart, restarting FR in debug mode is not an option to get more information. But here is a snipped from my radiusd.log showing the symptom:
Is there any more information I can provide?
Yes, what is the contents of your logrotate script. There are two typical strategies, either it directly does a "kill -HUP" to the freeradius pid, or it invokes the initscript passing it the "reload" option. If it's the later we would need to know what the reload option does, e.g. does it also just do a "kill -HUP" or does it do something else?