• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

SQL Migration Issues

J

Jericon

Guest
I am migrating from a Plesk 8.0.0 Installation on a Fedora Core 2 with MySQL 4.1.18 to a Plesk 8.0.0 installation on Fedora Core 4 with MySQL 4.1.19.

None of my databases are transfering over. Each and every database is giving me the following error (obviously with the different database name and information):

Failed deployment of database mysqlec085f3d723281ebb62120b3631 (domain jericon.net)

Execution of /usr/local/psa/admin/sbin/cid_unpacker /usr/local/psa/PMM/var/2006-06-13-18.04.20.30896 failed with return code 1.
Stdin is
db

Does anyone have any ideas why this is happening and how to resolve it?
 
Originally posted by Jericon
I am migrating from a Plesk 8.0.0 Installation on a Fedora Core 2 with MySQL 4.1.18 to a Plesk 8.0.0 installation on Fedora Core 4 with MySQL 4.1.19.

None of my databases are transfering over. Each and every database is giving me the following error (obviously with the different database name and information):
Click to expand...

There should be more information in logs (somewhere in /usr/local/psa/PMM/var), but logs are deleted when you press 'finish' on the migration page, so you have to stay on it :(
 
You must log in or register to reply here.

Similar threads

Azurel
Issue Plesk Migrator returned non-zero exit code
Replies
6
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
F
Issue postalias fatal: open database virtual.lmdb: No such file or directory (Plesk 18.0.81.2, Ubuntu 26.04) - related to PPPM-15128?
Replies
10
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
N
Issue Migration: mdb.c assertion failed with Plesk 18.0.76
Replies
12
Views
8K
Boni
B
F
Resolved Amavis virus scanning silently disabled - bypass_virus_checks fallback due to missing SQL column (Plesk 18.0.81.2)
Replies
2
Views
2K
Fabian
F
AmaZili Communication
Resolved Upgrade to 18.0.75 Integrity constraint violation: 1062 Duplicate entry 'localhost-database\_-user' for key 'PRIMARY':
2
Replies
34
Views
14K
Hangover2
Hangover2
Back
Top