Bug#289607: (no subject)
Andreas Metzler
Andreas Metzler <ametzler@downhill.at.eu.org>, 289607@bugs.debian.org
Mon, 10 Jan 2005 07:47:40 +0100
On 2005-01-10 Rory Campbell-Lange <rory@campbell-lange.net> wrote:
> Package: exim4
> Version: 4.34-8
> Severity: important
> I am seeing lots of exim4 processes in the following state:
Strange.
> exim4 6304 Debian-exim 0u IPv4 655292 TCP myserver:smtp->mail2.myisp.net:49602 (CLOSE_WAIT)
> exim4 6304 Debian-exim 2u IPv4 655292 TCP myserver:smtp->mail2.myisp.net:49602 (CLOSE_WAIT)
> exim4 6304 Debian-exim 3u IPv4 655313 UDP myserver:35888->ns1.myisp.net:domain
What does exiwhat say?
> Also lots of processes are running:
> ....
> Debian- 6162 0.0 0.2 8488 2556 ? Ss 13:06 0:00 /usr/sbin/exim4 -bd -q30m
> Debian- 6292 0.0 0.2 8500 2692 ? S 13:11 0:00 /usr/sbin/exim4 -bd -q30m
> Debian- 6304 0.0 0.2 8500 2692 ? S 13:12 0:00 /usr/sbin/exim4 -bd -q30m
> Debian- 6399 0.0 0.2 8500 2692 ? S 13:35 0:00 /usr/sbin/exim4 -bd -q30m
> ....
Are you starting exim4 bdifferent means that /etc/init.d/exim4?
e.g. Have you symlinked /usr/sbin/exim4 to /usr/sbin/exim and still
exim uninstalled but not purged so its cronjobs are still running?
dpkg -l '*exim*'
or inetd?
find /etc -type f -print0 | xargs -0r grep -l exim
> If left all smtp connections are saturated over time, as the number of
> exim processes increases incrementally.
> After issuing an /etc/init.d/exim4 stop there are still lots of exim4
> processes running, which have to be killed manually.
[...]
/etc/init.d/exim4 stop wil only kill the master-daemon process(es)
(smtp-listener/queue-runner) it started, open smtp deliveries will not
be killed.
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
http://downhill.aus.cc/