On October 19, 2021, we have enabled 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.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing 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.

Articles in this section

See more

Upgrade to Plesk Obsidian fails with Postfix dependency error: Error: Package: 2:postfix-perl-scripts-2.10.1-7.el7.x86_64 (base) Requires: postfix = 2:2.10.1-7.el7

Avatar
Yaroslav Tarasov
Updated
Follow
kb: bug ABT: Group A Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux

Symptoms

  • Upgrade to Plesk Obsidian fails with the following dependency error if postfix-perl-scripts is installed:

    PLESK_ERROR: Exception: Failed to solve dependencies:
    2:postfix-perl-scripts-2.10.1-7.el7.x86_64 requires postfix = 2:2.10.1-7.el7
    Error: Package: 2:postfix-perl-scripts-2.10.1-7.el7.x86_64 (base)
    Requires: postfix = 2:2.10.1-7.el7
    Installed: 2:postfix-3.4.5-2.centos.7+p18.0.19.0+t190904.1310.x86_64 (@PLESK_18_0_19-dist)
    postfix = 2:3.4.5-2.centos.7+p18.0.19.0+t190904.1310
    Available: 2:postfix-2.10.1-7.el7.x86_64 (base)
    postfix = 2:2.10.1-7.el7

  • In Plesk Obsidian, it's not possible to install additional Postfix packages such as postfix-perl-scripts.

Cause

This is considered as a Plesk bug with ID #PPPM-11129 which will be fixed in future Plesk updates.

Resolution

As a temporary workaround, apply the following solution:

  1. Connect to the server via SSH

  2. Remove postfix-perl-scripts package:

    # yum remove postfix-perl-scripts

  3. Proceed with upgrade:

    # plesk installer

    Note: Currently it is not possible to use additional Postfix libraries/packages in Plesk Obsidian.

Comments

8 comments

Sort by Date Votes
  • Avatar
    Luca

    While trying the same Obsidian upgrade (Plesk 17.8 -> Plesk 18), I experienced the same dependency issue with "postfix = 2:2.10.1-7.el7".

    In my case, the troubling package is "2:postfix-sysvinit-2.10.1-7.e17.noarch": it will not upgrade, citing the same dependency. As a result, it will block the whole upgrade.

    Successfully applied the resolution:

    1. Connect via SSH

    2. Run "yum remove postfix-sysvinit"

    3. Run "plesk installer"

     

    Thank you!  :-)

    Luca

    1
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @Thank you for sharing with us!

    0
    Comment actions Permalink
  • Avatar
    Tobias Buschor

    When will this be fixed? I am afraid to apply a "temporary workaround".

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Tobias, right now we don't have ETA.

    0
    Comment actions Permalink
  • Avatar
    Tobias Buschor

    Can I safely remove "postfix-perl-scripts" or "postfix-sysvinit"?

    Were they installed from a previous Plesk version or Plesk extension?

    I have the problem on two different servers and I don't think I installed them myself.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Tobias Buschor

    No issues should be caused by a workaround in question.

    In case of additional issues, feel free to submit a request for Plesk support: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

     

    0
    Comment actions Permalink
  • Avatar
    Hüseyin Şevki TOPUZ

    1. Connect via SSH

    2. Run "yum remove postfix-sysvinit"

    3. Run "plesk installer"

    this solved my problem on centos 7

    0
    Comment actions Permalink
  • Avatar
    Yaroslav Tarasov

    Hello @Hüseyin Şevki TOPUZ,

    Thank you for sharing the solution! Hope it will be helpful for others.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles