Good day to all, I´d like to congratulate you for the excellent work in freeradius and the last 2.2.4 update. Finally our freeradius doesnt stop work every x hours, and instead logs an error and resumes working. Now instead of giving every couple of hours the errors: Thu Nov 7 18:32:09 2013 : Error: rlm_sql (sql): Failed to connect DB handle #1 Thu Nov 7 18:32:10 2013 : Error: rlm_sql (sql): There are no DB handles to use! skipped 20, tried to connect 0 It just says: at Jan 18 09:22:26 2014 : Error: [sql] Couldn't insert SQL accounting START record - Deadlock found when trying to get lock; try restarting transaction Sat Jan 18 10:29:24 2014 : Error: [sql] Couldn't update SQL accounting STOP record - Deadlock found when trying to get lock; try restarting transaction Sat Jan 18 10:29:24 2014 : Error: rlm_sql_mysql: MySQL error 'Deadlock found when trying to get lock; try restarting transaction' Thank you
On 20 Jan 2014, at 13:35, Rui Ribeiro <ruyrybeyro@gmail.com> wrote:
Good day to all,
I´d like to congratulate you for the excellent work in freeradius and the last 2.2.4 update. Finally our freeradius doesnt stop work every x hours, and instead logs an error and resumes working.
Now instead of giving every couple of hours the errors: Thu Nov 7 18:32:09 2013 : Error: rlm_sql (sql): Failed to connect DB handle #1 Thu Nov 7 18:32:10 2013 : Error: rlm_sql (sql): There are no DB handles to use! skipped 20, tried to connect 0
It just says: at Jan 18 09:22:26 2014 : Error: [sql] Couldn't insert SQL accounting START record - Deadlock found when trying to get lock; try restarting transaction Sat Jan 18 10:29:24 2014 : Error: [sql] Couldn't update SQL accounting STOP record - Deadlock found when trying to get lock; try restarting transaction Sat Jan 18 10:29:24 2014 : Error: rlm_sql_mysql: MySQL error 'Deadlock found when trying to get lock; try restarting transaction' Thank you
There have been no changes between 2.2.3 and 2.x.x HEAD which would account for this behaviour change. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Rui Ribeiro wrote:
I´d like to congratulate you for the excellent work in freeradius and the last 2.2.4 update. Finally our freeradius doesnt stop work every x hours, and instead logs an error and resumes working.
Now instead of giving every couple of hours the errors:
Thu Nov 7 18:32:09 2013 : Error: rlm_sql (sql): Failed to connect DB handle #1
Those messages indicate issues with the database. They should be fixed, rather than ignored.
It just says:
at Jan 18 09:22:26 2014 : Error: [sql] Couldn't insert SQL accounting START record - Deadlock found when trying to get lock; try restarting transaction
Those messages indicate problems with the database. As Arran said, nothing changed to account for this. I'd suggest ensuring that your database is fast enough to handle the load. Alan DeKok.
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Rui Ribeiro