Applicable to:
- Plesk Onyx for Linux
- Plesk for Linux
Symptoms
When the IP address for a subscription with more than ~1000 domains is changed, postfix service stops:
# systemctl status postfix.service
● postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2018-12-04 16:47:01 CET; 6s ago
Process: 95048 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
Process: 94905 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS)
Process: 94902 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=0/SUCCESS)
Process: 94900 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS)
Main PID: 94977 (code=killed, signal=TERM)
plesktest-plesk001 systemd[1]: postfix.service failed.
plesktest-plesk001 systemd[1]: start request repeated too quickly for postfix.service
plesktest-plesk001 systemd[1]: Failed to start Postfix Mail Transport Agent.
Cause
This is a Plesk bug with ID #PPPM-9733, which is planned to be fixed in one of the future product updates.
Resolution
As a workaround, perform the following steps:
-
Connect to the server via SSH;
-
Create the following directory:
# mkdir /etc/systemd/system/postfix.service.d/
-
Create the configuration file:
# touch 10-start_limit_interval.conf
-
Use the command below to add the directive to the
10-start_limit_interval.conffile:# StartLimitInterval='0' > /etc/systemd/system/postfix.service.d/10-start_limit_interval.conf
-
Reload unit files and restart Postfix:
# systemctl daemon-reload
# systemctl start postfix.service
Comments
2 comments
Any news on a fix?
@Stéphan Schamp
No news regarding ETA so far. Please make sure to follow this article to receive a notification on the fix as soon as it is released.
Please sign in to leave a comment.