Re: Re-Authentication Failure

Thanks for the info.

We are using NIS for authentication.  It dawned on me it could be the
cps (connections per seconds) in inetd, I will increase it and try
again.

Yanik

On Mon, 2004-07-12 at 15:40, Janne Pikkarainen wrote:
> On Mon, 2004-07-12 at 21:28, Yanik Charbonneau wrote:
> > Hi All,
> > 
> > We are in the process or implementing a new mail infrastructure, we have
> > 60000 users and want to run it using;
> > 
> > 	- 2 P4 for perdition ?directors?
> > 	- 6 dual Xeon for our "real" servers
> > 
> > Things are starting to pull together, I'm trying to do some load testing
> > with mstone and I'm getting a whole bunch of:
> > 
> > Jul 12 14:20:27 woody perdition[10906]: Auth:
> > 137.122.106.76->137.122.6.89 user="mailtestuser100" server="mail2"
> > port="143" status="failed: Re-Authentication Failure"
> > 
> > What is causing this?  How can I fix it?
> 
> The actual reason can lurk behind many things. I would check things in
> this order:
> 
> - Check the logs at server mail2 and/or stay logged on to that server
> during the test and see interactively how it (mis)behaves.
> 
> - What kind of authentication mechanism are you using? /etc/passwd, nis,
> ldap, pam_mysql, something else? Maybe authentication server falls upon
> its knees during the load test?
> 
> - Is your pop/imap daemon at mail2 launching from (x)inetd? If it is, is
> there some kind of connection rate limit applied?
> 
> - If everything else fails, increase debug level everywhere you can and
> see if any new info appears to your logfiles.
> 
> 
> Best regards,
> 
> Janne Pikkarainen 
--

-- 
Yanik Charbonneau                                 /~\  The ASCII
University of Ottawa                              \ /  Ribbon Campaign
Ottawa, Ontario                                    X   Against HTML
Canada                                            / \  Email!