• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Migration error Failed to execute SQL query on Plesk database: failed to parse JSON returned by SQL

netq

New Pleskian
Hey guys, hi;

I am migrating plesk from one Ubuntu 14.04 (Source) server to another Ubuntu 16.04 (Target) server

the source did not have root access so follow the procedure at Resolved - migration error

It is also important to note that our Origin server is running MariaDB Ver 5.5.59 and our target server is running MySQL Server 5.7.21.

and he throws the following mistake:

Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Failed to execute SQL query on Plesk database: failed to parse JSON returned by SQL script.
Query:
SELECT Subscriptions.id as subscription_id, clients.id, login, pname
FROM clients
LEFT JOIN Subscriptions ON
Subscriptions.object_id = clients.id
AND Subscriptions.object_type = 'client'
WHERE clients.type = 'reseller'

Command's exit code: 255
Command's stdout:
Command's stderr: Died at AgentConfig.pm line 23.

That is a critical error, migration was stopped.


we run plesk db command in our source server (which is running maria) and the query output the right result, displaying correctly the information, we whish know if the issue could be motived by the root permission or some trouble between sql servers...

Thank you see you later
 
Back
Top