Hello,
We have 3 backend servers which are used in a client-balance mode from
our local proxy server. We are running FR 2.1.10 (from git), but have
seen the following behaviour when we were running 2.1.7 and 2.1.9 for a
short time. Our logs are showing that FR marks the backend servers as
zombie
On Thu, Jun 17, 2010 at 11:26:37AM +0100, John Horne wrote:
So what is being seen is that backend server 141.163.66.101 has sent an
accept accept packet (to the local proxy server 195.250) and the log
shows a user as having authenticated. About 10 seconds later, the server
is marked as zombie,
On Thu, 2010-06-17 at 14:16 +0200, Josip Rodin wrote:
On Thu, Jun 17, 2010 at 11:26:37AM +0100, John Horne wrote:
So what is being seen is that backend server 141.163.66.101 has sent an
accept accept packet (to the local proxy server 195.250) and the log
shows a user as having
On Thu, 2010-06-17 at 14:09 +0100, Alan Buxey wrote:
Hi,
On Thu, Jun 17, 2010 at 11:26:37AM +0100, John Horne wrote:
So what is being seen is that backend server 141.163.66.101 has sent an
accept accept packet (to the local proxy server 195.250) and the log
shows a user as having
John Horne wrote:
So what is being seen is that backend server 141.163.66.101 has sent an
accept accept packet (to the local proxy server 195.250) and the log
shows a user as having authenticated. About 10 seconds later, the server
is marked as zombie, but tcpdump shows that a packet (access
On Thu, 2010-06-17 at 17:54 +0200, Alan DeKok wrote:
John Horne wrote:
Why does it think it looks like it is dead?
Because the home server didn't respond to *another* request.
Each request has a timer. If the home server doesn't respond within
that time, then it is marked zombie.
John Horne wrote:
Hmm. Given that the servers are lightly loaded, I guess we are looking
at packet loss over the network?
Yes. Many packets lost. The NAS re-transmits, FR re-transmits, and
the home server doesn't respond.
The default timeout before marking a home server zombie is 30s.
John Horne john.ho...@plymouth.ac.uk writes:
On Thu, 2010-06-17 at 17:54 +0200, Alan DeKok wrote:
John Horne wrote:
Why does it think it looks like it is dead?
Because the home server didn't respond to *another* request.
Each request has a timer. If the home server doesn't respond
Alan DeKok al...@deployingradius.com writes:
John Horne wrote:
Hmm. Given that the servers are lightly loaded, I guess we are looking
at packet loss over the network?
Yes. Many packets lost. The NAS re-transmits, FR re-transmits, and
the home server doesn't respond.
The default
On Thu, 2010-06-17 at 20:08 +0200, Bjørn Mork wrote:
I would start by looking for any such deliberately ignored request.
I am told that the home server logs show nothing suspicious. I have no
direct access to those servers so I cannot say for myself. However, I
have asked that the logs are
10 matches
Mail list logo
