• 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.

Plesk 8.1 psa rebuild

S

snookersky

New Pleskian
After successfully upgrade to 8.1, I wanted to restore my databases previously generated with mysqldump. So the old psa database was (erroneous) recreated and the 8.1 one droped. Therefore some fields are missing and errors occures using Plesk administration.

How can I rebuild the 8.1 psa structure (hopefully not from scratch)?

----

ok, I found out howto:
1. install plesk 8.1 from scratch on other machine
2. mysqldump scratch_db
3. EDIT old dumped sql-file, adapting all table structures to new version (they are not too many)
4. source edited sql-file into upgraded DB-server
 
Originally posted by snookersky
After successfully upgrade to 8.1, I wanted to restore my databases previously generated with mysqldump. So the old psa database was (erroneous) recreated and the 8.1 one droped. Therefore some fields are missing and errors occures using Plesk administration.

How can I rebuild the 8.1 psa structure (hopefully not from scratch)?

----

ok, I found out howto:
1. install plesk 8.1 from scratch on other machine
2. mysqldump scratch_db
3. EDIT old dumped sql-file, adapting all table structures to new version (they are not too many)
4. source edited sql-file into upgraded DB-server
Click to expand...

I have the same problem, do you have the scratch_db dump file you did?

Thanks.
 
You must log in or register to reply here.

Similar threads

M
Issue How to repair "plesk repair db"
Replies
4
Views
8K
scsa20
scsa20
M
Resolved Daily log rotation fails: "A table must have a primary key" on statisticsMeasurement, but plesk repair db finds no errors.
Replies
7
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
R
Resolved CVE-2026-42945 Nginx Rift and older Wordpress Toolkit heads up
Replies
14
Views
13K
rhall
R
Matt N
Issue Maria DB 10.11 > 11.4 upgrade results in issues with Plesk Repair Tool - reports innodb corruption in ibdata1
2
Replies
27
Views
21K
Azurel
Azurel
M
Issue Plesk Update 18.0.34 to 18.0.57 Database 'psa' not found
Replies
10
Views
7K
musa.sc
M
Back
Top