Issue Update error Table 'psa.UserSettings' doesn't exist

[lanopa]

Server operating system version

Debian 11.11

Plesk version and microupdate number

Plesk Obsidian v18.0.67_build1800250117.15 os_Debian 11.0

i have a problem and can't find a solution. wich keyword must i search to get my answere?

i got daily a massage "Das Plesk Update ist fehlgeschlagen"
to me it looks like there is a table missing but what i have to do.

below the error log

Expand/Collapse Block: LOG-File with error

Installation started in background
Checking whether the package dependencies are resolved.
Installing packages
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.67-bootstrapper/migrations/
Migration failed: 18.0.63/2024-06-28-18-35-06_drop_active_list.php
Table 'psa.UserSettings' doesn't exist

**** Product prep-install started.
Create user 'psaadm' and group 'psaadm'
Group 'psaadm' already exists
Checking for the user 'psaadm'...
User 'psaadm' already exists
Create group 'swkey-data'
Group 'swkey-data' already exists
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create group 'psaserv'
Group 'psaserv' already exists
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Create group 'psacln'
Group 'psacln' already exists
Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done
Checking that /opt/psa/bin/chrootsh registered as login shell...

===> Performing safe prep-install database actions


===> Upgrading database

Trying to start service mariadb... active
done
Trying to establish test connection... connected
done
Trying to find Plesk database psa... version is 018000000
Trying to backup MySQL database... done
MySQL databases are dumped to /mnt/backup/backup/mysql.preupgrade.18.0.67-18.0.67.20250212-210921.dump.gz
===> Cumulative APS controller database (apsc) upgrade has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /mnt/backup/backup/mysql.preupgrade.apsc.18.0.67-18.0.67.20250212-210922.dump.gz
===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).
Trying to set psa database version to 018000000... done
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.67-bootstrapper/migrations/
Migration failed: 18.0.63/2024-06-28-18-35-06_drop_active_list.php
Table 'psa.UserSettings' doesn't exist

===> Plesk database scheme was not upgraded completely.

Applying migrations from: /opt/psa/bootstrapper/pp18.0.67-bootstrapper/migrations/
Migration failed: 18.0.63/2024-06-28-18-35-06_drop_active_list.php
Table 'psa.UserSettings' doesn't exist
***** problem report *****
===> Plesk database scheme was not upgraded completely.
Launching component and product checkers...
Downloading file report-update: 0%
Downloading file report-update: 100% was finished.
Downloading file pool/PSA_18.0.67_16338/examiners/py_launcher.sh: 0%
Downloading file pool/PSA_18.0.67_16338/examiners/py_launcher.sh: 100% was finished.
Error: An error occurred during performing of installation PREP actions (see log for details). Installation was rolled back.
Warning! Not all packages were installed.
Please check if your system services are operable.
Please resolve this issue and try to install the packages again.
Visit https://support.plesk.com/ to search for a solution.

 

[Sebahat.hadzhi]

Hello, @lanopa . Please run the following command to check if there any inconsistencies detected with the Plesk database:

plesk repair db -n

If there are, please do:

1. Create a backup of the Plesk database:
   

   plesk db dump psa > /root/psa_dump.sql

2. Run the Plesk database repair utility:
   

   plesk repair db -y

If there are no issues detected, I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket go to:
https://support.plesk.com
If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[Kaspar]

1. Run the Plesk database repair utility:
   plesk repair db -n

Shouldn't that be plesk repair db -y with a -y instead of -n?

 

[lanopa]

after i wrote this and wait 1hr, i didn't find it anymore, so i search aggressivly and find exakt near the same on Plesk Repair Utility

but the Story never end, i didn't can't start plesk ticket so i wrote to my reseller. They didn't would help me. After this thread i wrote again back, today i recieve a message there is a "new thread" exaktly my Problem... they didn't now that is me.

Long story Short end, i use "plesk repair all -v" but it doesn't help, then i use "plesk repair db -v" and now i able to finish the error update prozess.

and yes i know "-n" is only simulation, i didn't do any backup like this way but i got a whole server backup in case.
"-v" sound like as verbose

 

[Sebahat.hadzhi]

Yes, that's right. My bad. Thank you, @Kaspar . Fixed. Glad you were able to sort it out, @lanopa .