How to upgrade Plesk to the next release

Follow

Comments

26 comments

  • Avatar
    Alessandro Marengo

    What can I do if there's no update available?

    2
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Alessandro Marengo

    Hello!
    Could you specify which version is currently installed?

    Generally, please try to start Plesk Installer with the parameter --all-versions, for example:

    "%plesk_bin%"\ai.exe --console --all-versions

    0
    Comment actions Permalink
  • Avatar
    Alessandro Marengo

    Thanks Ivan for your reply.

    What if, instead of using command line, I'd like to use Plesk Updates option?

    0
    Comment actions Permalink
  • Avatar
    Alexandr Tumanov

    @Alessandro, this option is available only in CLI version of Plesk installer. If you cannot see the desired version for the upgrade, it may mean that your OS does not meet all requirements. 

    0
    Comment actions Permalink
  • Avatar
    adrian TNT

    Running /usr/local/psa/admin/bin/autoinstaller says that it should only be ran on clean install servers and that I should backup my data, so I am not sure I should proceed:

    ------ IMPORTANT ------

    * New installation of product(s) should be performed on clean servers only.

    * Before upgrading Plesk, be sure to back up your data.

    * By using this Wizard you agree to the terms and conditions described at
    http://www.plesk.com/legal/terms/ and those of the Plesk End User
    License Agreement.

    Available actions:
    (F) Go forward
    (Q) Cancel installation

    Select an action [F/q]: q
    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hi @adrianTNT!

    In case you are updating Plesk, the warning about clean server may be ignored, this is for new installations only.

    As for backup, it is a general recommendation in case the update will fail (usually the process goes fine). You may make a server snapshot or backup Plesk domains.

     

    0
    Comment actions Permalink
  • Avatar
    Michael (Edited )

    Hi, I'm running Plesk Onyx on CentOS 7. "Install and Upgrade Product" is grayed out. In the "Update and Upgrade Settings", I have General Release  selected. Is that the issue potentially? Thanks. - Ignore this got it running, how can I tell if the upgrade is stuck. Been running for 2 hours now still on 45/17something.

    0
    Comment actions Permalink
  • Avatar
    Maxim Krasikov

    Hello @Michael,

    Please check the last records in /var/log/plesk/install/autoinstaller3.log. If the file is not updated then the upgrade is stuck.
    In this case please kill the existing installer process using the article:
    https://support.plesk.com/hc/en-us/articles/213917525
    After that, run Plesk upgrade using the command line:
    # plesk installer

    The solution regarding grayed out Install or Upgrade Product option is described below:
    https://support.plesk.com/hc/en-us/articles/213914005

    If you still face issues with Plesk upgrade, please contact support directly:
    https://support.plesk.com/hc/en-us/requests/new

    0
    Comment actions Permalink
  • Avatar
    Rainer Kraft

    Plesk Onyx 17.8.11 on Centos7

    Installation of 18.0.20 via web installer is not possible. Last error in the line of errors is: postfix3 meets postfix-2... 

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @Rainer Kraft

    Looks like dependency issue with postfix package, please contact support directly:
    https://support.plesk.com/hc/en-us/requests/new

    0
    Comment actions Permalink
  • Avatar
    Rainer Kraft

    @Lev lurev

     

    That's not possible, 'cause I got Plesk from my Provider and it is not possible to get any more help, than this forum. Here are some lines from the log:

       Package 2:postfix-2.10.1-7.el7.x86_64 already installed and latest version
       PyYAML-3.10-11.el7.x86_64.rpm | 153 kB 00:00
       libyaml-0.1.4-11.el7_0.x86_64.rpm | 55 kB 00:00
       dejavu-sans-mono-fonts-2.33-6.el7.noarch.rpm | 433 kB 00:00
       rrdtool-perl-1.4.8-9.el7.x86_64.rpm | 42 kB 00:00
       rrdtool-1.4.8-9.el7.x86_64.rpm | 440 kB 00:00
       postfix3-3.4.7-1.gf.el7.x86_64.rpm 0.0 B/s | 3.1 MB 00:00 postfix3-3.4.7-1.gf.el7.x86_64.rpm | 3.1 MB 00:04

       Fatal error during packages installation:
       Test Transaction Errors: file /usr/libexec/postfix/local from install of postfix3-2:3.4.7-1.gf.el7.x86_64 conflicts with file from package postfix-2:2.10.1-7.el7.x86_64

    If I search for postfix-2, there is no result on the server

       Warnung: Keine Übereinstimmung gefunden für: postfix-2.10.1-7.el7.x86_64

    Perhaps it points someone in the right direction. I stopped the update for now.

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Anzhelika Khapaknysh

    Hi @Rainer Kraft,

    It's hard to provide you with exact steps without taking a look at the issue.

    As the license you own was purchased from our partner, you can buy a support subscription and contact Plesk Support Team directly.
    Check this article for details: https://support.plesk.com/hc/en-us/articles/213953025-How-to-get-support-directly-from-Plesk- 

    First 30 days are free of charge.

    0
    Comment actions Permalink
  • Avatar
    Claudio

    > Note: Make sure that port 8447 is opened in firewall. If it is closed and cannot be opened, use the command-line instructions.

    Can you please elaborate if the mentioned port 8447 is for outgoing (from Plesk to Internet) or incoming (from Internet to Plesk) connections? Or even both directions?

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @Claudio incomming

    0
    Comment actions Permalink
  • Avatar
    Scott Saccenti

    Plesk hung on an update from 18.0.20-->18.0.21. Appears update was incomplete.

    Server working fine, but no longer able to access Plesk control panel.

    Error log indicates plesksrvstartuphandler.exe failed with error code 255, failed opening required "Loader.php."

    When I examine the relevant folder (Plesk\admin\plib), it looks like the files in that folder are incomplete. The files there all show a date modified that matches the time of the upgrade, but the files are all alphabetically "A" through "E" and stop abruptly at "E". It appears any files "F" through "Z" are missing (including the indicated "Loader.php."

    It seems the upgrade was interrupted and now I have a problem.

    Attempts to reinstall the upgrade through command line seem successfull "you already have the latest version of the product and selected components installed, installation will not continue."

    But not able to launch Plesk control panel :(

    0
    Comment actions Permalink
  • Avatar
    Anzhelika Khapaknysh

    @Scott Saccenti,

    it's hard to propose a solution on the fly, as such issues require direct investigation on the server.
    Thus, I'd recommend contacting our Technical Support Team for assistance.

    0
    Comment actions Permalink
  • Avatar
    Scott Saccenti

    I have Plesk through a GoDaddy VSP, so I don't think your Tech Team will support me.

    So I have to support myself. Got it fixed, running the following from a command prompt (admin):

    C:\>plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

    This managed to rebuild the corrupted folder that I correctly described above (when I check it now, files exist from "A" to "Z."

    Hopefully this helps the next poor sob.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Scott Saccenti,

    Thank you for sharing your experience. Indeed, this may help other Pleskians.

    0
    Comment actions Permalink
  • Avatar
    Ahmed Abderraman

    I decided to try and upgrade from Onyx to Obsidian (0.21) today. It took like 3 hours, with most of the time systemd (init -z) using 100% of the cpu. During these hours I couldn't access the control panel. Also the update log showed the following error message like 100 times: "Failed to list unit files: Connection timed out".

    4 cores server with 4GB of RAM and SSD disk running Ubuntu 18.04.

    One of the worst experiences I've had with a control panel.

    Also apparently now my server is running Grafana for some reason. Like really, I have to run Grafana for a control panel. Is Plesk becoming the new Gitlab, where you will need a NASA computer to run it fast?

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello,

    3 hour is not normal for the upgrade, please create a support ticket to check why it took so long.

    Graphana is a part of Advanced Monitoring extension added in Obsidian, if you don't want to run it you may remove it under Extensions catalog.

    0
    Comment actions Permalink
  • Avatar
    Enrique Ruiz Millan (Edited )

    Hello 

    I have made an update to Plesk Obsidian and I have the following error:

    ERROR while trying to check the hostname
    Bootstrapper has finished action (exec time: 1 sec.): Parent_name = 'panel', sequence = 'prep', stage = 'execute', sequence_order = '0', operation = 'install', exec_cmd = '/ opt / psa /bootstrapper/pp18.0.25-bootstrapper/bootstrapper.sh prep-install BASE '', m_arch = '', output:
    **** Product prep-install started.
    Create user 'psaadm' and group 'psaadm'
     Group 'psaadm' already exists
     Checking for the user 'psaadm' ...
     User 'psaadm' already exists
    Create group swkey-data
     Group 'swkey-data' already exists
     Trying to add supplementary group 'swkey-data' for user 'psaadm' ... already there
     Trying to got legacy variables ... done
     Trying to save legacy variables ... done
     Trying to resolve hostname 'sample.com' and validate its IP address ...
    Can not bind a socket to address sample.com:715 - Cannot assign requested address
    Please check your network configuration

    ERROR while trying to check the hostname

    ***** problem report *****
    ERROR while trying to check the hostname

    [2020-03-26 09: 50: 10.384716] Bootstrapper has finished action (exec time: 0 sec.): Parent_name = 'PLESK_18_0_25', sequence = 'prep', stage = 'rollback', sequence_order = '1', operation = 'install', exec_cmd = 'rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; rm -f /var/lock/parallels-panel-upgrade-failure.flag; : '', m_arch = '', output: ~ empty

    I have changed the real domain to "sample.com".

    On the other hand, I have applied this KB: https://support.plesk.com/hc/en-us/articles/213941265-How-to-change-or-get-the-server-hostname-on-Plesk-server

    But I continue with the problem. Can you help me?

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Maxim Krasikov

    Hi @Enrique Ruiz Millan,

    Please apply the resolution steps from the article:

    https://support.plesk.com/hc/en-us/articles/213396889-Plesk-upgrade-or-update-fails-ERROR-while-trying-to-check-the-hostname

    If you face any further issues, please contact Plesk technical support for assistance:
    https://support.plesk.com/hc/en-us/requests/new 

    0
    Comment actions Permalink
  • Hello, Please help me.

    I cannot upgrade Plesk 12.5.30 to Plesk 17.8.11.

    I encountered an error, that I could not solve.

     

    Please help me to solve this problem, and help guide me to successfully upgrade Plesk 12.5.30 to Plesk 17.8.11.

     

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @มงคล รอดศรี

     

    Please create a ticket to our support department.

    0
    Comment actions Permalink
  • Avatar
    Arnaud DEBRINCAT

    Je ne peux pas mettre mon plesk à jour de la version 17.8.11 vers 18.0.3 , il me met cet erreur :

     

    Errors were encountered while processing:
     docker-ce
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    et arrête le processus.
    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Arnaud DEBRINCAT

    As I can see, you've contacted Plesk support and it was found that the issue was caused by the Docker process failing to start.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request