• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Auto Migration from 7.1.x and 7.5.x

R

RalphW

Guest
We currently have one license for Plesk 7 Unlimited Domains (the other license is owned by company who owns server). We're interested in migrating all the site's we're hosting on the Plesk 7 servers to the Plesk 9 server. We can upgrade the license to Plesk 9, but if we do that the Plesk 7 licenses will become inactive. If we don't do that we're unable to test migration of new domains to the new host. I don't want to buy a $1500 license that I don't need. Is there a grace period after license upgrade that you can use both licenses and if so how long?

Any suggestions on how to move forward and any specific issues to watch out for coming from Plesk 7.1/7.5 -> 9 would be greatly appreciated.

Regards,

Ralph
 
I can suggest you request trial Plek 9 license from your sales representative and perform migration. After that you can upgrade your current Plesk 7 license to 9 version.
 
Thanks for the idea, it sounds like a good one, any pitfalls to watch out for during the upgrade?
 
Thanks for the idea, it sounds like a good one, any pitfalls to watch out for during the upgrade?

If you mean license upgrade that it would be better contact your sales representative regarding this question :)
 
No, i was refering more to general migration from the technical side fo things.

Case in point, my migrations are failing ~170 domains, ~20 accounts. It gets about 8m in and just gives status failed with no logs what so ever. Anyone have any ideas?
 
Migration logs you can find in /usr/local/psa/PMM/logs directory.
 
Migrations

I'm getting this result, which doesn't make a whole lot of sense.

<?xml version="1.0"?>
<execution-result status="error"><message code="InternalDtdValidationFailed" severity="error"><context>void plesk::validateSchema(plesk::tXmlDocument&amp;, const std::string&amp;)</context><file>./xml_parse.cpp</file><line>412</line><text>Failed validation of the document with its internal DTD. The errors are: Element 'spamassassin', attribute 'action': [facet 'enumeration'] The value 'del' is not an element of the set {'delete', 'mark'}.Element 'spamassassin', attribute 'action': 'del' is not a valid value of the local atomic type..</text></message></execution-result>
 
That did help as did disabling spamassassin on the originating host, but now I'm getting this and the entire migration fails...

31875: 2009-12-16 06:50:02,848 INFO Subprocess raised ExecuteException: Subprocess <subprocess[31877] '/usr/local/psa/admin/bin/launchpad --dump-selected --host=xxx --login=root --session-path=/usr/local/psa/PMM/msessions/2009121606450867 --selected-objects-file=/usr/local/psa/PMM/msessions/2009121606450867/selected_objects --agent-name=PleskX --agent-dir=/migration/2009121606450867/'> was finished with exit code 2
== STDOUT ====================

== STDERR ====================
Error during dump retrieval
31875: 2009-12-16 06:50:02,849 DEBUG Backup status saved to session
31875: 2009-12-16 06:50:02,852 CRITICAL Runtime error in migration handler:
subproc.NonzeroExitException was finished with exit code 2
Traceback (most recent call last):
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1394, in main
data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1294, in migration_start
return MigrationHandlerActionRunner(MigrationStartAction, None, migration_session_id).doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 88, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 864, in doActivity
service.backup(migration_session.getValue('agent_name'), migration_session.getValue('agent_dir'))
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service.py", line 95, in backup
res = self.backupImpl(agent_name, agent_dir)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service_impl.py", line 62, in backupImpl
self.runCmdLine(cmd)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service.py", line 51, in runCmdLine
self.session.runWorker(cmd)
File "/usr/local/psa/admin/share/migration-handler/migration_handler_session.py", line 290, in runWorker
cmd.spawn()
File "/usr/local/psa/admin/lib/python/subproc.py", line 240, in spawn
self.proc.run()
File "/usr/local/psa/admin/lib/python/subproc.py", line 185, in run
BaseSubprocess.run(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 169, in run
self.wait()
File "/usr/local/psa/admin/lib/python/subproc.py", line 193, in wait
BaseSubprocess.wait(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 179, in wait
raise NonzeroExitException(self, self.__retcode)
NonzeroExitException: was finished with exit code 2

31875: 2009-12-16 06:50:02,853 INFO Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1001</errcode>
<errmsg>Runtime error in migration handler:
subproc.NonzeroExitException was finished with exit code 2
Traceback (most recent call last):
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1394, in main
data_action_response, errcode_response, error_message = actions.get(sys.argv[1][2:])(parameters)
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 1294, in migration_start
return MigrationHandlerActionRunner(MigrationStartAction, None, migration_session_id).doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 88, in doActivity
result = self.processor.doActivity()
File "/usr/local/psa/admin/share/migration-handler/migration_handler.py", line 864, in doActivity
service.backup(migration_session.getValue('agent_name'), migration_session.getValue('agent_dir'))
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service.py", line 95, in backup
res = self.backupImpl(agent_name, agent_dir)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service_impl.py", line 62, in backupImpl
self.runCmdLine(cmd)
File "/usr/local/psa/admin/share/migration-handler/pmm_migr_remote_service.py", line 51, in runCmdLine
self.session.runWorker(cmd)
File "/usr/local/psa/admin/share/migration-handler/migration_handler_session.py", line 290, in runWorker
cmd.spawn()
File "/usr/local/psa/admin/lib/python/subproc.py", line 240, in spawn
self.proc.run()
File "/usr/local/psa/admin/lib/python/subproc.py", line 185, in run
BaseSubprocess.run(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 169, in run
self.wait()
File "/usr/local/psa/admin/lib/python/subproc.py", line 193, in wait
BaseSubprocess.wait(self)
File "/usr/local/psa/admin/lib/python/subproc.py", line 179, in wait
raise NonzeroExitException(self, self.__retcode)
NonzeroExitException: was finished with exit code 2
</errmsg>
</response>
 
Not sure that it will help, but try to reinstall psa-migration-manager package and contact support team if it not help because this complex problem require deep investigation directly on server.
 
Back
Top