• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Migration Error: from Obsidian 18.0.34 Update #2 to Obsidian 18.0.66

srib

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
18.0.66
Hi

When I run the migration tool on 18.0.66 server, I get the following error:

Preparing migration
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.

Running the same SQL on the source server against "psa" database is giving me an empty set. Can someone guide me on the possible next steps?

-Sri
 
Just needed to ensure the migration needs to be done as "root" user and not any other user. Thanks to the support for pointing this out and the migration went fine afterwards.

-Sri
 
Hello! Please verify that root password is correct by connecting to source server directly via SSH.

Also, it's possible that root login is not permitted on the source server. You can configure it in SSH config:

1. Open SSHD config on source server:
Code:
vi /etc/ssh/sshd_config

2. Set the PermitRootLogin and PasswordAuthentication settings to 'yes'
Code:
PermitRootLogin yes
PasswordAuthentication yes

3. Save the changes and close the file

4. Restart SSH service:
Code:
service sshd restart

5. Restart migration
 
Back
Top