Hi Fajar,
On Tue, Feb 16, 2010 at 1:16 PM, Fajar A. Nugraha fa...@fajar.net wrote:
On Tue, Feb 16, 2010 at 6:09 AM, Phil Pierotti phil.piero...@gmail.com
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
Since you've deleted 99% of the debug log, I can't tell. Since you
don't know what to look for in the logs, you can't tell, either.
Yes, I have no idea what to look for. If I did, I'd have been looking for
it, rather than asking the list.
Not withstanding your replies, I *still* am no
On Tue, Feb 16, 2010 at 3:37 PM, Phil Pierotti phil.piero...@gmail.com wrote:
about actual accounting request, do they get a timely response? It is
It could easily be that the downstream server is lagging in responsiveness ,
given that it's a db backend.
Best-case is snappy, worst-case is
Phil Pierotti wrote:
Yes, I have no idea what to look for. If I did, I'd have been looking
for it, rather than asking the list.
Maybe my messages haven't been clear enough. The people on this list
know what to look for. But if you insist on giving *no* information for
us to work with... we
Hi Alan,
The main reason my initial checking was with tcpdump was to identify what
the packets were doing.
ACCT request IN from LNS - check
ACCT request OUT to downstream RADIUS - no
So the problem is not due to the downstream RADIUS failing to respond at
all. (ie genuinely/obviously dead)
Phil Pierotti wrote:
The main reason my initial checking was with tcpdump was to identify
what the packets were doing.
As opposed to looking at the debug logs from the server?
You can look at the high level packet in / packet out view. Or, you
can look at the detailed log messages from
On Tue, Feb 16, 2010 at 4:00 AM, Phil Pierotti phil.piero...@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,
Hi Alan,
Sorry, I didn't mean to imply I wasn't interested in looking further, my
primary concern was to find out if it was something as simple and obvious as
the downstream proxy not responding.
Thanks for your feedback, I'll look at the debug logs and see what they tell
me, given the fairly
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
So I've run freeradius with -X -xx
Other than logging the details of the packets sent and received, the debug
logs do not have much more than marking as zombie, seems to be dead.
No complaints, no explanation, no details, just jumps straight into looks
like its dead.
This is the point at
Phil Pierotti wrote:
So I've run freeradius with -X -xx
Other than logging the details of the packets sent and received, the
debug logs do not have much more than marking as zombie, seems to be dead.
They have rather a lot more than that.
No complaints, no explanation, no details, just
On Tue, Feb 16, 2010 at 6:09 AM, Phil Pierotti phil.piero...@gmail.com 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
Hi All,
I've got Freeradius (2.1.7, Ubuntu Hardy) setup to answer some requests
itself, and others get proxied away.
All accounting requests get proxied away.
My Cisco LNS is sending periodic accounting requests , every ten minutes.
We have enough concurrent sessions online that there's a
I've upgraded to 2.1.8 , and still the same.
Oddly enough, it says the *ACCT* port is zombie (which it isn't , we're
still seeing responses frequently).
*and* the un-zombie recovery does an AUTH, so there is no case where the
ACCT port will UN zombify.
Phil P
On Mon, Feb 15, 2010 at 1:42 PM,
Phil Pierotti wrote:
TCPDUMP shows the accounting requests are still being received on the
freeradius box, but the outbound/proxied messages have just stopped.
Any suggestions as to what might be wrong/where to look?
The logs from the server?
I don't understand why you're looking at
15 matches
Mail list logo
