• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question error notice during the restore procedure

girobot

New Pleskian
Hi, I recently found a problem during the backup restore procedure. I state that I have the updated version of plesk and certainly this is the cause of the problem due to the update.

Code:
Warning: Restore hosting "girobot.eu"
Can not deploy content of domain girobot.eu
Warning:
Archive error: Unable to extract files from /var/lib/psa/dumps/domains/girobot.eu/backup_user-data_1805292352.tgz to /var/www/vhosts/girobot.eu: /usr/lib/plesk-9.0/sw-tar: bin/head: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/vi: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/rmdir: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/wget: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/mkdir: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/gunzip: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/chmod: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/unzip: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/cat: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/curl: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/more: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/groups: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/sh: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/grep: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/rm: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/id: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/less: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/pwd: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/touch: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/mv: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/ln: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/false: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/gzip: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/tar: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/du: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/bash: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/ls: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/cp: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/true: Cannot open: File exists /usr/lib/plesk-9.0/sw-tar: bin/tail: Cannot open: File exists ... (truncated)
 
Last edited:
What is your Plesk version? What is the output of command:

# rpm -qf /usr/lib/plesk-9.0/sw-tar
 
Hi Igor, I tried to issue this command in SSH but it is not recognized "comand not found"
Version: Plesk Onyx 17.8.11
 
Looks like you have Plesk installed on Ubuntu or Debian, because rpm is CentOS package manager.
So, try to fix this issue with commands:

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
# plesk repair installation
 
It seems to have been done correctly, now I will check if the problem has been solved. I'll update you if there are other problems.

Thank you
---------------
Bootstrapper repair finished.

If problems persist, please check installer logs ('/var/log/plesk/install/plesk_17.8.11_repair.log' and '/var/log/plesk/install/plesk_17.8.11_repair_problems.log') for errors.

If you can't resolve the issue on your own, please address Plesk support.
------------

CONFIRM DEBIAN 8
 
I performed a backup to a restore, same problem.
 

Attachments

  • Schermata 2018-05-31 alle 22.41.23.png
    Schermata 2018-05-31 alle 22.41.23.png
    160.9 KB · Views: 9
I think that investigation directly on your server is required. Therefore I strongly recommend you contact Plesk Support Team for investigation and fixing this issue.
 
Back
Top