Hello !
On Sat, 23 Sep 2000, Hugh Irvine wrote:
> Could you send us a bit more detail on your hardware and software plaforms and
> the Radiator and database setups (in terms of what software is running on what
> host)? Also, have you tried altering the Timeout and FailureBackoffTime
> parameters in the AuthBy SQL clause? Normally, Radiator will wait 60 seconds
> for a reply to an SQL query, then it will not try to reconnect for a further
> 600 seconds (10 minutes).
We have a server station (Dual PIII-500,RAID5 array,392Mb RAM) running Linux
RedHat 6.2 (kernel version 2.2.16 with patches for i2o subsystem for RAID5
array and for reiserfs, whole base system works on ext2 partition), Oracle8i
(8.1.6) with a single instance and a single database,Radiator 2.16.3.
FailureBackoffTime is set to 30, TimeOut - defaults to 60 seconds. Part of my
AuthBy SQL clause:
<AuthBy SQL>
Identifier AcctStop
FailureBackoffTime 30
DBSource dbi:Oracle:auth3
DBUsername xxxxxxxx
DBAuth xxxxxxxx
AuthSelect
AccountingStopsOnly
AcctSQLStatement insert into radacct ( \
RadAcctId, \
AcctSessionId, \
UserName, \
Realm, \
..............................
</AuthBy>
> > On Sat, 23 Sep 2000, Alexey A. Shavaldin wrote:
> > I've got a problem with SQL Timeout, when using Oracle 8.1.6 and Radiator
> > 2.16.3. The fact is that authorization works OK for first several users, they
> > login and work OK, but then authorization for next users just hangs. Radiator
> > reports SQL Timeout, and the problem is usually solved after that by
> > stopping/starting Radiator again. After that authorization works OK for the
> > next 20-30 users. Is that really the problem with Radiator (as I have to reload
> > it) or with Oracle.
> >
> > Trace 4 log:
> >
> > Fri Sep 22 20:05:32 2000: ERR: do failed for 'insert into RADONLINE ( USERNAME,
> > REALM, NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS,
> > NASPORTTYPE, SERVICETYPE, CalledStationId, CallingStationId ) values ( 'xxxxx',
> > '' , 'yyy.yyy.yyy.yyy' , nvl('48',0), '0000CA86', SYSDATE, '', 'Async',
> > 'Framed-User', '38', '' )'': SQL Timeout
> >
> > Besides, I've found such a thing: Oracle refuses to shut down by command, when
> > Radiator is running. Oracle reports: waiting for unclosed connections. When I
> > stop Radiator, Oracle shuts down correctly.
> >
> > Thirdly, when I make radpwtst test FREQUENTLY for some test user, first test
> > works OK for Access-Request,Start and Stop, but the second, which goes right
> > adter the first, reports OK for "Access-Request" and "Accounting Stop", but No
> > reply for Start:
--
With regards,
Alexey A. Shavaldin [EMAIL PROTECTED]
--------------------
System Administrator
of Kraft-S, JSC
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
