On 2025-06-22 11:14:31 -0400, Noah Meyerhans wrote:
> On Sun, Jun 22, 2025 at 10:01:52AM -0400, Noah Meyerhans wrote:
> > I also don't see it on upgrade from -3 in trixie, but I do see a couple
> > of unexpected things:
> >
> > Setting up sa-compile (4.0.1-4) ...
> > Running sa-compile (may take a long time)
> > Warning: The unit file, source configuration file or drop-ins of
> > spamd.service changed on disk. Run 'systemctl daemon-reload'
> > to reload units.
> > Setting up spamd (4.0.1-4) ...
> > Processing triggers for man-db (2.13.1-1) ...
>
> Strangely, this does not seem to happen 100% of the time. Here is a
> transcript of an upgrade from -3 to -4 that did not encounter this
> issue.
Note that the /var/log/apt/term.log file here just contains
Log started: 2025-06-21 13:25:21
[...]
Setting up sa-compile (4.0.1-4) ...
Running sa-compile (may take a long time)
Warning: The unit file, source configuration file or drop-ins of spamd.service
changed on disk. Run 'systemctl daemon-reload' to reload units.
Setting up spamd (4.0.1-4) ...
Processing triggers for man-db (2.13.1-1) ...
Log ended: 2025-06-21 13:25:54
like above.
The error is in the journalctl output. With the context:
Jun 21 13:25:30 qaa systemd[1]: Reloading spamd.service - Perl-based spam
filter using text analysis...
Jun 21 13:25:30 qaa spamd[1978]: spamd: server hit by SIGHUP, restarting
Jun 21 13:25:30 qaa systemd[1]: Reloaded spamd.service - Perl-based spam filter
using text analysis.
Jun 21 13:25:30 qaa spamd[1978]: spamd: child [2026] killed successfully:
interrupted, signal 2 (0002)
Jun 21 13:25:30 qaa spamd[1978]: spamd: child [2025] killed successfully:
interrupted, signal 2 (0002)
Jun 21 13:25:30 qaa spamd[1978]: spamd: server socket closed, type
IO::Socket::IP
Jun 21 13:25:30 qaa spamd[1978]: spamd: server socket closed, type
IO::Socket::IP
Jun 21 13:25:30 qaa spamd[1978]: spamd: restarting using '/usr/bin/perl -T -w
-I /etc/perl -I /usr/lib/x86_64-linux-gnu/perl5/5.40 -I /usr/share/perl5 -I
/usr/lib/x86_64-linux-gnu/perl-base -I /usr/lib/x86_64-linux-gnu/perl/5.40 -I
/usr/share/perl/5.40 /usr/sbin/spamd --pidfile=/run/spamd.pid --create-prefs
--max-children 5 --helper-home-dir'
Jun 21 13:25:30 qaa systemd[1]: Reload requested from client PID 362049
('systemctl') (unit session-2.scope)...
Jun 21 13:25:30 qaa systemd[1]: Reloading...
[... things related to other daemons ...]
Jun 21 13:25:30 qaa systemd[1]: Reloading finished in 154 ms.
[... things related to other daemons ...]
Jun 21 13:25:30 qaa systemd[1]: Reload requested from client PID 362131
('systemctl') (unit session-2.scope)...
Jun 21 13:25:30 qaa systemd[1]: Reloading...
[... things related to other daemons ...]
Jun 21 13:25:30 qaa systemd[1]: Reloading finished in 131 ms.
Jun 21 13:25:30 qaa systemd[1]: Stopping spamd.service - Perl-based spam filter
using text analysis...
Jun 21 13:25:30 qaa spamd[1978]: spamd: server killed by SIGTERM, shutting down
Jun 21 13:25:30 qaa spamd[1978]: replacetags: regexp compilation failed for
__HOURS_DEADLINE: [... hundreds of lines ...]
Jun 21 13:25:30 qaa spamd[1978]: zoom: able to use 399/399 'body_0' compiled
rules (100%)
Jun 21 13:25:31 qaa spamd[1978]: spamd: server started on IO::Socket::IP
[::1]:783, IO::Socket::IP [127.0.0.1]:783 (running version 4.0.1)
Jun 21 13:25:31 qaa spamd[1978]: spamd: server pid: 1978
Jun 21 13:25:31 qaa spamd[1978]: spamd: server successfully spawned child
process, pid 362204
Jun 21 13:25:31 qaa spamd[1978]: spamd: server successfully spawned child
process, pid 362205
Jun 21 13:25:31 qaa spamd[1978]: prefork: child states: IS
Jun 21 13:25:31 qaa spamd[1978]: prefork: child states: II
Jun 21 13:25:50 qaa systemd[1]: spamd.service: State 'stop-sigterm' timed out.
Killing.
[...]
Why is there an error *after* it is killed by SIGTERM?
There might be a race condition, which could explain why this is not
always visible.
Also, I don't understand the "spamd: server started on..." why the
goal is to kill it (for the upgrade?) as seen at
Jun 21 13:25:30 qaa systemd[1]: Stopping spamd.service - Perl-based spam filter
using text analysis...
and
Jun 21 13:25:50 qaa systemd[1]: spamd.service: State 'stop-sigterm' timed out.
Killing.
No issues with "systemctl start spamassassin-maintenance.service".
But the upgrade case may be different.
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
