RE: replication with radrelay: Failed to aquire filelock

[Kostas Kalevras]

On Tue, 14 Dec 2004, Michael Markstaller wrote:
My setup: Running FreeRADIUS 1.0.1 on Debian sarge
server2 (secondary) -> detail-relay/radrelay -> server1 (primary) ->
mysql
The servers are far away from being under (dual Xeon 2,8, 1GB, SCSI 15k
etc)
As long as the primary runs and is reachable, everything is fine but
whenever the secondary server comes into action due to the primary being
unreachable,
I see this "Error: rlm_detail: Failed to aquire filelock
for...<detail-relay>" frequently. (~1000 acct per hour with ~25 "Error:
rlm_detail: " messages per hour)
Is there really nothing that can be done about this because I'm
concerned to loose some accounting as whenever this happens the primary
is most likely down ?
Does this happen when the primary server comes back up or while it is down? For 
instance does the detail file get larger when these messages are printed?

radrelay should not create any problem especially in this case (where the 
target radius server is down), since it will fill up it's accounting slots and 
not read the detail file untill the corresponding packets have been 
acknowledged by the primary radius server.

Maybe it'd help i.e. to make radrelay doing less frequent checks on the
detail-file but I found no option for this..
Accounting is the most important thing, when I see freeradius reporting
problems with it, I always feel very uncomfortable ;)
Michael
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Serkin
Sent: Friday, October 01, 2004 7:27 AM
To: [EMAIL PROTECTED]
Subject: Re: replication with radrelay: Failed to aquire filelock

Kostas Kalevras wrote:
On Thu, 30 Sep 2004, Alexander Serkin wrote:

Hello again.
While replicating accounting info to secondary server with
radrelay i see the
following message in radius.log:
Thu Sep 30 10:48:51 2004 : Error: rlm_detail: Failed to
aquire filelock for
/opt/fr/radacct/detail, giving up
Does it mean that i'm losing some accounting records when
radrelay and radiusd
processes are bumped with each other on detail file lock?

Only if you see these messages all the time. If the detail
module fails to
The message appears approximately once a minute (~1000
simultaneous logins).
The amount of simultaneous logins grows with about 100 per month.
So in 10 months we'll come to 2000 of them. And the message
will be more frequent.
And i've no idea when i shoud degin to worry about that :-).
acquire the file lock it will return failure and the whole
accounting process
will fail. As a result the Access-Server *should* resend
the corresponding
accounting request which will probably get stored
sucessfully the second time.

--
Sincerely Yours,
Alexander
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
Kostas Kalevras         Network Operations Center
[EMAIL PROTECTED]       National Technical University of Athens, Greece
Work Phone:             +30 210 7721861
'Go back to the shadow' Gandalf
- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html