On Tue, Feb 16, 2010 at 6:09 AM, Phil Pierotti <[email protected]> wrote:
> Tue Feb 16 09:40:25 2010 : Proxy: Marking home server 192.168.147.2 port > 1813 as zombie (it looks like it is dead). There should be other things before that > Sending Accounting-Request of id 228 to 192.168.147.2 port 1813 > User-Name := "----------...@-------------" > Acct-Status-Type := Stop > Acct-Session-Id := "00000000" > Event-Timestamp := "Feb 16 2010 09:40:25 EST" > NAS-Identifier := "Status Check. Are you alive?" > Tue Feb 16 09:40:25 2010 : Debug: Waking up in 0.7 seconds. > rad_recv: Accounting-Response packet from host 192.168.147.2 port 1813, > id=228, length=20 > Tue Feb 16 09:40:25 2010 : Proxy: Received response to status check 34 (1 in > current sequence) Like that one. That particular status check was completed immediately. How were other status check responses, do they arrive on time? How about actual accounting request, do they get a timely response? It is possible that the status check returns early due to non-existent record (Acct-Session-Id := "00000000") needs no db write at all, while actual accounting requests received late response due to db write involved. As Alan said, a complete debug log would be able to show that (and possible other problems as well). You should be able to find out how long it takes for actual accounting packets to get response. If it's within reasonable limits, you may need to increase FR proxy timeouts so it doesn't declare the home server to be dead or zombie. However if it's dreadfully slow, your only choice is to fix your database, possibly tuning it or add faster disks. -- Fajar - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
