Your message dated Tue, 16 Nov 2021 20:05:44 +0100
with message-id <[email protected]>
and subject line Re: amavisd-new: amavis stops with DB unregistering failed
has caused the Debian Bug report #999340,
regarding amavisd-new: amavis stops with DB unregistering failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
999340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999340
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: amavisd-new
Version: 1:2.11.1-5
Severity: important
Hi,
I recently updated my amavis/spamassassin LXC to bullseye and started
experiencing random amavis shutdowns, which in turn interrupt the mail
pipeline completely. That happens sometime after few minutes, sometimes
after a few hours.
I've tried raising the debug level but it doesn't really help.
In the logs, what I have is:
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) Requesting process rundown
after 20 tasks (and 20 sessions)
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) TempDir removal: empty
tempdir is being removed:
/var/lib/amavis/tmp/amavis-20211109T115021-00456-Z7zXfwfm
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) load: 0 %, total idle
25624.889 s, busy 22.962 s
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) sd_notify (no socket):
STOPPING=1\nSTATUS=Server rundown, notifying child processes.
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) Net::Server:
2021/11/09-18:57:49 Server closing!
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) sd_notify (no socket):
STATUS=Child processes have been stopped.
Nov 9 18:57:49 lxc-amavis amavis[456]: (00456-20) (!)Amavis::END: DB
unregistering failed:
The first few logs seem normal (apparently the child processes will stop
after processing a number of tasks and a new child will be started) but
somehow the process then fails with that DB unregistering failed
message.
Unfortunately, I don't have any log (with $log_level=3) after that line,
so I'm unsure what actually happen.
I've tried to remove the dbs in /var/lib/amavis/db in case those would
be corrupted, but it didn't work, I still had the failure above.
I didn't find a lot of references to that log message so I'm opening a
bug here.
I don't have reportbug nor net access on the LXC so I can't provide the
full reportbug output but if you need information on the system please
ask. It's an up to date bullseye LXC running on an up to date bullseye
host.
Regards,
--
Yves-Alexis
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, 2021-11-12 at 15:12 +0100, Yves-Alexis Perez wrote:
> I'll let it run a bit more and then close the bug if it works.
I can confirm I didn't have any more problem, so I consider the bug closed and
hopefully if someone else has the problem she'll see the fix about $max_server
here.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmGUAQgACgkQ3rYcyPpX
RFtXGggA0aWdw/ioRr7oTsJI3iehw2w2iSmn9VphDs3z4QZBDSkcm63KtPdjwzAH
3sk+qDsNIgWkvJfdVlt+fxMVtK9Uw2PutyUXo/PVMCt1vvQpiZfKwkP22pAuNYWW
rjfABxvF6k0ILVB17wiClbRMoOC93rEAlo0UaDwXFSI7HhE0bG7rSHv1gYE47XOu
ebtnA2Pqquzuzg6venaEb0nBwKsbqblzvRubfpWMLlJGRd0UTu1sn4hfJzHXw5F1
MBU9/5xHCZrC0cFlt38zB6E5YczdMyyGY3GOoM4GOn63W7UOQHn8nDP/3h6j00H7
FLWzd0rdpn2XMQAzxR5tJ4tMUNW6mA==
=peKl
-----END PGP SIGNATURE-----
--- End Message ---
