Hi Rich,
On Apr 28, 12:37pm, Richard Hawley wrote:
> Subject: (RADIATOR) Session database not being updated
> I have had several instances since putting Radiator into production
> where the session database does not get updated. When I check the
> accounting files, I notice that the accounting database never received a
> stop request for that session. My question is, what would cause the
> stop request to either not be sent, or not be received by Radiator? The
> NAS is a USR Hiper Modem Chassis. Could it be a problem with the
> dictionary file? I am using the dictionary.usr which came with
> Radiator. Thanks.
The usual cause of this sort of thing is to do with the NAS:
1. Some NASs have software problems that sometimes prevent the Stop being sent.
2. With some NAS types, if the NAS restarts, the sessions that were up at the
time wont get a Stop. (If the NAS sends a accounting on packet Radiator will
use that to clerar all the sessions that were on that NAS, but not all NASs
send accounting start)
3. sometimes it can be casued by (longish) network outages, where the Stop
fails to get through the network in spite if the NASs normal retransmissions.
Eventually the NAS will give up trying to send it.
I would probably consider item 1 as the most likely.
Hope that helps.
Cheers.
--
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.
