Author: Juergen Weiss Date: To: exim-users Subject: [exim] Exim is not running the queue runner because of some linux
update
Hello all,
in the archive i have found some emails with a similar problem to mine but
no helpful fix.
I got the problem - whenever i start "exim -bd -q30m", the queue runner is
starting and ending one time (right after starting entries in the log file)
and then not anymore.
Even if i run it with "exim -d -v -bd -q1m", there is only one "exec
/usr/sbin/exim -q" right after the start.
Exim seems to dont exec the queue runner again.
I think some linux system update is the problem because exim will not start
the queue again even if i reinstall the distribution (SuSE) default rpm.
I have the problem on a SuSE 10.1 and 9.1 System. On the 9.1 i had the very
same problem till i completely reinstalled the whole suse linux.
Then removed exim package and reinstalled exim to its default configuration
with rpm, same problem.
Then reinstalled the whole linux to its very minimal default environment,
problem fixed.
I have found the day when this switched.
On this day i found that i have updated some suse linux packages - too many
to find the one which caused the problem.
Does someone got an idea which update could cause such a problem that the
queue runner will not start anymore?
Also theres no log of this behaviour :(
The only log is:
2006-12-03 22:16:17 exim 4.63 daemon started: pid=19225, -q1m, listening for
SMTP on [127.0.0.1]:25 85.10.xxx.xxx]:25 [127.0.0.1]:3939
2006-12-03 22:16:17 Start queue run: pid=19226
2006-12-03 22:16:17 End queue run: pid=19226
Thats all, no more "Start queue run"...
Ahh, you could ask if i changed something on my configuration - no, as i
wrote above i found the switching time from "all is working" to "queue
runner not starting anymore" and on that day (some months in the past), the
only change was some linux updates (without exim).
Hopefully someone of you got a hint for me to check.
