SQL_LOG Interim Update missing "partial" config error? huh?
Greetings Everyone, I am using FreeRadius + mySQL + SQLIPPOOL. FreeRADIUS Version 2.1.11. The start and stop accounting records work fine. My issue is I keep getting the following in the logs: Tue Mar 13 22:18:33 2012 : Info: [sql_log] Couldn't find an entry Interim-Update in the config section. Any idea why the interim-updates not working? I have looked through the configuration, I cant find what config section it refers too? I mean the stuff should all be configured as per default for interim update sql query etc is still in raddb/sql/mysql/dialup.conf what special configuration do I have todo? Or where can I go read about it? Please advice! Many thanks! -- Christiaan Rademan - JNCIE #661 Mobile: +27 83 419 2078 E-mail: christiaan.rademan@gmail.com
Hi Chrstiaan, It's because there is no SQL statement configured for Interim-Update by default, you need to create a query to be associated with it in modules/sql_log. A poor example: Interim-Update = "UPDATE ${acct_table} \ SET FramedIPAddress = '%{Framed-IP-Address}', \ AcctSessionTime = '%{Acct-Session-Time}', \ AcctInputOctets = '%{Acct-Input-Octets}', \ AcctOutputOctets = '%{Acct-Output-Octets}' \ WHERE AcctSessionId = '%{Acct-Session-Id}' \ AND UserName = '%{User-Name}';" While you've got this question posted, does anyone mind sharing their sql_log config? The default only talks about inserting a new row for start, stop and alive and nothing about doing updates on stop and interim-update. Is it still acceptable to use updates on stop/interim-update? On 14/03/2012, at 4:34 AM, Christiaan Rademan wrote:
Greetings Everyone,
I am using FreeRadius + mySQL + SQLIPPOOL. FreeRADIUS Version 2.1.11.
The start and stop accounting records work fine.
My issue is I keep getting the following in the logs: Tue Mar 13 22:18:33 2012 : Info: [sql_log] Couldn't find an entry Interim-Update in the config section.
Any idea why the interim-updates not working? I have looked through the configuration, I cant find what config section it refers too?
I mean the stuff should all be configured as per default for interim update sql query etc is still in raddb/sql/mysql/dialup.conf
what special configuration do I have todo? Or where can I go read about it?
Please advice! Many thanks!
-- Christiaan Rademan - JNCIE #661
Mobile: +27 83 419 2078 E-mail: christiaan.rademan@gmail.com
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Any possible updates on this? It seems at some point the man pages changed from using INSERTs and UPDATEs to only using INSERTS. On 14/03/2012, at 3:52 PM, Aidan Rowe wrote:
Hi Chrstiaan,
It's because there is no SQL statement configured for Interim-Update by default, you need to create a query to be associated with it in modules/sql_log.
A poor example:
Interim-Update = "UPDATE ${acct_table} \ SET FramedIPAddress = '%{Framed-IP-Address}', \ AcctSessionTime = '%{Acct-Session-Time}', \ AcctInputOctets = '%{Acct-Input-Octets}', \ AcctOutputOctets = '%{Acct-Output-Octets}' \ WHERE AcctSessionId = '%{Acct-Session-Id}' \ AND UserName = '%{User-Name}';"
While you've got this question posted, does anyone mind sharing their sql_log config? The default only talks about inserting a new row for start, stop and alive and nothing about doing updates on stop and interim-update. Is it still acceptable to use updates on stop/interim-update?
On 14/03/2012, at 4:34 AM, Christiaan Rademan wrote:
Greetings Everyone,
I am using FreeRadius + mySQL + SQLIPPOOL. FreeRADIUS Version 2.1.11.
The start and stop accounting records work fine.
My issue is I keep getting the following in the logs: Tue Mar 13 22:18:33 2012 : Info: [sql_log] Couldn't find an entry Interim-Update in the config section.
Any idea why the interim-updates not working? I have looked through the configuration, I cant find what config section it refers too?
I mean the stuff should all be configured as per default for interim update sql query etc is still in raddb/sql/mysql/dialup.conf
what special configuration do I have todo? Or where can I go read about it?
Please advice! Many thanks!
-- Christiaan Rademan - JNCIE #661
Mobile: +27 83 419 2078 E-mail: christiaan.rademan@gmail.com
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 03/15/2012 09:11 PM, Aidan Rowe wrote:
Any possible updates on this? It seems at some point the man pages changed from using INSERTs and UPDATEs to only using INSERTS.
I'm guessing here, but I suspect the problem with doing UPDATEs is that they noop if the row isn't present. This can happen if an Accounting-Start packet gets dropped and fails its retransmit for example. This is not a problem if you just do INSERTs. The "sql" module (driven either synchronously, or asynchronously via buffered detail files / SQL) handles this differently for this exact reason - it does an UPDATE and if no rows are changed, does an INSERT instead. FWIW we use sql_log and just INSERT to a log table, and a trigger on the table then does the "UPDATE or INSERT" magic. We never moved to using buffered SQL because we need to stream the auth logs as well as the accounting logs (long story) and I couldn't see a way to do that.
participants (3)
-
Aidan Rowe -
Christiaan Rademan -
Phil Mayers