Alan Ivan,
I can confirm that the change made to the event.c file fixed the problem
with the robust proxy accounting.
Many thanks for you help.
Chris
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Chris Howley wrote:
I can confirm that the change made to the event.c file fixed the problem
with the robust proxy accounting.
That's great news!
Many thanks for you help.
And thanks for spending the time to not only debug it, but provide
useful feedback.
Alan DeKok.
-
List info
Chris Howley wrote:
Here's the output from FR2.1.7.
OK. Please grab an updated copy of the 2.1.7 tar file from
http://git.freeradius.org/pre/
I've put some changes in which should help.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Alan,
This is the debug output using the latest release of 2.1.7 from
http://git.freeradius.org/pre.
Thanks for your help in advance.
Chris
-Original Message-
From: Chris Howley [mailto:ecl...@netserv3.leeds.ac.uk]
Sent: 15 June 2009 12:07
To: Chris Howley
Subject: radius.debug4
Alan,
This is the debug output using the latest release of 2.1.7 from
http://git.freeradius.org/pre.
Hm, for some reason failure doesn'r result in retry in last pass:
...
Found Post-Proxy-Type
server home.example.com {
+- entering group Fail {...}
[detail.example.com] Suppressing
Chris Howley wrote:
This is the debug output using the latest release of 2.1.7 from
http://git.freeradius.org/pre.
Arg. There was an idiotic typo in the code. I can't help but feel at
least partially responsible.
OK... I've put the updated version on the same web site. You don't
have
Ivan,
I doubled the value of cleanup delay in radiusd.conf. This change didn't fix
the problem (see below).
Thanks for your help,
Chris
++[exec] returns noop
Sending Access-Accept of id 88 to 10.12.80.109 port 32769
User-Name = isschug
MS-MPPE-Recv-Key =
Chris Howley wrote:
I doubled the value of cleanup delay in radiusd.conf. This change didn't fix
the problem (see below).
Grab a copy of the server from http://git.freeradius.org/pre/
I've added some debug messages which might help explain what's going on.
Alan DeKok.
-
List
Alan,
Here's the output from FR2.1.7.
Thanks for you help in advance,
Chris
++[exec] returns noop
Sending Access-Accept of id 128 to 10.12.80.109 port 32769
User-Name = isschug
MS-MPPE-Recv-Key =
0x3019b4c8f9f76bb2fc4d69edbc20e98377351a661c0b412c760cd773e3b4c5f5
Ivan,
When both RADIUS servers are operational robust proxying works. When one of the
servers is
unreachable the other server (that's attempting to proxy an accounting request)
will delete
the detail.work file from the listener's sub-directory after failing to get a
response from
the other
When both RADIUS servers are operational robust proxying works. When one
of the servers is
unreachable the other server (that's attempting to proxy an accounting
request) will delete
the detail.work file from the listener's sub-directory after failing to
get a response from
the other
.++[detail.example.com] returns noop } # server
acct_detail.example.com Going to the next request Received proxied response
from internal virtual server.
server home.example.com {
}
1) The following is in the robust-proxy-accounting file.
# (5) Define the virtual server to write the packets
Hi,
I used the example configuration and got the same result.
.
2. I moved the following from the robust-proxy-accounting file to the
proxy.conf file.
why?
the robust-accounting stuff is a self-contained virtual server. by putting
this into proxy.conf you have introduced
Alan,
Thank you for your help. I've removed the configuration from the proxy.conf and
I'm now using
the original robust-proxy-accounting file. However, the problem persists - the
detail.work
file is being erased.
Chris
-Original Message-
From: freeradius-users-bounces+c.p.howley
Thank you for your help. I've removed the configuration from the
proxy.conf and I'm now using
the original robust-proxy-accounting file. However, the problem persists -
the detail.work
file is being erased.
Which detail.work? Accounting one or failover one? Are you implying that
failover
Chris Howley wrote:
I used the example configuration and got the same result.
Well... it worked the last time I tried it, hence the example.
The goal is:
a) have a fallback configuration in the pool that writes packets to
the detail file
b) read from the detail file, and try to proxy
Alan,
I hoping you can help me. We're currently testing FR2.1.6 and robust proxy
accounting.
We have two servers running FR2.1.6. When both servers are operational the
relaying of
accounting packets works. However, when one of the servers is down the other
operational
server fails to retain
Chris Howley wrote:
Sending proxied request internally to virtual server.
server acct_detail.leeds.ac.uk {
+- entering group accounting {...}
[detail.leeds.ac.uk] Suppressing writes to detail file as the request was
just read from a detail file.
++[detail.leeds.ac.uk] returns noop
} #
JDL wrote:
In FreeRADIUS 2.x, the radrelay functions have been built into radiusd.
That's the intention.
However, I seem to be having problems with data loss. Everything works
fine when the remote accounting server is up. However, when it goes
down, here is what I am seeing.
...
4) Here
19 matches
Mail list logo
