Hello Alan, Arran, I am in post-crisis analysis so I know why my database had a problem and do not need to debug it. However I do not understand why the Stop records was failing to write in the detail files. Start records was well written in detail files because it is not send to the database. I did not change a lot of configuration, do you have any idea on where to search ? I dot not have an error code for rlm_sql in my logs only the followings: Wed Feb 5 13:53:07 2014 : Error: rlm_sql (sql): There are no DB handles to use! skipped 0, tried to connect 0 Wed Feb 5 13:53:37 2014 : Error: WARNING: Unresponsive child for request 4700544, in component accounting module sql Wed Feb 5 13:53:38 2014 : Info: WARNING: Child is hung for request 4700544 in component accounting module sql. There no logs problem about detail files. I am not using redundant section. In site-enabled/default I have: accounting { detail radutmp sql attr_filter.accounting_response } Thanks. Aurélien Lafranchise Network Operations Manager Mob.: +33 (0)6 03 88 36 26 Fax: +33 (0)4 83 33 45 61 eMail: aurelien.lafranchise@mobiquithings.com Web: http://www.mobiquithings.com Le 11 févr. 2014 à 17:05, freeradius-users-request@lists.freeradius.org a écrit :
De: Alan DeKok <aland@deployingradius.com> Objet: Rép : Acounting problem with SQL and detail files Date: 11 février 2014 16:28:19 UTC+1 À: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Répondre à: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
Aurélien Lafranchise wrote:
We had a database connection problem (Error: rlm_sql (sql): There are no DB handles to use! skipped 0, tried to connect 0). We were surprised that during this problem the accounting information that cannot be passed to the database was not written in the detail files.
Run the server in debugging mode to see why. You can use "raddebug" on a live server.
Also, if there are no DB handles... check the database. It's likely broken / slow / whatever.
The default configuration logs to the "detail" file. If you configure SQL, the default configuration logs to both SQL and "detail". If one fails, it still logs to the other.
So... what changes did you make to the default configuration?
Alan DeKok.
De: Arran Cudbard-Bell <a.cudbardb@freeradius.org> Objet: Rép : Acounting problem with SQL and detail files Date: 11 février 2014 17:05:20 UTC+1 À: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Répondre à: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
On 11 Feb 2014, at 14:47, Aurélien Lafranchise <aurelien.lafranchise@mobiquithings.com> wrote:
Hi All,
We noticed an issue on our FreeRADIUS Version 2.1.12 on a CentOS 6.3 kernel 2.6.32-279.2.1.el6.x86_64.
Our FreeRADIUS is connected to a database for the accounting queries. It is also configured to save the same accounting information in the detail files.
We had a database connection problem (Error: rlm_sql (sql): There are no DB handles to use! skipped 0, tried to connect 0). We were surprised that during this problem the accounting information that cannot be passed to the database was not written in the detail files.
You were using something like
redundant { sql detail }
Right?
What error code was rlm_sql returning when it had no handles left?
You may want to consider using v3.0.x, the connection pool code, and reconnection logic is a significant improvement over the module specific code in v2.x.x.
-Arran
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
