error when starting up radius using systemctl start radiusd.service command

[null) (null]

Thanks for your feedback and input.

Yes, you’re right, it’s an OS issue related to SELinux (Security-Enhanced Linux) policy settings. Adding or modifying the policy settings in SELinux will resolve the issue.
Thank you very much.

# semanage port -a -t mysqld_port_t -p tcp 33061



> On 23 Jul 2024, at 8:34 AM, Alan DeKok <aland at deployingradius.com> wrote:
> 
> On Jul 22, 2024, at 5:27 PM, (null) (null) <kckong1 at yahoo.com> wrote:
>> I want to report a bug on FreeRADIUS Version 3.0.13,
> 
>  We are not going to issue fixes for a version which is many years out of date.  There's no reason to re-check issues which are already found and fixed years ago.
> 
>> it does not allow any other sql port number other than 3306. Below is the error when I change the port to other number eg. 33061.
> 
>  That's not a FreeRADIUS issue.  Your local OS is limiting the ports.
> 
>> Both mysql database is running, when I change back to default port number 3306, no error. The weird thing is this only happen if I use the systemctl command. No error if I use radiusd -X
>> 
>> Is that a bug fix?
> 
>  Blame your local OS.  FreeRADIUS has no limits on outbound ports for SQL databases.
> 
>  Alan DeKok.
>