official repository for centos 7
Hi , trying both versions from freeradius.org 3.0.26 and 3.2.1 , in both cases while communicating with oracle db via odbc driver I got same error (11) sql: Executing select query: select * from table(radius.pkg_freeradius_auth.radcheck('itest', '100.64.0.1', '8ef5.5e4c.9e0a')) rlm_sql_unixodbc: 22003 [Oracle][ODBC]Numeric value out of range. (11) sql: ERROR: Error fetching row (11) sql: ERROR: Unknown error At the same time with centos freeradius release 3.0.13 it works fine. Also same query via isql client works fine , without any errors Found old issue on github , but think it should be resolved in these versions. https://github.com/FreeRADIUS/freeradius-server/issues/2822
On Feb 1, 2023, at 2:14 AM, Anatoliy Kushner <cphlpd@gmail.com> wrote:
Hi , trying both versions from freeradius.org 3.0.26 and 3.2.1 , in both cases while communicating with oracle db via odbc driver I got same error (11) sql: Executing select query: select * from table(radius.pkg_freeradius_auth.radcheck('itest', '100.64.0.1', '8ef5.5e4c.9e0a')) rlm_sql_unixodbc: 22003 [Oracle][ODBC]Numeric value out of range. (11) sql: ERROR: Error fetching row (11) sql: ERROR: Unknown error
That's weird.
At the same time with centos freeradius release 3.0.13 it works fine. Also same query via isql client works fine , without any errors
Found old issue on github , but think it should be resolved in these versions. https://github.com/FreeRADIUS/freeradius-server/issues/2822
That change was made because the 3.0.13 version didn't work for many people. The change fixed that. If you say that 3.0.13 works for you and the newer version doesn't work, then we're not sure what to do. For now, you can use another driver to talk to Oracle. Alan DeKok.
Hi Alan , thank you. Can you tell more about RCA of this issue, for better understanding ? \ AK
On 3 Feb 2023, at 22:10, Alan DeKok <aland@deployingradius.com> wrote:
On Feb 1, 2023, at 2:14 AM, Anatoliy Kushner <cphlpd@gmail.com> wrote:
Hi , trying both versions from freeradius.org 3.0.26 and 3.2.1 , in both cases while communicating with oracle db via odbc driver I got same error (11) sql: Executing select query: select * from table(radius.pkg_freeradius_auth.radcheck('itest', '100.64.0.1', '8ef5.5e4c.9e0a')) rlm_sql_unixodbc: 22003 [Oracle][ODBC]Numeric value out of range. (11) sql: ERROR: Error fetching row (11) sql: ERROR: Unknown error
That's weird.
At the same time with centos freeradius release 3.0.13 it works fine. Also same query via isql client works fine , without any errors
Found old issue on github , but think it should be resolved in these versions. https://github.com/FreeRADIUS/freeradius-server/issues/2822
That change was made because the 3.0.13 version didn't work for many people. The change fixed that.
If you say that 3.0.13 works for you and the newer version doesn't work, then we're not sure what to do.
For now, you can use another driver to talk to Oracle.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi all , finally fixed this after changing ID type, from NUMBER to VARCHAR. On Fri, Feb 3, 2023 at 7:10 PM Alan DeKok <aland@deployingradius.com> wrote:
On Feb 1, 2023, at 2:14 AM, Anatoliy Kushner <cphlpd@gmail.com> wrote:
Hi , trying both versions from freeradius.org 3.0.26 and 3.2.1 , in both cases while communicating with oracle db via odbc driver I got same error (11) sql: Executing select query: select * from table(radius.pkg_freeradius_auth.radcheck('itest', '100.64.0.1', '8ef5.5e4c.9e0a')) rlm_sql_unixodbc: 22003 [Oracle][ODBC]Numeric value out of range. (11) sql: ERROR: Error fetching row (11) sql: ERROR: Unknown error
That's weird.
At the same time with centos freeradius release 3.0.13 it works fine. Also same query via isql client works fine , without any errors
Found old issue on github , but think it should be resolved in these versions. https://github.com/FreeRADIUS/freeradius-server/issues/2822
That change was made because the 3.0.13 version didn't work for many people. The change fixed that.
If you say that 3.0.13 works for you and the newer version doesn't work, then we're not sure what to do.
For now, you can use another driver to talk to Oracle.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Feb 9, 2023, at 2:28 AM, Anatoliy <cphlpd@gmail.com> wrote:
Hi all , finally fixed this after changing ID type, from NUMBER to VARCHAR.
That's probably not a good solution. Many of the default queries do "ORDER BY ID". Changing the ID to VARCHAR may change the ordering, and the server will behave differently. Alan DeKok.
Hi Alan, thank you for warning. We do not use default queries. \ AK
On 9 Feb 2023, at 20:43, Alan DeKok <aland@deployingradius.com> wrote:
On Feb 9, 2023, at 2:28 AM, Anatoliy <cphlpd@gmail.com> wrote:
Hi all , finally fixed this after changing ID type, from NUMBER to VARCHAR.
That's probably not a good solution. Many of the default queries do "ORDER BY ID". Changing the ID to VARCHAR may change the ordering, and the server will behave differently.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Alan, in queries.conf file Row ID marked as unused. # 0. Row ID (currently unused) If it is really unused, how sorting can impact on freeradius behaviour ? On Thu, Feb 9, 2023 at 8:43 PM Alan DeKok <aland@deployingradius.com> wrote:
On Feb 9, 2023, at 2:28 AM, Anatoliy <cphlpd@gmail.com> wrote:
Hi all , finally fixed this after changing ID type, from NUMBER to
VARCHAR.
That's probably not a good solution. Many of the default queries do "ORDER BY ID". Changing the ID to VARCHAR may change the ordering, and the server will behave differently.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Feb 10, 2023, at 2:34 AM, Anatoliy <cphlpd@gmail.com> wrote:
Hi Alan, in queries.conf file Row ID marked as unused. # 0. Row ID (currently unused)
If it is really unused, how sorting can impact on freeradius behaviour ?
As I said in my previous message... look at the default queries. They do "order by ID". The comment is wrong. Or, not entirely correct. Alan DeKok.
participants (3)
-
Alan DeKok -
Anatoliy -
Anatoliy Kushner