> I'm still seeing the same error happen even after making that change in
> /etc/hosts.
> 
> If what you're saying above is true, then why am I am I only seeing
> these errors when there's a spike of incoming email. I'm graphing the
> number of mails coming in and every time I see these errors there's a
> large spike of incoming mail coming on the machine. Also, why would
> this cause spamd to seem to lose track of messages and have them not
> get tagged?
> 
> I checked the load balancer monitor check for spamassassin and we're
> doing the SPAMC PING test on it. The interval is set at 5 seconds and
> the timeout is set at 16 seconds. I don't recall seeing these errors
> before the upgrade.
> 
> Anyways, still puzzled. The two machines that have the newer perl
> version seem to not show this error. I saw it happen a few times on one
> of the machines, but not as many as the others.

Hmm.  Maybe it is indeed a result of the additional local loopback address
required for the IP load-balancers.  I'm asking around various places if
that's a supported situation.

Reply via email to