Marinko Tarlac wrote:
> A little update... In the same time (2009-02-17 11:23:16), there was at
> least 20 other closed sessions and they are from different NASes so I
> guess that problem is on the server side...
You can turn on SQL tracing to see the SQL statements. Or, (it's
easier in 2.1.4)
A little update... In the same time (2009-02-17 11:23:16), there was at
least 20 other closed sessions and they are from different NASes so I
guess that problem is on the server side...
In which cases accounting_onoff_query is triggered by radius server?
(Accounting Off, and Stop but is there
I have at
Tue Feb 17 11:22:44 2009 and
Tue Feb 17 11:24:14 2009 which is OK because the updates are set to every 90
seconds.
According to database the session was closed at 2009-02-17 11:23:16
After Tue Feb 17 11:24:14 2009, radius still receives regular updates.
acctterminatecause is empty and w
>For start record I have
>
>Tue Feb 17 00:21:11 2009
>Service-Type = Framed-User
>Framed-Protocol = PPP
>NAS-Port = 416808
>NAS-Port-Type = Ethernet
>User-Name = "branka"
>Calling-Station-Id = "00:4F:62:09:3C:C9"
>NAS-Port-Id = "konc-javne"
>Acct-Session-Id = "8135a5
For start record I have
Tue Feb 17 00:21:11 2009
Service-Type = Framed-User
Framed-Protocol = PPP
NAS-Port = 416808
NAS-Port-Type = Ethernet
User-Name = "branka"
Calling-Station-Id = "00:4F:62:09:3C:C9"
NAS-Port-Id = "konc-javne"
Acct-Session-Id = "8135a552"
Fra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marinko Tarlac wrote:
> Hi friends.
>
> I have small problem with freeradius and accounting (with
> database). Something is closing opened sessions and I can't see
> what is the reason. It seems that accounting_onoff_query was
> triggered by "something
Hi friends.
I have small problem with freeradius and accounting (with database).
Something is closing opened sessions and I can't see what is the reason.
It seems that accounting_onoff_query was triggered by "something" and
acctterminatecause field is empty so I don't see anything.
accountin
7 matches
Mail list logo
