On Jun 26, 2015, at 12:29 PM, Adam Hammond <adam.hammond@wicoms.com> wrote:
On 26 Jun 2015, at 16:35, Alan DeKok wrote:
On Jun 26, 2015, at 11:26 AM, Adam Hammond <adam.hammond@wicoms.com> wrote:
I've checked out 3.0.x from git and configured it to my means. I get the following error when I try and start it:
/etc/raddb/mods-config/sql/main/postgresql/queries.conf[150]: Failed parsing expanded string: /etc/raddb/mods-config/sql/main/postgresql/queries.conf[150]: ...M radgroupcheck WHERE GroupName = '%{SQL-Group}' ORDER BY id /etc/raddb/mods-config/sql/main/postgresql/queries.conf[150]: ^ Unknown attribute
You edited the configuration files and broken them. Don't do that.
# Loading module "wicoms_sql" from file /etc/raddb/mods-enabled/sql sql wicoms_sql {
Why did you change the name? What's wrong with just using "sql {" ?
My production server uses several sql instances, mainly so I can use different queries on different virtual servers that authenticate access in different ways.
Use multiple queries.conf files and include them in the different SQL instances?
If you change the name, you have to use the instance name in SQL-Group, as in:
wicoms_sq-SQL-Group
Which means changing the default queries, too.
Ah!
Up till now (well - up till 3.0.4) 'Sql-Group' has always just worked for me in the configuration included in each instance. I'll make sure I set it properly from now on.
Which was wrong and broken, yes. -Arran