Hello Fernando -
Thanks for sending the files.
I would agree with Mariano ("Mariano Absatz" <[EMAIL PROTECTED]>) who
suggested trying the HoldServerConnection parameter, however this was only
added in Radiator 2.15.1 and I note that you are running 2.14.1.
I would suggest that you upgrade to the latest Radiator 2.17.1, which has
also had some additional work done on the LDAP modules.
Please let me know how the new version of Radiator works for you.
hth
Hugh
On Saturday 03 March 2001 01:06, Fernando Almeida wrote:
> > Im sending you the data you requested (the radius configuration file
> and a trace 4 log). The strange is that the LDAP connections are still
> estabilished ten minutes after the test (Im sending you a "netstat -na"
> output executed ten minutes after the autentications ended ).
> Every time I execute the radpwtst, the connections are being helded
> in the estabilished status... After a number of executions, there are no
> more connections available and the radiator begins to log "Unable to
> bind"...
>
> Thank you in advance...
>
> Fernando
>
>
>
> -----Mensagem original-----
> De: Hugh Irvine [mailto:[EMAIL PROTECTED]]
> Enviada em: Friday, March 02, 2001 1:58 AM
> Para: Fernando Almeida; '[EMAIL PROTECTED]'; Christian Pinheiro;
> Fabiano Bianchi; Rodrigo Castelar Silva
> Assunto: Re: (RADIATOR) <Auth By LDAP2> hangs the connections
>
>
>
> Hello Fernanado -
>
> On Friday 02 March 2001 06:20, Fernando Almeida wrote:
> > I am making some performance tests with Auth by LDAP2. My LDAP
> > server is a NT machine running NT4 and Site Server 3 and my radiator is
> > running in a machine with FreeBSD 4.0.
> >
> > Basically, I used the script radpwtst with the iteractions parameter
> > of 10,20,50,200,500,1000.. and plot the this numbers versus the time
> > spent to complete the procedure. When the number is too high, (400 or
> > more) the radiator begins to log a lot of mesgs like "Could not bind with
> > o=Brprima..." and running a "netstat -na" I see a lot of connections to
>
> the
>
> > LDAP estabilished. If I try to telnet the LDAP Server in the port 389 in
> > the middle of the execution of radpwtst, the machine responds with
> > "Connection refused by host".
> >
> > I dont know exactly what is happening, but I feel that this is a
> > limitation of the LDAP (perhaps configurable), but Im not sure about it.
>
> I would suggest that you start with just a small number of requests (say
> 10)
>
> and run Radiator with a trace 4 debug so you can see how much time is being
> taken by the LDAP queries. This will tell you a lot about what sort of
> performance you can expect from your setup.
>
> If you would like to send me a copy of your configuration file (no secrets)
> and a copy fo the trace 4 I will be happy to take a look.
>
> regards
>
> Hugh
----------------------------------------
Content-Type: text/plain; charset="iso-8859-1"; name="Netstat.txt"
Content-Transfer-Encoding: 7bit
Content-Description:
----------------------------------------
----------------------------------------
Content-Type: text/plain; charset="iso-8859-1"; name="Radiusldap.txt"
Content-Transfer-Encoding: 7bit
Content-Description:
----------------------------------------
----------------------------------------
Content-Type: text/plain; charset="iso-8859-1"; name="TraceLevel4.txt"
Content-Transfer-Encoding: quoted-printable
Content-Description:
----------------------------------------
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.