Re: [tpop3d-discuss] open sockets...

[prune]

Michael Klatsky wrote:
> Chris & Prune-
>
> First of all- I want to say a big thanks for all your help in
> implementing DARC, and in addressing the segfault on incorrect password
> issue.
>
> It looks like there is one issue that I see- and I believe it's a
> "solaris" ism as I haven't seen much about the issue...
>
> I have a system (my "semi-production" system)  which has 3 regular
> users. Doing an lsof shows 241 open tpop3d connections in either
> CLOSE_WAIT (63) or ESTABLISHED (177). These have been open for quite
> awhile (hours).
>
> This seems quite high, and I would believe that tpop isn't releasing the
> connections to the ldap server. Some output:
>
> tpop3d     418     root  236u  IPv4 0x30001500e10     0t697    TCP
> mail:33263->mail:ldap             
>  (ESTABLISHED)
> tpop3d     418     root  237u  IPv4 0x30001500050     0t792    TCP
> mail:33271->mail:ldap             
>  (ESTABLISHED)
> tpop3d     418     root  238u  IPv4 0x300015
> 5be60     0t697    TCP
> mail:33272->mail:ldap             
>  (ESTABLISHED)
> tpop3d     418     root  239u  IPv4 0x3000150e908     0t792    TCP
> mail:33275->mail:ldap             
>  (ESTABLISHED)
> tpop3d     418     root  240u  IPv4 0x30001568e18     0t697    TCP
> mail:33276->mail:ldap             
>  (ESTABLISHED)
>
> I'm currently looking into the Solaris tuning aspects too, and I'll give
> some feedback on that.
>
> M
>   
  
241 opened socket for 3 clients ?
:)
  
you (normaly) can't do anything about CLOSE_WAIT .... this is system related.
then, tpop3d have 177 opened socket to the ldap server.... this is a problem.
Normaly tpop3d use (and re-use) the same connection... so I believe the same
socket.
If this happen, it's probably because you're re-connecting to the server
for every pop you do.
is there a  relation between the number of sockets and the number of times
you popped mail ?
  
I saw Chris released some patch for connecting every time you pop.... did
you apply it ?
  
from openldap man page : 
  
UNBINDING
       The ldap_unbind() call is used to unbind from  the  direc-
       tory,  terminate  the  current  association,  and free the
       resources contained in  the  ld	structure.   Once  it  is
       called,	the  connection to the LDAP server is closed, and
       the ld structure is invalid.  The ldap_unbind_s() call  is
       just  another  name for ldap_unbind(); both of these calls
       are synchronous in nature.
As the unbind function is associated to the bind function (and not to the
ldap_connect or ldap_init), I'm not pretty sure the connection (the TCP)
is dropped. Normaly you should be able to unbind and re-bind after that....
(unbinding makes you anonymous...).
maybe there's a bug here.
I'll try to test that if I have some time.
  
Could you send me the auth_ldap.c/.h files you used on you pre-prod server
?
  
Cheers,
  
Prune
  
> On Sat, 2002-06-08 at 17:04, Michael Klatsky wrote:
> > Drac is working in a test environment...:)
> >
> > I'll be dropping it into a (semi) production environment and see how it
> > goes- I'll let you know.
> >
> > One thing to note- make sure that libdrac.a is in your LD_LIBRARY_PATH,
> > otherwise confgure won't pick it up.
> >
> > M
> >
> >
> > <snip>
> >       
>