[exim-dev] [Bug 3046] New: exim 4.97 stops starting queue ru…

Top Page
Delete this message
Reply to this message
Author: Exim Bugzilla
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 3046] New: exim 4.97 stops starting queue runners
https://bugs.exim.org/show_bug.cgi?id=3046

            Bug ID: 3046
           Summary: exim 4.97 stops starting queue runners
           Product: Exim
           Version: 4.97
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Queues
          Assignee: unallocated@???
          Reporter: wbreyha@???
                CC: exim-dev@???


It already occurred once with RCx and happend again with final 4.97 that no
more queue runners are started by the main process which is started with -q5m.

host/s is/are running as VMware guest on fully updated Rocky Linux 8.8.

This never occurred in my setup with Exim4 yet (since 2006).

I do not use any unusual settings or multiple queues. One main queue and mostly
defaults aside from:
queue_only_load = 15
queue_run_max = 20

smtp_accept_queue = 192
smtp_accept_queue_per_connection = 20

The log shows one final queue run:
Nov 9 14:48:06 roger exim[3862339]: Start queue run: pid=3862339
Nov 9 14:48:06 roger exim[3862339]: End queue run: pid=3862339
... and nothing with "queue" afterwards.

Since this is a MX host the queue is empty most of the time only filled if the
upper limits are reached.

It looks like Exim fails to handle/restart it's own timer/alarm in some case.

I'm still searching my logs if there was something "unusual" at this time.

There was quite some load on the system at the time, but nothing of concern.
While all of our 4 MX hosts had the same load (~5-10) it happened only on one
of them. But I see no log entries that queue_only_load was reached.

Looking at some of the queued mails -Mvh doesn't show any unusual values.

Since these hosts are syslogging to a remote host there is no "-HUP" for Exim
at midnight.

--
You are receiving this mail because:
You are on the CC list for the bug.

--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@???
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/