• 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

Reset the Migraiton Manager? It's stuck!

michaellunsford

Regular Pleskian
something unexpected happened during a migration attempt, and now when I visit the migration manager page, it doesn't give me the usual list, or any options. Instead it gives the following errors:

ERROR: PleskPMMResponseException
Failed to find status element

0: PMMResponseTaskStatus.php:400
PMMResponseTaskStatus->__construct(object of type StreamXMLReader)
1: PMMResponseTaskStatus.php:272
PMMResponseStatusMixed->__construct(object of type StreamXMLReader)
2: PMMResponseTaskStatus.php:392
PMMResponseTaskStatus->__construct(object of type StreamXMLReader)
3: PMMResponseTaskList.php:85
PMMTask->__construct(object of type StreamXMLReader)
4: PMMResponseTaskList.php:197
PMMResponseTaskList->getNextTask()
5: MigrationCurrentTasksList.php:57
MigrationCurrentTasksList->fetchMigrationCurrentTasksList()
6: class.cList.php3:99
cList->fetchList()
7: class.cList.php3:118
cList->init()
8: server.migration.php:57
plesk__server__migration->accessTasksList(string 'GET', NULL null)
9: server.migration.php:44
plesk__server__migration->accessItem(string 'GET', NULL null)
10: UIPointer.php:596
UIPointer->access(string 'GET')
11: plesk.php:38

I've rebooted the server a few times without success. Is there a way to reset the Migration Manager so I can try again?
 
Hello,

Please, check the following file if there are any timeout limits that could cause the issue (small limits), and try to increase them:

/etc/my.cnf

Thank you
 
no dice

I updated a few 500k entries with 2m, but still nothing.

[mysqld]
set-variable=local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1

skip-bdb

set-variable = innodb_buffer_pool_size=2M
set-variable = innodb_additional_mem_pool_size=2M
set-variable = innodb_log_buffer_size=2M
set-variable = innodb_thread_concurrency=2
[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
skip-bdb

set-variable = innodb_buffer_pool_size=2M
set-variable = innodb_additional_mem_pool_size=2M
set-variable = innodb_log_buffer_size=2M
set-variable = innodb_thread_concurrency=2
 
Server management company punted - the re-imaged the machine, which seems to be functioning normally (sort of). I posted a new problem in a separate thread.
 
Back
Top