Sorry yes, you are right. the schema.sql is only informational. All I really needed was queries.conf. I have shared the Freeradius -X output in my first email (with 3.0.19 queries.conf on 3.0.16 database schema) if it helps to see what the issue could be. Thanks, On Thu, 19 Dec 2019 at 15:03, Alan DeKok <aland@deployingradius.com> wrote:
On Dec 19, 2019, at 9:58 AM, Houman <houmie@gmail.com> wrote:
Thanks for your answer.
I should have been more specific with what I mean by the previous
version.
My previous version was Freeradius 3.0.16 (Ubuntu 18.04). So what I just did was to copy both queries.conf and schema.sql
As I said, the schema file is informational. It's not actually used by FreeRADIUS for anything,
from 3.0.16 and copied them in the same place on a Freeradius 3.0.19 (Ubuntu 19.04). I have restarted Freeradius and I can connect now.
Is this approach ok?
If it works...
But the schema and queries really haven't changed that much from 3.0.16 to 3.0.19. So this copying shouldn't be necessary.
Which makes me wonder what else is going on here.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html