• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Can't restore backup: Perhaps /usr/local/psa/admin/bin/deployer application missing

ShoneA

Basic Pleskian
Error received when attempting to restore a backup:

Perhaps /usr/local/psa/admin/bin/deployer application missing, has incorrect permissions or unexpectedly terminated

Panel version 11.5.30 Update #20, last updated at Oct 24, 2013 01:28 AM

openSUSE 12.3 (x86_64)
VERSION = 12.3
CODENAME = Dartmouth
NAME=openSUSE
VERSION="12.3 (Dartmouth)"
VERSION_ID="12.3"
PRETTY_NAME="openSUSE 12.3 (Dartmouth) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:eek:pensuse:eek:pensuse:12.3"
 
Have you checked that file /usr/local/psa/admin/bin/deployer is really there?

# ls -la /usr/local/psa/admin/bin/deployer
lrwxrwxrwx 1 root root 15 Oct 29 04:35 /usr/local/psa/admin/bin/deployer -> ../sbin/wrapper

This file is a part of plesk-service-node-utilities package. Make sure that this package is correctly installed and not corrupted.
 
Yes it exists:

plesk:~ # ls -la /usr/local/psa/admin/bin/deployer
lrwxrwxrwx 1 root root 15 Sep 26 20:53 /usr/local/psa/admin/bin/deployer -> ../sbin/wrapper
 
i have the same problem when i do migration :

Error :
Perhaps /usr/local/psa/admin/bin/deployer application missing, has incorrect permissions or unexpectedly terminated

Some others informations for log migration :

migration_handler.log
[2013-11-11 01:44:57.423|21156] WARNING: Session data value file '/usr/local/psa/PMM/msessions/201311110142030/last_time' does not exist
[2013-11-11 01:44:57.425|21156] DEBUG: Executing asynchronously [22332] process
[2013-11-11 01:44:57.425|21156] DEBUG: <migration_handler.MigrationStartAction object at 0x7f5439a1db10>: response
[2013-11-11 01:44:57.426|21156] INFO: Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>0</errcode>
</response>

pmmcli.log
[2013-11-11 01:44:27.022|21303] ERROR: Could not get value from '/usr/local/psa/PMM/rsessions/20131111014427527/repository_url'.
[2013-11-11 01:44:27.022|21303] ERROR: Could not get value from '/usr/local/psa/PMM/rsessions/20131111014427527/repository_login'.
[2013-11-11 01:44:27.023|21303] ERROR: Could not get value from '/usr/local/psa/PMM/rsessions/20131111014427527/repository_pwd'.
....
[2013-11-11 01:44:27.025|21303] ERROR: Could not get value from '/usr/local/psa/PMM/rsessions/20131111014427527/delete_dump'.
.....
[2013-11-11 01:44:27.032|21303] ERROR: Could not get value from '/usr/local/psa/PMM/rsessions/20131111014427527/storage_type'.
[2013-11-11 01:44:27.032|21303] DEBUG: <pmmcli.RestoreAction object at 0xae5d10>: response
[2013-11-11 01:44:27.033|21303] INFO: Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>0</errcode>
<data>
<task-id>21259</task-id>
</data>
</response>

Have you solution ?
 
I have the same problem with Plesk 11.5.30 migration manager.
But in my case I can fix it by restarting the server before i start the migration. After the server restart everything works fine.
If I do a migration a few days later I have to reboot the server again.

Maybe this can help you too
 
Back
Top