• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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