Hello !
The fact is that I have the same problem, not solved yet. Radiator works for
first 30 users and then reports about Session-Timeouts.
Besides, such Session-Timeouts also occur when a user arrives at the NAS's
line with some NASIDENTIFIER and NASPORT. If there is a line in my RADONLINE,
containg these NASIDENTIFIER and NASPORT, Radiator sends "delete from
RADONLINE where NASIDENTIFIER=... and NASPORT=... and then after about 1
minute reports about Session-Timeout and after that doesn't want to
authenticate at all...
On Monday 06 November 2000 11:30 pm, Hugh Irvine wrote:
> > I'm testing Radiator with SQL (Oracle 8.1.6) and something strange
> > happens. After accessing DB (with <AutBy SQL> or <SessionDatabase SQL>),
> > Radiator dies and this message appears (in 10 seconds like say
> > sessiondatabase tag below):
> >
> > timeout at /usr/local/lib/perl5/site_perl/5.005/Radius/SqlDb.pm line 226
>
> It sounds like a problem with the DBD-Oracle configuration. There is an
> item on Oracle in the FAQ here:
>
> http://www.open.com.au/radiator/faq.html#58
Here is my TNSNAMES.ora file
xxx =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = yyy.yyy.yy)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = xxx)
)
)
Is something wrong with this Oracle config ? In accordance with the FAQ,
everything seems to be OK with tnsnames.ora.
Thanks for help.
--
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.
