Acounting problem with SQL and detail files
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. Thanks for your help. AL PS: sqltrace is not a solution for us.
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.
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
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Aurélien Lafranchise