• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

GoDaddy's Fedora Plesk systems will not migrate!

D

dave5b03

Guest
GoDaddy has required all their customers to upgrade to Fedora 7 by March 15.

However, the GoDaddy Plesk systems will not migrate! I have tried to migrate both Fedora 2/Plesk 7.5.3 and Fedora 6/Plesk 8.2 to Fedora 7/Plesk 8.3 with no success.

I get the same error regardless of which version I try to migrate:

Failed to execute scout.
The return code is 9
The output on STDERR is
"use" not allowed in expression at - line 4, at end of line
syntax error at - line 4, near "<mypasswd>
#!/usr/bin/perl

use strict"
BEGIN not safe after errors--compilation aborted at - line 16.

On one of the systems I ran ./scout and got the following result:

[root@www PMM]# ./scout.pl
<?xml version="1.0"?><scout-result><detected-panel agent="PleskX" name="Plesk 8.2.0 FedoraCore 6 82070706.15"/><os-info os="Lin ux" loadavg="0.08 0.02 0.01"/><remote-fs><fs mountpoint="/" device="/dev/vzfs" mode="rw" size="10737418240" free="10011987968" type="reiserfs"/></remote-fs></scout-result>

Who is responsible for this error? I think it is reasonable to expect that a system provisioned with Fedora and Plesk to migrate Plesk when you pust the Plesk "migrate button".

Is this a SWSoft Plesk migration programming error or is it a GoDaddy provisioning error?
 
I think I have answered my own questions; the error messages were confusing.

The problem appears to be SWSoft documentation indicates the source host /etc/sudoers file should contain 'user ALL=(ALL) NOPASSWD: ALL'.

That does not work on the GoDaddy servers, you require 'user ALL=(ALL) ALL'.
 
Back
Top