[Building Sakai] James email issues

[Joshua Swink]

It reaches James from about three mail relay servers. In this incident:

- We restarted Sakai at 6:30 A.M.
- Over the next few hours, about 25 messages were received and relayed
through the email archive.
- At the same time, two of the relay servers were contacting James
once per minute to say hello (as they always do, without problems)
- At 12:40 P.M. James' 30 connections were tied up in the CLOSE_WAIT
state and it stopped accepting connections.

After restarting Sakai, this hasn't occurred again.

Josh

On Wed, Oct 7, 2009 at 8:03 PM, Michael J Wenk <mjwenk at ucdavis.edu> wrote:
>
> 3) We had one incident where the incoming connections to James (from
> our email relay servers) were piling up in CLOSE_WAIT state. After 30
> of them piled up, it was impossible for mail to be delivered to Sakai
> any more. The connections did not close until I restarted Sakai.
>
> I am going to change all of the logging in James' environment.xml to
> DEBUG. It would be especially helpful if there were any other places
> that debugging output could be turned on.
>
> The above has happened to us.  I have debug turned on all of our nodes, and while its interesting, it doesn't seem to really show the problem.  How does mail reach James?  Is there a load balancer involved?
>
> Mike
>
>
>