On Oct 24, 2024, at 10:01 AM, Alan Smith via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am using freeradius 3.0.20 with MariaDB. Radius clients are stored in the database.
You should upgrade to 3.0.27 at least.
When I try to start the service, it will attempt to start the service. Then 1 minute 30 seconds later, it will log error message timed out.In /var/log/radius/radius.log, I can check the clients are still being loaded (not completed yet).The output of systemctl status radiusd is as follows.
There's no reason for the server to take more than 1/10s to start. If it's timing out after 90 seconds, then something external is blocking it. This is usually either things like NFS mounts not being available, or there are hostnames in the configuration file, and DNS isn't working. Each hostname lookup will get a 30 second timeout. Check radiusd.conf, and verify that you have: hostname_lookups = no This setting means that if you do accidentally add a hostname to the configuration, the server will refuse to start. And it won't get multiple 30s DNS timeouts.
May I know how this can be fixed?
The default configuration doesn't have this problem. So the cause is something which was added in the local configuration. Alan DeKok.