On 15/12/2021 21:29, Alan DeKok wrote:
On Dec 15, 2021, at 4:21 PM, Antônio Modesto<modesto@hubsoft.com.br> wrote:
I am sorry, I am using Freeradius 3.0.21, not 2.0.21. OK, that's good.
But regarding the attributes, they are being read from the database (PostgreSQL). What you said about database issues does not make sense to me. If freeradius can't read something from the database, it should halt the request, not respond a Access-Accept with truncated attributes. It depends on how you configure the server. It's perfectly possible to have it return Access-Accept if the DB is down.
So... how did you configure the server?
As I said before, the weird part is that running freeradius in debug-mode (single-threaded) the problem didn't happen. That doesn't mean anything. If the issue happens randomly, then it would be rare for it to happen when you're running in debug mode for a short time.
I will try to upgrade to the last build and see what happens. It would also help to try to understand what you've configured the server to do.
Where are the attributes coming from? What happens if the DB is down?
Alan DeKok.
The attributes are coming from the database, from the radgroupreply table. My configuration is basically the default one with minor adjustments. I use attr_filter to not send attributes from one vendor to another, but I already checked that and it is not the source of the problem. I think it may be caused by the bug reported by our friend in a previous message. Thanks a lot.
- List info/subscribe/unsubscribe? Seehttp://www.freeradius.org/list/users.html
-- Att, *Antônio Modesto*