Failed to install or upgrade Plesk Migrator: Error occurred during /bin/cp command

Follow

Comments

14 comments

  • Avatar
    John Keegan (Edited )

    The solution from the article did solve my issue, actually Alexey. Just wanted to backup @Alex Ortmanns point that this is still happening. ;)

    0
    Comment actions Permalink
  • Avatar
    John Keegan

    I just experienced this on a fresh install of CloudLinux 7.6 and latest Plesk so it's still out there...

    0
    Comment actions Permalink
  • Avatar
    Alisa Kasyanova

    @Alex Ortmanns

    Thank you for the report. I have inspected it and discussed the issue with developers. A bug PMT-3777 is dealing with Plesk Migrator installation issues on CloudLinux. It will be fixed in one of the next Plesk versions, please follow the article to receive a notification as soon as the fix becomes available. I have edited the article accordingly. Thank you for your collaboration!

    0
    Comment actions Permalink
  • Avatar
    Alex Ortmanns

    Hi,

    It was a fresh installation of Cloudlinux 7.6

    The issue occured during ./plesk-installer wizard, I tried it 3 times and it always happened. I installed Plesk for the 4th time without the Migrator and installation succeeded. When trying the installation afterwards through updates & upgrades the same message appeared and I was able to fix it according to the kb article.

    0
    Comment actions Permalink
  • Avatar
    Alex Ortmanns

    Also happened here on a fresh install today.

    0
    Comment actions Permalink
  • Avatar
    Lev Iurev

    @John Keegan

    Thank you for clarification. We will update the article once the issue is fixed.

    0
    Comment actions Permalink
  • Avatar
    Alexey Lapshin

    Hello, @John

    If the solution from the article does not help, please submit a ticket for us, https://support.plesk.com/hc/en-us/requests/new and we will investigate this issue further.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Alex,

    May I also know additional details to reproduce the issue?

    Was Plesk 17.8 installed? What OS was used?

    Was it installed the same way as @Christopher did?

    Thank you in advance.

    0
    Comment actions Permalink
  • Avatar
    Alex Ortmanns

    I don't know if it's still useful but here you go! I'm surprised you are unable to reproduce it given that it was so persistent.

    TR-PLSK-40863

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Christopher,

    Thank you for the feedback.

    The issue was not reproduced in a test environment, the same command was used to install Plesk.

    Is the issue reproducible on your servers every time or do you have the exact steps to reproduce such behavior? 

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Christopher,

    Thank you for letting us know.

    The article will be updated as soon as we will figure out additional details.

    0
    Comment actions Permalink
  • Avatar
    Christopher Scott

    Hi @Ivan,

    I'm sorry I don't initialise new servers very often, and don't have any plans to do so in the near future, so I can't say if this happens every time.  Hopefully @Alex can shed some more light on it.

    0
    Comment actions Permalink
  • Avatar
    Christopher Scott (Edited )

    This has just happened on a fresh install using Plesk Onyx 17.8 update 38 installed via

    sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)

    on a clean cloudlinux 7.6

     

    The problem is easy to fix using these guidelines, but a little disappointing that after so long this still isn't fixed in your installer. I just wanted to highlight for you that this problem is still occuring on new installs in 17.8 (not just 17.5) as the article says, and so you can fix it for new customers :-)

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hi @Alex,

    Is that possible to get a technical report so we can analyze and find the cause? Still cannot reproduce the same in our labs unfortunately. 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request