Hi Fajar, Yes and no, it's a third-party product integrated into our billing system, so it's 100% "mystery magic". Debugging is strictly "ask someone to fix it because its broken". Re: your comments about database lookups, this is exactly the situation. Thanks, Phil P On Tue, Feb 16, 2010 at 8:56 AM, Fajar A. Nugraha <fajar@fajar.net> wrote:
On Tue, Feb 16, 2010 at 4:00 AM, Phil Pierotti <phil.pierotti@gmail.com> wrote:
Tue Feb 16 07:45:32 2010 : Proxy: Marking home server {{radius-ip}} port 1813 as zombie (it looks like it is dead).
I assume that radius is out of your control?
Also, status check (via request) succeeds, naturally, given that its not the auth proxy that freeradius is complaining about. (single downstream RADIUS configured as auth+acct)
Running in debugging mode, or at least looking at FR logs, might show you what's happening. I suspect the home server is taking a long time processing acct packets. This is somewhat common if (for example) the home server uses database for acct, with lots of rows and index, an slow disks, in such a way that writes/updates takes a long time. This is just a guess though, more info should be available from the log.
-- Fajar
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html