• 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!
  • 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.

Resolved Restore stops with "... deployer application missing ... or unexpectedly terminated"

Bitpalast

Plesk addicted!
Plesk Guru
Plesk Onyx 17.5, CentOS 7.3, 64-Bit

On a full restore of admin owned users and admin owned domains from a locally stored backup, after the restore routines have restored approximately 15 users and their subscriptions, all the sudden the restore stops with

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

The knowledgebase articles and other user reports on this did not fit the case. No obvious errors in the log files. Machine is a 12-core system without any other load and has 256 GB RAM + 128 MB swap space. No other transactions like web server restarts or reconfigurations were going on at the same time. No other pmm-processes were in the process list. The deployer library is installed on the system. Single subscription restores were possible.

The error was reproducible on several attempts to restore "full system".

The final solution was to reboot the computer. After the reboot, users and subscriptions could be restored with only some minor, typical issues. The reboot must have cleared something from the processes or RAM that was previously breaking the deployment process of the restore. The exact reason remains unclear.
 
Back
Top