On Friday, November 24, 2023 at 3:51:07 AM UTC-8 jochen....@gmail.com wrote:
Perhaps I should add, that manually a
service amavis start
also did not solve the problem, but a
service amavis restart
helped. The Active state again changed to active(running)
jochen....@gmail.com schrieb am Freitag, 24. November 2023 um 12:46:28
UTC+1:
Hi,
I manage a Debian Mailserver running postfix, amavis and others. I have
service statements in place that should keep the server running.
>From time to time, the service resource does not correctly restart the
amavis service.
if I do service amavis status, the output should be
Active: active (running)
but it seems to me, when the output is
Active: active (exited)
my service resource does not work:
service { 'amavis':
ensure => running
}
active(exited) is the typical state a running postfix is in... I don't
know, why this does not seem to work with amavis. Can anyone please share
some knowledge how to correctly keep amavis running?
Thanks, best
Jochen
This is a problem with amavis, not puppet. You'll need to do systemctl
status amavis, journalctl --pager-end --unit amavis, and look at amavis's
own logs to see why the service is dying or not starting.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/47f189bb-e3d7-49b1-a340-c1d7fdec306en%40googlegroups.com.
