• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Deployer already running?

S

SnefIT

Guest
Hi,

When migrating i get this error:

"Unable to start Deployer because there is another Deployer run". It know it was some bug in 9.2, workaround was rebooting.

Rebooting isn't an option on this time of day, is there another way (killing an process or something like that?)

S.
 
Seems that I have to reboot after every migration.... Can take some time to do so :(

Well... the problems gets bigger! Now I even get the error after a reboot, so importing is not possible!

What can be done????

Please?
 
Last edited by a moderator:
Igor,

As you could have read, the problem still exists after a reboot!

But, I solved it myself. When the error occurs, just clean the dirs (backup if you want them later):
%plesk%/PMM/msessions
%plesk%/PMM/rsessions
%plesk%/PMM/tasks

Now the PMM has no tasks left, so there is no other deployer run.

If it still give the error, clean the dirs and reboot.

( it doesn't migrate everything)
 
NVM.. I deleted them at destination server. great tip.

Btw, also do a

ps ax|grep -i deployer

and if you see anything there, kill it.. like with killall deployer

Plesk's migration tool is so fragile! :(
 
Back
Top