This problem has been solved. It is a buggy old version of Domino that doesn't send a correct FIN response packet as the second part of the TCP connection teardown, thus leaving many connections in CLOSE_WAIT state; I discovered an IBM paper about the problem. RH7.1 (the earlier opsys) was more tolerant of this problem than the current opsys (FC5). The solution is that the client has been told to put his hand in his pocket and upgrade his Domino server software.
On Wed, May 10, 2006 10:21, James Gray wrote: > On Tue, 9 May 2006 03:03 pm, Howard Lowndes wrote: >> I have a Domino server which is now running on FC5 having previously >> been >> running on RH7.1 >> >> I can establish an SMTP connection to it (3 part TCP handshake) but it >> won't announce itself to the calling host, except I did manage to get it >> to announce, and receive, an email immediately after I had booted it and >> started the Domino server, but not since. >> >> Any ideas? > > I've seen this on sendmail and postfix when there are permission problems > at > the file system level for the mail queue directories - ie, process running > as > user "foo" but queue dirs are only writable by "root". Another possible > culprit could be tcp wrappers (if you're using them for SMTP). > > Anything in the logs? What happens when you launch the SMTP server and > run it > in the foreground with a high debug level (can Domino even do that?). > > HTH, > > James > -- > The University of California Statistics Department; where mean is normal, > and deviation standard. > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
