Articles in this section

See more

Postfix stops after subscription IP address is changed: Failed to start Postfix Mail Transport Agent

Avatar
George Alibegashvili
Updated
Follow
Plesk for Linux Plesk Onyx for Linux kb: bug ABT: Group A

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:

  1. Connect to the server via SSH;

  2. Create the following directory:

    # mkdir /etc/systemd/system/postfix.service.d/

  3. Create the configuration file:

    # touch 10-start_limit_interval.conf

  4. Edit the configuration file 10-start_limit_interval.conf adding the following strings:

    CONFIG_TEXT: [Service]
    StartLimitInterval=0

  5. Reload unit files and restart Postfix:

    # systemctl daemon-reload
    # systemctl start postfix.service

Comments

4 comments

Sort by Date Votes
  • Avatar
    Stéphan Schamp

    Any news on a fix?

    0
    Comment actions Permalink
  • Avatar
    Alisa Kasyanova

    @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.

    0
    Comment actions Permalink
  • Avatar
    GK

    I agree the problem is in Plesk and should be fixed (this problem is here for ages).

    2nd the workaround does not work, because the override files does not include a section (and this ignored by systemd). Correct content of file should be:

    [Service]
    StartLimitInterval=0

     

    0
    Comment actions Permalink
  • Avatar
    George Alibegashvili

    Hello @GK, Thank you for your feedback, article changed accordingly.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles