Lars Bjørndal writes:
> https://lamasti.net/filer/shutdown.log.gz
You've got some kind of logging problem with writing to the persistent
storage for the log, whatever that is (defaults to several files in
$var/dir/logs, but can be configured very flexibly using the stdlib
logging module). A bunch of Mailman processes are raising exceptions
when trying to log that they're shutting down. This could result in a
deadlock, which is why systemd terminates the processes with SIGABRT.
There's also a message about reentrancy (I think only one per process,
but Mailman 3 spawns lots of processes). It might be a bug in logging
(not Mailman code) but I think that's some exception handler that's
trying to log the logging exception. If so, it's not the root problem
and should not recur if you fix the basic problem.
1. What, if anything, is in Mailman's own logs? This appears to be
systemd's log from journalctl.
2. Do you have any settings for logging in mailman.cfg?
3. If your logging handler is a file-based handler, maybe the log
partition is full.
4. Maybe there is some security restriction (selinux?) on the logging
channel, whatever it is. Or a permissions restriction on the file
system so Mailman can't write.
I also noticed that PostgreSQL gets shut down, but there's no log that
it gets restarted. I think Mailman should then shutdown with an error
that it can't talk to the database, but maybe it retries a few times.
Steve
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/EIOVUNSLPFEMBC5S6OFMZPOSQIFEB4UX/
This message sent to [email protected]
