FreeRadius Fresh installation 3.0.23 "${dialect}" Reference "${dialect}" not found

Pizu pizpower at gmail.com
Thu Sep 23 18:22:38 CEST 2021


Hi,

Yes vm I have no issues. Live setup is on same os version and same
freeradius version.

Physical server I have issue, tomorrow I am going to try a
different physical server as the current one is old and cannot install esxi
on it, it's not supported.

Will keep you all updated.

Thanks & Regards

On Thu, 23 Sep 2021, 16:50 Kristofer Hallin, <kristofer at sunet.se> wrote:

> Hi,
>
> I got curious and started a fresh VM with Ubuntu myself (Ubuntu 20.04.2
> LTS). I installed the packages from NetworkRADIUS and symlinked status, sql
> and ldap just like you did. I then changed dialect in sql from sqlite to
> mysql and restarted FreeRADIUS without seeing the same issue as you do (TLS
> for MySQL, LDAP config etc are out of the scope here).
>
> The sql configuration now has the following two lines for dialect and
> driver:
>
>   dialect = "mysql"
>   driver = "rlm_sql_${dialect}"
>
> And that was the _only_ change I made to the configuration and it works.
>
> BR,
> /K
>
>> Kristofer Hallin
> SUNET
> On 23 Sep 2021, 16:17 +0200, Pizu <pizpower at gmail.com>, wrote:
> > Hi,
> >
> > This is a formated server, fresh Ubuntu installation and fresh freeradius
> > installation, just did the above mentioned configuration. I.e sym linked
> > the LDAP/SQL/Status mods and site and changed the dialect from SQLite to
> > MySQL and driver from null to use the dialect that's all the
> configuration.
> > I cannot understand what I did wrong here :( The same procedure for all
> > servers..
> >
> >
> >
> > On Thu, 23 Sep 2021, 16:06 Alan DeKok, <aland at deployingradius.com>
> wrote:
> >
> > > On Sep 23, 2021, at 9:22 AM, Pizu <pizpower at gmail.com> wrote:
> > > >
> > > > I am going to format it and install ESXi and will create a VM and
> will
> > > give
> > > > you an update.
> > >
> > > I suspect what happened is that you broke the configuration, and then
> > > kept re-installing the packages, hoping that would fix it.
> > >
> > > The problem is that the packages don't wipe your configuration and
> > > install the new ones. That's so you can upgrade the server by
> installing
> > > the new package, and it won't break a production system.
> > >
> > > So as always, if you make a change:
> > >
> > > * test it before the change. Make sure it works
> > >
> > > * make the change
> > >
> > > * test it after the change. If it doesn't work, then the problem is the
> > > change you made. Don't do anything else until you fix the
> configuration.
> > >
> > > Alan DeKok.
> > >
> > >
> > > -
> > > List info/subscribe/unsubscribe? See
> > > http://www.freeradius.org/list/users.html
> > -
> > List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html


More information about the Freeradius-Users mailing list