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

New PLESK 7.5.3 Migration Manager Problems

B

bdobson

Guest
Brand new installation of 7.5.3 on FreeBSD 5.3 and attempting to migrate some sites over from 5.0.5 machines. It stops and within the logfile I see this following message:

[13:51:33 26.07.2005 | pid 1772]:3; readResponse|handle 1|(15) data[Semicolon $
String found where operator expected at - line 22, near "ie
"PleskX""
(Missing semicolon on previous line?)
Scalar found where operator expected at - line 24, near "$name"
(Missing semicolon on previous line?)
Semicolon seems to be missing at - line 24.
String found where operator expected at - line 32, near "7.1.5""
(Might be a runaway multi-line "" string starting on line 31)
(Missing semicolon on previous line?)
Scalar found where operator expected at - line 34, near "$notes"
(Missing semicolon on previous line?)
Semicolon seems to be missing at - line 34.
syntax error at - line 5, near "synopsis:"
syntax error at - line 22, near "ie
"PleskX""
"no" not allowed in expression at - line 53, at end of line
"use" not allowed in expression at - line 58, at end of line
syntax error at - line 66, near "Cgp
sub
checkCgp
"
Execution of - aborted due to compilation errors.
]
 
Originally posted by bdobson
Brand new installation of 7.5.3 on FreeBSD 5.3 and attempting to migrate some sites over from 5.0.5 machines. It stops and within the logfile I see this following message:

It was already discussed on the forum somewhere. Support said 'sudo' migration is broken and you have to use root account for migration.
 
Thanks. I have since found that, you also need to make another correction. How on earth does this kind of thing slip past QA?
 
Back
Top