error when starting up radius using systemctl start radiusd.service command
null) (null
kckong1 at yahoo.com
Tue Jul 23 00:27:31 UTC 2024
I want to report a bug on FreeRADIUS Version 3.0.13, 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.
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?
sql sql1 {
dialect = "mysql"
driver = "rlm_sql_mysql"
server = “10.0.0.1"
port = 3306
login = "root"
password = "password"
radius_db = “radius"
}
sql sql2 {
dialect = "mysql"
driver = "rlm_sql_mysql"
server = “10.0.0.2"
port = 33061
login = "root"
password = “password"
radius_db = “radius"
}
systemctl restart radiusd.service
-- Unit radiusd.service has begun starting up.
Jul 23 08:25:11 radius1 systemd[1]: radiusd.service: control process exited, code=exited status=1
Jul 23 08:25:11 radius1 systemd[1]: Failed to start FreeRADIUS high performance RADIUS server..
-- Subject: Unit radiusd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit radiusd.service has failed.
radius.log
Tue Jul 23 08:15:00 2024 : Error: /etc/raddb/mods-enabled/sql[53]: Instantiation failed for module “sql2"
# radiusd -v
radiusd: FreeRADIUS Version 3.0.13, for host x86_64-redhat-linux-gnu, built on May 24 2020 at 15:07:49
FreeRADIUS Version 3.0.13
Copyright (C) 1999-2017 The FreeRADIUS server project and contributors
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> On 18 Jul 2024, at 10:11 AM, (null) (null) <kckong1 at yahoo.com> wrote:
>
> When I startup using radiusd -X, it doesn't give me the error and radius server start successfully attached is the debug log details.
>
> But if I startup using the "systemctl start radiusd.service”, it failed to start and radius.log appear the following message
>
> # systemctl start radiusd.service
> Job for radiusd.service failed because the control process exited with error code. See "systemctl status radiusd.service" and "journalctl -xe" for details.
>
> Thu Jul 18 09:59:19 2024 : Info: Debugger not attached
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql (sql1): Driver rlm_sql_mysql (module rlm_sql_mysql) loaded and linked
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql (sql2): Driver rlm_sql_mysql (module rlm_sql_mysql) loaded and linked
> Thu Jul 18 09:59:19 2024 : Warning: rlm_sql (sql1): Ignoring read_groups as group_membership_query is not configured
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql_mysql: libmysql version: 5.6.51
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql (sql1): Attempting to connect to database "radius"
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql (sql1): Opening additional connection (0), 1 of 1 pending slots used
> Thu Jul 18 09:59:19 2024 : Warning: rlm_sql (sql2): Ignoring read_groups as group_membership_query is not configured
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql (sql2): Attempting to connect to database "radius"
> Thu Jul 18 09:59:19 2024 : Info: rlm_sql (sql2): Opening additional connection (0), 1 of 1 pending slots used
> Thu Jul 18 09:59:19 2024 : Error: rlm_sql_mysql: Couldn't connect to MySQL server root at 10.0.0.3:radius
> Thu Jul 18 09:59:19 2024 : Error: rlm_sql_mysql: MySQL error: Can't connect to MySQL server on '10.0.0.3' (13)
> Thu Jul 18 09:59:19 2024 : Error: rlm_sql (sql2): Opening connection failed (0)
> Thu Jul 18 09:59:19 2024 : Error: Failed to load clients from SQL
> Thu Jul 18 09:59:19 2024 : Error: /etc/raddb/mods-enabled/sql[47]: Instantiation failed for module "sql2"
>
>
> <debug20240718.log>
More information about the Freeradius-Users
mailing list