> lena@??? hat am 06.12.2023 08:00 CET geschrieben:
>
>
> > >> But I would expect that a queue runner (I start exim with -q10m)
> > >> in a future run would take these messages but it doesn't seem to happen.
> > >
> > > Do you see "Start queue run", "End queue run" in the mainlog?
> > > https://bugs.exim.org/show_bug.cgi?id=3046
> >
> > Rarely. I think that might be it. Thanks.
> >
> > I just tried setting queue_fast_ramp to false (which is a changed default
> > in 4.97 and the changed code in the patch seems to have something to do
> > with it) and suddenly the message comes as often as expected.
>
> I haven't this problem. What's different between your system and mine?
> Mine is FreeBSD 12.4 on a KVM VPS.
> I also use -q10m , without -qq .
> "serialize_hosts = *" in transports.
What I see is that it works for some time and then suddenly it stops. I just rebooted all the hosts. host5 and host6 are mail-servers which are only for sending out mails, host1-4 are incoming mailservers.
*** executing on host1 ***
2023-12-06 17:42:01 Start queue run: pid=6499
2023-12-06 17:45:38 Start queue run: pid=3015
2023-12-06 17:50:38 Start queue run: pid=12444
2023-12-06 17:55:38 Start queue run: pid=20100
2023-12-06 18:00:38 Start queue run: pid=27604
*** executing on host2 ***
2023-12-06 17:48:43 Start queue run: pid=3025
2023-12-06 17:53:43 Start queue run: pid=11400
2023-12-06 17:58:43 Start queue run: pid=17596
2023-12-06 18:03:43 Start queue run: pid=29731
2023-12-06 18:08:43 Start queue run: pid=40160
*** executing on host3 ***
2023-12-06 17:37:46 Start queue run: pid=88326
2023-12-06 17:42:46 Start queue run: pid=96013
2023-12-06 17:47:46 Start queue run: pid=4963
2023-12-06 17:52:20 Start queue run: pid=3818
2023-12-06 17:57:20 Start queue run: pid=13730
*** executing on host4 ***
2023-12-06 17:32:11 Start queue run: pid=55264
2023-12-06 17:37:12 Start queue run: pid=65384
2023-12-06 17:42:12 Start queue run: pid=73605
2023-12-06 17:54:40 Start queue run: pid=4020
2023-12-06 17:59:40 Start queue run: pid=12364
*** executing on host5 ***
2023-12-06 17:47:46 Start queue run: pid=57582
2023-12-06 17:50:34 Start queue run: pid=2665
2023-12-06 17:55:34 Start queue run: pid=16043
2023-12-06 18:00:34 Start queue run: pid=36513
2023-12-06 18:05:34 Start queue run: pid=49185
*** executing on host6 ***
2023-12-06 17:48:14 Start queue run: pid=61511
2023-12-06 17:53:14 Start queue run: pid=85406
2023-12-06 17:58:14 Start queue run: pid=9527
2023-12-06 18:03:14 Start queue run: pid=80086
2023-12-06 18:08:14 Start queue run: pid=59034
I don't understand it. Maybe it is the bug you filed. Then I'd need to try to patch the port and build it on one host and see if the behaviour improves.
Niels
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
