-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 2021-11-10 at 09:02 +0100, Yves-Alexis Perez wrote:
> On Wed, 2021-11-10 at 08:10 +0100, Yves-Alexis Perez wrote:
> > 
> > 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.

So it might actually be worse than that.

I tried to set $enable_db = 0; in 50_user.conf and in the end it still failed
with:

Nov 10 20:07:12 lxc-amavis amavis[2387]: (02387-20) Requesting process rundown 
after 20 tasks (and 20 sessions)
Nov 10 20:07:12 lxc-amavis amavis[2387]: (02387-20) TempDir removal: empty 
tempdir is being removed: 
/var/lib/amavis/tmp/amavis-20211110T162308-02387-YoaC54ip
Nov 10 20:07:12 lxc-amavis amavis[2387]: (02387-20) load: 0 %, total idle 
13421.884 s, busy 22.927 s
Nov 10 20:07:12 lxc-amavis amavis[2387]: (02387-20) sd_notify (no socket): 
STOPPING=1\nSTATUS=Server rundown, notifying child processes.
Nov 10 20:07:12 lxc-amavis amavis[2387]: (02387-20) Net::Server: 
2021/11/10-20:07:12 Server closing!
Nov 10 20:07:12 lxc-amavis amavis[2387]: (02387-20) sd_notify (no socket): 
STATUS=Child processes have been stopped.

So no DB error at all, but the main process still exits, without failure:

● amavis.service - Interface between MTA and virus scanner/content filters
     Loaded: loaded (/lib/systemd/system/amavis.service; enabled; vendor
preset: enabled)
     Active: inactive (dead) since Wed 2021-11-10 20:07:12 CET; 4min 30s ago
       Docs: http://www.ijs.si/software/amavisd/#doc
    Process: 2385 ExecStartPre=/usr/bin/find /var/lib/amavis -maxdepth 1 -name
amavis-* -type d -exec rm -rf {} ; (code=exited, status=0/SUCCESS)
    Process: 2386 ExecStartPre=/usr/bin/find /var/lib/amavis/tmp -maxdepth 1 -
name amavis-* -type d -exec rm -rf {} ; (code=exited, status=0/SUCCESS)
    Process: 2387 ExecStart=/usr/sbin/amavisd-new foreground (code=exited,
status=0/SUCCESS)
   Main PID: 2387 (code=exited, status=0/SUCCESS)
        CPU: 29.155s

What would be the reason for a shutdown like this?
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmGMGhAACgkQ3rYcyPpX
RFu6XQgAwUcX3ZagGRHRfCRzVUwYR8zs+fAciovbU3a7lBTvhWIhXl3A68FPGy+D
ImvleCLHbFU+7NGpBhhmxYN723X4oLS1Z/L5WYAYGj/bI4EtefQghoQ3DsXX0jMt
/gWtNQe9brdOH/UzHCA7cCO/yDyYjPDK0ZK9TH3rDJl/4fH9V0oXEMjE7WSudWx+
TTyuZDBg+JUbW2cVEcGZx5RbjYBk9d5yXHHxCtLJxgi7pL2AxupUX0aSmQL4/0/P
Z//nB8ZdRwN/1Z6T/Z2O7FFwT+O0f2sa5bDYZeK3zbbpk33pstcqU4IJtVYnBwXG
kSRqOZypWbWHj5gEUlRv/YbwWemyhA==
=Y0iz
-----END PGP SIGNATURE-----

Reply via email to