How I can enable debug logs for home server status check
Hello, I am not sure if this is a potential issue or not so let me first ask how the home server if it is marked as dead can become alive? I have a configuration like this home_server <>__1812 { type = auth ipaddr = ip port = 1812 secret = <> response_window = 20 zombie_period = 40 # revive_interval = 120 status_check = request username = ping password = test check_interval = 30 check_timeout = 4 num_answers_to_alive = 3 max_outstanding = 65536 } I've tried to uncomment or comment revive_interval but in both cases, I don't see in debug log (-fxxl) any messages about the home server status check. Also in my pool of home servers I have only 1 server, I know this is a weird config, but this is all that I have. In debug logs, I see a message like this (3600) ERROR: Failed to find live home server: Cancelling proxy (3600) Clearing existing &reply: attributes (3600) Found Post-Proxy-Type Fail-Authentication How I can enable debug messages about home server status checks? (I've tried to use more x i.e. -fxxxxx..., not helping) And manual request with radclient and credentials ping/test returns Access-Reject. So I expect that server should be marked as alive. Best regards, Vladimir
On 7 Nov 2022, at 22:39, work vlpl <thework.vlpl@gmail.com> wrote:
Hello, I am not sure if this is a potential issue or not so let me first ask how the home server if it is marked as dead can become alive?
I have a configuration like this
home_server <>__1812 { type = auth ipaddr = ip port = 1812 secret = <> response_window = 20 zombie_period = 40 # revive_interval = 120 status_check = request username = ping password = test check_interval = 30 check_timeout = 4 num_answers_to_alive = 3 max_outstanding = 65536 }
I've tried to uncomment or comment revive_interval but in both cases, I don't see in debug log (-fxxl) any messages about the home server status check.
So, the documentation https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/proxy.conf... <https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/proxy.conf#L365> says: # The "revive_interval" is used ONLY if the “status_check” # entry below is "none". Otherwise, it will not be used, # and should be deleted. Have you tried that? If no, please try as the docs says.
Also in my pool of home servers I have only 1 server, I know this is a weird config, but this is all that I have.
It's fine.
In debug logs, I see a message like this
(3600) ERROR: Failed to find live home server: Cancelling proxy (3600) Clearing existing &reply: attributes (3600) Found Post-Proxy-Type Fail-Authentication
How I can enable debug messages about home server status checks? (I've tried to use more x i.e. -fxxxxx..., not helping)
And manual request with radclient and credentials ping/test returns Access-Reject. So I expect that server should be marked as alive.
Which version are you using? Independent of the answer, we encourage you to use the latest 3.2.x as can be seen at https://networkradius.com/packages/
Best regards, Vladimir - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Jorge Pereira jpereira@networkradius.com
Hi On Tue, 8 Nov 2022 at 14:17, Jorge Pereira <jpereira@freeradius.org> wrote:
So, the documentation https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/proxy.conf... <https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/raddb/proxy.conf#L365> says:
# The "revive_interval" is used ONLY if the “status_check” # entry below is "none". Otherwise, it will not be used, # and should be deleted.
Have you tried that? If no, please try as the docs says.
Yes, I saw it and I expected if I will comment out revive_interval this will be equal to "should be deleted." And the recommendation is to use a status check.
Which version are you using? Independent of the answer, we encourage you to use the latest 3.2.x as can be seen at https://networkradius.com/packages/
FreeRADIUS Version 3.0.27 (git #9fe91c185), And sorry for annoying but I still have the same question. How I can enable debug messages about home server status checks? I am trying to debug how freeradius tests if the home server is alive or dead, and why it keeps home server marked as dead if I manually can ping the server and see the response from it. Best regards, Vladimir
On Nov 8, 2022, at 1:39 AM, work vlpl <thework.vlpl@gmail.com> wrote:
I am not sure if this is a potential issue or not so let me first ask how the home server if it is marked as dead can become alive?
The comments in the configuration files document how it works.
I've tried to uncomment or comment revive_interval but in both cases, I don't see in debug log (-fxxl) any messages about the home server status check.
Then it's not sending Status-Server packets. If it sends packets, they show up in debugging mode.
And manual request with radclient and credentials ping/test returns Access-Reject. So I expect that server should be marked as alive.
No. FreeRADIUS doesn't know you're using radclient to send packets to the home server. FreeRADIUS only knows about packets it sends. Alan DeKok.
On Tue, 8 Nov 2022 at 18:07, Alan DeKok <aland@deployingradius.com> wrote:
Then it's not sending Status-Server packets.
If it sends packets, they show up in debugging mode.
Hello, I researched a bit more. Please check the version from 9fe91c1856d4545a13d0a58946f53e7366b95249 commit.
From what I see this version does not proxy any requests, with the next home server configuration.
To reproduce start 2 servers home and proxy. Send auth requests, a proxy server with return reject. In logs, I see this. (0) ERROR: Failed to find live home server: Cancelling proxy (0) Clearing existing &reply: attributes (0) Found Post-Proxy-Type Fail-Authentication I've returned back to a version from this commit 8fd11ab7168c4aedda8315275a02a34845005f5d it works for me.
And manual request with radclient and credentials ping/test returns Access-Reject. So I expect that server should be marked as alive.
No.
FreeRADIUS doesn't know you're using radclient to send packets to the home server. FreeRADIUS only knows about packets it sends.
Yes, I understand that when I am using radclient it will not affect the internal state of freeradius. I just tried to explain that radclient can access home server, therefore I expected that freeradius also should be able to reach the home server. But what I saw radius server didn't try to do that and in the internal state, the home server was marked as offline. Best regards, Vladimir
On Wed, 9 Nov 2022 at 18:41, work vlpl <thework.vlpl@gmail.com> wrote: Sorry, I forgot to attach home server config home_server testing__proxy { ipaddr = radius-home IPv4 address [172.18.0.7] port = 1812 type = "auth" secret = <<< secret >>> response_window = 20.000000 response_timeouts = 1 max_outstanding = 65536 zombie_period = 40 status_check = "request" ping_interval = 30 check_interval = 30 check_timeout = 4 num_answers_to_alive = 3 revive_interval = 120 username = "ping" password = "test" limit { max_connections = 16 max_requests = 0 lifetime = 0 idle_timeout = 0 } coa { irt = 2 mrt = 16 mrc = 5 mrd = 30 } }
On Nov 9, 2022, at 5:41 PM, work vlpl <thework.vlpl@gmail.com> wrote:
I researched a bit more. Please check the version from 9fe91c1856d4545a13d0a58946f53e7366b95249 commit.
From what I see this version does not proxy any requests, with the next home server configuration.
To reproduce start 2 servers home and proxy. Send auth requests, a proxy server with return reject. In logs, I see this.
Thanks, I pushed some fixes. Alan DeKok.
participants (3)
-
Alan DeKok -
Jorge Pereira -
work vlpl