On Apr 16, 12:32pm, Paul Thornton wrote:
> Subject: (RADIATOR) Lost Stop Records
> Does anyone know why I am sometimes not receiving a STOP record for when a
> user disconnects (for whatever reason). We are using the radius detail
> logs for accounting purposes, but with this being an intermittent problem
> our accounting program doesn't record them logging out. This in turn
> causes another program (Time Watcher) to keep deducting credit. Not good
> for our records and definately not good for the user.
> I have basically had to create a script (very resource hungry) which uses
> smtp to retreive the latest user list from 15 PortMasters and then verify
> this list, with what our database shows. There is always one or two that
> should not be there :(
I guess the most common cause of missing Stop packets in your detail file is if
your NAS crashes or is restarted. You will never get a Stop for the users who
were on the NAS at the time.
Other possibilities are:
1. Flakey network. That doesnt sound likely, as you would probably have other
more serious problems than this.
2. Firmware problem in your NAS, though I havent had any similar reports from
this cause for PMs.
3. Anyone else think of anything?
Hope that helps.
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.