AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080916135205.4a1dc69b@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>,<ed.kwan@onstor.com>,<jonathan.goldick@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0BA2845C@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 16 Sep 2008 13:52:27 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Cc: "Ed Kwan" <ed.kwan@onstor.com>, "Jonathan Goldick"
 <jonathan.goldick@onstor.com>
Subject: Re: Defect  Yes TED00023471 [Cougar] repeating cluster error
 message on g10r10
Message-ID: <20080916135227.1c77537a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0BA2845C@onstor-exch02.onstor.net>
References: <ONSTOR-EXCH01FEZEqz000047ff@onstor-exch01.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0BA28450@onstor-exch02.onstor.net>
	<20080916134205.1d70a262@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0BA2845C@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I'm not arguing, I'm stating a simple fact.  People can make whatever
they want from it.  And yes, it's a bug, just not in exim.  Let's fix
the actual bug.

On Tue, 16 Sep 2008 13:46:35 -0700 "Maxim Kozlovsky"
<maxim.kozlovsky@onstor.com> wrote:

> You can not argue that having 500 exim processes running is not a bug
> which does not need to be fixed. Whatever the reason is, we should not
> have process duplication. Fix this one, if we still have the problem
> after that we'll look at it.
> 
> >-----Original Message-----
> >From: Andy Sharp
> >Sent: Tuesday, September 16, 2008 1:42 PM
> >To: Maxim Kozlovsky
> >Cc: Ed Kwan; Jonathan Goldick
> >Subject: Re: Defect Yes TED00023471 [Cougar] repeating cluster error
> >message on g10r10
> >
> >Exim is the victim, not the instigator, as I said before.
> >
> >On Tue, 16 Sep 2008 13:37:25 -0700 "Maxim Kozlovsky"
> ><maxim.kozlovsky@onstor.com> wrote:
> >
> >> I think Andy should work on fixing the problem with too many exim4
> >> processes running. The clustering problems are likely to be the
> >> downstream of that. Since every exim4 process opens a rmc session
> >> to the clusterrpc, too many processes will exhaust the limit of
> >> open sessions and cause the clustering failures.
> >>
> >> >-----Original Message-----
> >> >From: chris.vandever@onstor.com [mailto:chris.vandever@onstor.com]
> >> >Sent: Tuesday, September 16, 2008 1:30 PM
> >> >To: dl-Escalation
> >> >Cc: Ed Kwan; Jonathan Goldick; May Ma; Sandrine Boulanger; Ed
> >> >Kwan;
> >> Chris
> >> >Vandever; Andy Sharp
> >> >Subject: Defect Yes TED00023471 [Cougar] repeating cluster error
> >> message on
> >> >g10r10
> >> >
> >> >company_name:
> >> >id: TED00023471
> >> >Headline: [Cougar] repeating cluster error message on g10r10
> >> >State: Assigned
> >> >Note_Entry: The mightydog crash is defect #25366.  Subsequent
> >> >analysis there seems to indicate this is unrelated.
> >> >
> >> >Release_Project: 4.0.0.0
> >>
