After moving MYSQL to a clustered environment, and moving all backup and not
related tasks to slave hosts,
It seems the issue is resolved, radius has been running for several days
without any errors and/or sessions not being stopped.
Thanks for all your help and suggestions,
Amir.
-
List
On 23 Jul 2012, at 14:06, Amir Tal wrote:
Dialup.conf :
[root@RADIUS4 radius]# cat /etc/raddb/sql/mysql/dialup.conf
Looks ok… Could you build with the 2.1x head and post the debug output?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
After additional debugging the fault seems to be with a rouge backup process
running on DB host, causing it to be slow to un-responsive for 10-20 minutes.
(all unclosed sessions are within this time frame)
This is easy to fix, but I'm looking for a way to make a fail-safe solution.
There can
Amir Tal wrote:
After additional debugging the fault seems to be with a rouge backup
process running on DB host, causing it to be slow to un-responsive for
10-20 minutes.
Stop that. The database used by the RADIUS server should ONLY be used
by the RADIUS server.
This is easy to fix, but
On 24 Jul 2012, at 14:24, Alan DeKok wrote:
Amir Tal wrote:
After additional debugging the fault seems to be with a rouge backup
process running on DB host, causing it to be slow to un-responsive for
10-20 minutes.
Stop that. The database used by the RADIUS server should ONLY be used
On 24 Jul 2012, at 18:18, Arran Cudbard-Bell wrote:
On 24 Jul 2012, at 14:24, Alan DeKok wrote:
Amir Tal wrote:
After additional debugging the fault seems to be with a rouge backup
process running on DB host, causing it to be slow to un-responsive for
10-20 minutes.
Stop that. The
Adding unique key to the database results in the following being returned from
rlm_sql,
What happen to accounting data when a duplicate entry is encountered?
In addition, currently there is no scheduled clearing of the data in radacct
table, wont this increase in occurrence?
--
[sql] expand:
Amir Tal wrote:
Adding unique key to the database results in the following being
returned from rlm_sql,
What happen to accounting data when a duplicate entry is encountered?
It SHOULD run the normal query, followed by the alt query.
In addition, currently there is no scheduled clearing
On 22 Jul 2012, at 11:56, Amir Tal wrote:
Adding unique key to the database results in the following being returned
from rlm_sql,
What happen to accounting data when a duplicate entry is encountered?
In addition, currently there is no scheduled clearing of the data in radacct
table, wont
I have increased the value of MAX_QUERY_LEN in
freeradius-server-2.1.12/src/modules/rlm_sql/conf.h
(#define MAX_QUERY_LEN 8192)
There are still duplicated connections/sessions , example sqltrace:
INSERT INTO radacct (acctsessionid,acctuniqueid, username, realm,
This seems to be the case for duplicated connections, there are several
accounting start requests sent within a few seconds from each other, all of
them create a new accounting record, and no stop request is sent for these
sessions.
I don't know about your original issue, but there's a
raised from the default 5 to 25,
this is a rare error, but it still exists, might be related.
Amir.
From: Amir Tal
Sent: Wednesday, July 11, 2012 4:48 PM
To: 'freeradius-users@lists.freeradius.org'
Subject: sql returns fail for some stop requests
Freeradius ver 2.1.12, configured to use ldap
Amir Tal wrote:
i have modified the sql queries and removed unnecessary whitespace,
but am still getting some queries cut-off in the log.
...
is there a way to increase the space/memory available for sql queries?
Edit the source code. See src/modules/rlm_sql/
in addition i have found the
Freeradius ver 2.1.12, configured to use ldap for auth, sql for acct.
Sometimes users' sessions get stuck and have to be closed manualy (simultaneous
use is turned on for all users).
After extensive debugging I have found the following in the logs (radius -X)
[thread] # Executing section
Amir Tal wrote:
It seems the last SQL query line is cut off for some reason, this only
happens on some connections, while others are stopped correctly.
The server has limited space for SQL qeuries. Make them shorter.
Remove multiple spaces, etc.
Alan DeKok.
-
List
15 matches
Mail list logo
