cassandra backends for freeradius v3.1.x
Hello, I'm trying to use cassandra backends for Freeradius. I opted for the V3.1.x as it already contains the cassandra module. After building the Freeradius-server in my machine I added the sql.conf which you can find here <https://gist.github.com/linnaea/ef2457ae6fc6db7c2e04#file-sql-conf> to the directory /usr/local/etc/raddb/mods-enabled/ under the name sql. Then I added some setting to my sites-enabled/default file by listing cassauth in the authorize section,cassauth/cassacctsupplement/ cassacct in the accounting section,cassauth in the session section, and cassauth in the post-auth section. Now when I do radiusd -X I get the following error which you can find attached. Please if you have any idea how to fix this, I will be very grateful to you. I'm ready to take any suggestions and try them I'm running my proper test environment.
On Jun 15, 2015, at 8:53 AM, ICHIBA Sara <ichi.sara@gmail.com> wrote:
I'm trying to use cassandra backends for Freeradius. I opted for the V3.1.x as it already contains the cassandra module. After building the Freeradius-server in my machine I added the sql.conf which you can find here <https://gist.github.com/linnaea/ef2457ae6fc6db7c2e04#file-sql-conf>
Just call the file "sql". And call the module "sql", too: sql { ... } Instead of sql cassauth { ... } Alan DeKok.
On Jun 15, 2015, at 9:00 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Jun 15, 2015, at 8:53 AM, ICHIBA Sara <ichi.sara@gmail.com> wrote:
I'm trying to use cassandra backends for Freeradius. I opted for the V3.1.x as it already contains the cassandra module. After building the Freeradius-server in my machine I added the sql.conf which you can find here <https://gist.github.com/linnaea/ef2457ae6fc6db7c2e04#file-sql-conf>
Nope.
Just call the file "sql".
And call the module "sql", too:
sql { ... }
Instead of
sql cassauth { ... }
Yeah, the problem is there's no query.conf or schema.sql in there yet, because I wasn't convinced the ones included in the gist were correct. The gist author used non-standard table column for everything as well, which makes this harder... and seems to be doing some crazy time based expiry, which is pretty cool, but not how the rest of the dialects operate. Because of Cassandra's architecture, it's impossible to get the affected row count, so you can't do the alt query failover thing you can with the other dialects. The queries should likely all be UPDATEs with a condition comparing Last-Updated to Event-Timestamp. I'll look at it more today. -Arran
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
ICHIBA Sara