Title: why does courier stop delivering?

Hello,

we are running Courier 0.42.2 on two load balanced RedHat 7.3 boxes, with more than 10000 virtual hosted domains.

We have been using it in our production environment for 1 year with no problems, but in the last week we are watching a strange behaviour: Very often (about 6-8 times a day), courier stops delivering either local or outgoing mail during a few minutes. It accepts connections, but there is no delivery at all. During this period of time, the log shows only messages of this kind:

Feb  2 10:32:36 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=393, inprogress=9

Feb  2 10:32:39 m3lnxsva01 courieresmtpd: started,ip=[::ffff:x.x.x.x]
Feb  2 10:32:39 m3lnxsva01 courieresmtpd: started,ip=[::ffff:x.x.x.y]
Feb  2 10:32:40 m3lnxsva01 courieresmtpd: started,ip=[::ffff:x.x.x.z]
Feb  2 10:32:41 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=393, inprogress=9

...
Feb  2 10:32:49 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=393, inprogress=9

Feb  2 10:32:50 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=393, inprogress=9

Feb  2 10:32:51 m3lnxsva01 courieresmtpd: started,ip=[::ffff:x.x.x.x]
Feb  2 10:32:51 m3lnxsva01 courieresmtpd: started,ip=[::ffff:x.x.x.y]
...
Feb  2 10:33:01 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=392, inprogress=8

... /several courieresmtpd: started .../
Feb  2 10:33:07 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=391, inprogress=7

... /several courieresmtpd: started .../
Feb  2 10:33:07 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=390, inprogress=6

...
Feb  2 10:33:07 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=389, inprogress=5

... /several courieresmtpd: started .../
Feb  2 10:33:10 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=Mon Feb  2 10:33:30 2004, queuedelivering=388, inprogress=4

Feb  2 10:33:30 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=388, inprogress=4
Feb  2 10:33:36 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=387, inprogress=3
Feb  2 10:33:42 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=387, inprogress=3
... /several courieresmtpd: started .../
... /several courierd: Waiting .../
...
Feb  2 10:35:31 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=387, inprogress=3
...
Feb  2 10:35:40 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=386, inprogress=2
...
Feb  2 10:35:58 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=385, inprogress=1
...
Feb  2 10:36:47 m3lnxsva01 courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=385, inprogress=1
Feb  2 10:36:48 m3lnxsva01 courierd: Loading STATIC transport module libraries.
Feb  2 10:36:48 m3lnxsva01 courierd: Courier 0.42.2.20030606 Copyright 1999-2002 Double Precision, Inc.
Feb  2 10:36:48 m3lnxsva01 courierd: Installing [0/0]


etc...

and starts delivering again messages.

As you can see, during more than 3 minutes, the server doesn't deliver any message, although there are lots of incoming mails. And when the "inprogress" deliveries comes to 0, the server has restarted and started delivering. Other times, we have to make a "courier restart" for the deliveries to run again. (During this period of time, it takes about 20-30 minutes for new arrived mail to be delivered to destination.)

I've considered changing the (default) queuelo and queuehi values, but I suspect this is not the problem, because during those intervals, no mail is processed at all, neither queued nor fresh.

Any clues what can be the problem/solution here? Do you need any other information?


Thank you.
Ra�l.


_____________________________________________________________
Uni2 Telecomunicaciones, S.A.U.
Aviso legal:

Este mensaje electr�nico est� dirigido �nicamente a la(s) direcci�n(es) indicadas anteriormente; el car�cter confidencial, personal e intransferible del mismo est� protegido legalmente. Cualquier revelaci�n, uso o reenv�o no autorizado, completo o en parte, est� prohibido.

Si ha recibido este mensaje por equivocaci�n, notif�quelo inmediatamente a la persona que lo ha enviado y borre el mensaje original junto con sus ficheros anexos sin leerlo ni grabarlo, total o parcialmente.

Gracias

Reply via email to