2017-10-25T09:55:43.186431+02:00 SERVER postfix/qmgr[22554]: 23A388234F5: removed
2017-10-25T09:56:32.509807+02:00 SERVER postfix/postfix-script[24714]: refreshing the Postfix mail system
2017-10-25T09:56:32.514089+02:00 SERVER postfix/master[22552]: reload – version 2.11.8, configuration /etc/postfix
2017-10-25T09:56:32.532268+02:00 SERVER postfix/scache[22560]: statistics: start interval Oct 25 09:55:43
2017-10-25T09:56:32.532532+02:00 SERVER postfix/scache[22560]: statistics: domain lookup hits=1 miss=2 success=33%
2017-10-25T09:56:32.532640+02:00 SERVER postfix/scache[22560]: statistics: address lookup hits=0 miss=2 success=0%
2017-10-25T09:56:32.532735+02:00 SERVER postfix/scache[22560]: statistics: max simultaneous domains=1 addresses=1 connection=2
2017-10-25T09:56:32.719778+02:00 SERVER postfix/postfix-script[24754]: stopping the Postfix mail system
2017-10-25T09:56:32.721256+02:00 SERVER postfix/master[22552]: terminating on signal 15
2017-10-25T09:56:32.932461+02:00 SERVER postfix/postfix-script[24869]: starting the Postfix mail system
2017-10-25T09:56:32.935970+02:00 SERVER postfix/master[24871]: daemon started – version 2.11.8, configuration /etc/postfix
2017-10-25T10:00:01.312186+02:00 SERVER postfix/postfix-script[29583]: stopping the Postfix mail system
2017-10-25T10:00:01.313398+02:00 SERVER postfix/master[24871]: terminating on signal 15
On 10/25/2017 03:24 AM, ChristianCzech wrote:[color=blue]
2017-10-25T09:55:43.186431+02:00 SERVER postfix/qmgr[22554]:
23A388234F5: removed
2017-10-25T09:56:32.509807+02:00 SERVER postfix/postfix-script[24714]:
refreshing the Postfix mail system
2017-10-25T09:56:32.514089+02:00 SERVER postfix/master[22552]: reload –
version 2.11.8, configuration /etc/postfix
2017-10-25T09:56:32.532268+02:00 SERVER postfix/scache[22560]:
statistics: start interval Oct 25 09:55:43
2017-10-25T09:56:32.532532+02:00 SERVER postfix/scache[22560]:
statistics: domain lookup hits=1 miss=2 success=33%
2017-10-25T09:56:32.532640+02:00 SERVER postfix/scache[22560]:
statistics: address lookup hits=0 miss=2 success=0%
2017-10-25T09:56:32.532735+02:00 SERVER postfix/scache[22560]:
statistics: max simultaneous domains=1 addresses=1 connection=2
2017-10-25T09:56:32.719778+02:00 SERVER postfix/postfix-script[24754]:
stopping the Postfix mail system
2017-10-25T09:56:32.721256+02:00 SERVER postfix/master[22552]:
terminating on signal 15
2017-10-25T09:56:32.932461+02:00 SERVER postfix/postfix-script[24869]:
starting the Postfix mail system
2017-10-25T09:56:32.935970+02:00 SERVER postfix/master[24871]: daemon
started – version 2.11.8, configuration /etc/postfix
2017-10-25T10:00:01.312186+02:00 SERVER postfix/postfix-script[29583]:
stopping the Postfix mail system
2017-10-25T10:00:01.313398+02:00 SERVER postfix/master[24871]:
terminating on signal 15
there is a solution for this?[/color]
Signal 15 is SIGTERM, meaning a normal terminate signal. This usually
means you told the service to stop, e.g. systemctl stop postfix
If that is not what you did, then the next step is probably to get postfix
logs specifically, maybe systemd messages from systemctl/journalctl, to
see if they have any other information.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
judging from the reload and later restart, plus the time stamps, I’d guess someone was working on the Postfix confguration. I cannot tell if YaST will cause any config refreshes (“reload” rather than “restart”), but at least I’d check who was logged in to that specific machine during that time…