Acct-Status-Type = Stop have stopped logging to the SQL database.
Suddenly my records with “Acct-Status-Type = Stop” have stopped logging to the SQL database. I am seeing a success entry in the log but a query is not showing any ‘Stop' record. (1858) sql: SQL query returned: success (1858) sql: 1 record(s) updated If I restart the “freeradius” service some new ‘Stop' records briefly start appearing but then it stops. ‘Start’ records are working just fine. My though is that it is updating the ‘Start’ record and not creating a new ‘Stop’ entry when a session is ending as I am seeing ‘acctsessiontime’ values in my ‘Start’ records. Any suggestions would be appreciated. - FreeRADIUS Version 3.0.13 - mysql Ver 15.1 Distrib 5.5.56-MariaDB, for Linux (x86_64) using readline 5.1 - CentOS Linux release 7.5.1804 (Core thanks! -andy
On Jul 30, 2018, at 1:39 PM, andy@andyappel.com wrote:
Suddenly my records with “Acct-Status-Type = Stop” have stopped logging to the SQL database.
I am seeing a success entry in the log but a query is not showing any ‘Stop' record. (1858) sql: SQL query returned: success (1858) sql: 1 record(s) updated
If I restart the “freeradius” service some new ‘Stop' records briefly start appearing but then it stops.
The stop records don't magically disappear. If they're not being updated, it's for a reason. Run the server in debug output to see what's going on.
‘Start’ records are working just fine. My though is that it is updating the ‘Start’ record and not creating a new ‘Stop’ entry when a session is ending as I am seeing ‘acctsessiontime’ values in my ‘Start’ records.
Umm... the server doesn't write "start" or "stop" to the database. It just writes the the users session information. Sessions which are still open don't have "acctstoptime" filled out. Sessions which are closed have a timestamp in the "acctstoptime" field. And all sessions have an "acctsessiiontime" value.
Any suggestions would be appreciated.
- FreeRADIUS Version 3.0.13
Upgrade to 3.0.17...
- mysql Ver 15.1 Distrib 5.5.56-MariaDB, for Linux (x86_64) using readline 5.1 - CentOS Linux release 7.5.1804 (Core
thanks! -andy
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Strange is that DEBUG seems to show everything is working. Here is a snippet of the DEBUG messages: (1858) Acct-Status-Type = Stop . . . (1858) sql: SQL query returned: success (1858) sql: 1 record(s) updated (1858) [sql] = ok (1858) [exec] = noop (1858) attr_filter.accounting_response: EXPAND %{User-Name} (1858) attr_filter.accounting_response: --> 7056278148 (1858) attr_filter.accounting_response: Matched entry DEFAULT at line 12 (1858) [attr_filter.accounting_response] = updated (1858) } # accounting = updated (1858) Sent Accounting-Response Id 203 from 10.x.x.10:1813 to 10.x.0.231:61258 length 0 (1858) Finished request (1858) Cleaning up request packet ID 203 with timestamp +36
From: Alan DeKok Sent: July 30, 2018 at 1:44:30 PM EDT To: FreeRadius users mailing list Subject: Re: Acct-Status-Type = Stop have stopped logging to the SQL database.
On Jul 30, 2018, at 1:39 PM, andy@andyappel.com wrote:
Suddenly my records with “Acct-Status-Type = Stop” have stopped logging to the SQL database.
I am seeing a success entry in the log but a query is not showing any ‘Stop' record. (1858) sql: SQL query returned: success (1858) sql: 1 record(s) updated
If I restart the “freeradius” service some new ‘Stop' records briefly start appearing but then it stops.
The stop records don't magically disappear. If they're not being updated, it's for a reason. Run the server in debug output to see what's going on.
‘Start’ records are working just fine. My though is that it is updating the ‘Start’ record and not creating a new ‘Stop’ entry when a session is ending as I am seeing ‘acctsessiontime’ values in my ‘Start’ records.
Umm... the server doesn't write "start" or "stop" to the database. It just writes the the users session information. Sessions which are still open don't have "acctstoptime" filled out. Sessions which are closed have a timestamp in the "acctstoptime" field.
And all sessions have an "acctsessiiontime" value.
Any suggestions would be appreciated.
- FreeRADIUS Version 3.0.13
Upgrade to 3.0.17...
- mysql Ver 15.1 Distrib 5.5.56-MariaDB, for Linux (x86_64) using readline 5.1 - CentOS Linux release 7.5.1804 (Core
thanks! -andy
- 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 Jul 30, 2018, at 1:51 PM, Andy Appel <andy@andyappel.com> wrote:
Strange is that DEBUG seems to show everything is working.
Then it's fine. But again... *why* do you think that something is wrong? Did my explanation make sense? And also... read the *rest* of the debug output. i.e. the pieces you didn't post here. Is the AcctStopTime field being updated? The debug output exists for a reason. It tells you *exactly* what the server is doing. If you don't read it, you'll never know *which* fields are being updated, or *why* they're being updated. Alan DeKok.
participants (4)
-
Alan DeKok -
Andy Appel -
andy＠andyappel.com
-
Arnab Roy