Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

Postfix or Dovecot 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: fixed kb: bug ABT: Group A

Applicable to:

  • Plesk Onyx for Linux
  • Plesk for Linux

Symptoms

When the IP address for a subscription with a large number of domains is changed, Postfix or Dovecot 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.

# systemctl status dovecot.service
...
failed to start dovecot imap/pop3 mail server
...

Cause

Product issue:

  • #PPPM-9733 "Changing an IP address of a subscription with multiple domains (30 or more) no longer breaks the Postfix service."
    Fixed in:

Resolution

Please consider updating your server:

Workaround

If update is not possible for some reason you may try the following

workaround

As a workaround, perform the following steps:

  1. Connect to the server via SSH;

  2. Create the following directory:

    For Postfix:

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

    For Dovecot:

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

  3. Create the configuration file in the directory from step 1:

    # 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/Dovecot:

    # systemctl daemon-reload
    # systemctl restart postfix.service
    # systemctl restart dovecot.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