Issue Backup Manager - Error: no such table: tasks

[adamgp]

Hi, within a subscription, i'm trying to click into the "Backup Manager" to alter some pre-existing backup settings.. however, since upgrading from version 11.5 to 12 Plesk is now giving the red error message "Error: no such table: tasks".

I have compared the database folder structure of the psa schema to another version 12 Plesk install I have, which (apart from mis-positioned columns) is identical, no missing tables or columns etc. And "psa.tasks" does not exist. Yet on this other server I can enter the Backup Manager and set up FTP details, etc.

I cannot find any reference to this precise error online or in this forum, does anyone have any ideas?!

I suspect "tasks" does not reference to a database table and may mean something else...

Thanks

 

[IgorG]

Have you tried to fix it with

# plesk repair installation
# plesk repair db

?

 

[adamgp]

I have now, I cant see anything out of place personally.

I ran the DB repair a couple of times as some minor issues where found (as seen in the logs below) - mainly missing indicies and redundant tables for dropping.
I ran these commands on my other server with Plesk which seemed to report similar issues (especially with regards to kavehost not starting). However afterwards again the Backup Manager still gave the same error message when trying to click the link.


Furthermore, I dont know if it was on the home page of Plesk before but a warning box has come up saying "For security reasons, we recommend that you protect data contained in backups. Please go to Backup Settings and update backup security settings."
However, when viewing these Backup Settings and clicking save, the same red error box reads "Error: no such table: tasks" on the home page!


The contents of the two .log files at the bottom of the output seem to contain the identical information in the below output from the command so there's not much more to go on.



[root@server0-0-0-0 ~]# plesk repair db

Checking the Plesk database using the native database server tools .. [OK]

Checking the structure of the Plesk database

Extra table: Components ........................................... [WARNING]
Delete table 'Components'? [Y/n] Y
Creating a database dump ........................................ [OK]
A dump of the database was created before an attempt to repair the database: /var/lib/psa/dumps/mysql.preresolve.20160718-150344.dump.gz
Deleting table 'Components' ..................................... [FIXED]

Extra table: NewsArticles ......................................... [WARNING]
Delete table 'NewsArticles'? [Y/n] Y
Deleting table 'NewsArticles' ................................... [FIXED]

Missing index in the table domains: ............................... [WARNING]
- permissions_id (permissions_id)
Repair table 'domains'? [Y/n] Y
Repairing table 'domains' ....................................... [FIXED]

Wrong attributes for the column 'same_ssl' in the table 'hosting': [ERROR]
- The attribute 'default' value mismatch: true in the original
schema and false in the Plesk database.
Repair table 'hosting'? [Y/n] Y
Repairing table 'hosting' ....................................... [FIXED]

Wrong attributes for the column 'same_ssl' in the table
'subdomains': ..................................................... [ERROR]
- The attribute 'default' value mismatch: true in the original
schema and false in the Plesk database.
Repair table 'subdomains'? [Y/n] Y
Repairing table 'subdomains' .................................... [FIXED]

Missing unique key in the table Subscriptions: .................... [WARNING]
- uuid (uuid)
Repair table 'Subscriptions'? [Y/n] Y
Repairing table 'Subscriptions' ................................. [FIXED]

Missing index in the table Templates: ............................. [WARNING]
- note_id (note_id)
Repair table 'Templates'? [Y/n] Y
Repairing table 'Templates' ..................................... [FIXED]

Extra index in the table WordpressInstances: ...................... [WARNING]
- subscriptionId (subscriptionId)
Repair table 'WordpressInstances'? [Y/n] Y
Repairing table 'WordpressInstances' ............................ [FIXED]

Checking the consistency of the Plesk database

Inconsistency in the table 'smb_users' for the column
subscriptionDomainId: No rows in the table 'domains' with id = 4 .. [WARNING]
To see more details, run the command in the verbose mode: plesk repair db -ver
Fix broken references in the table 'smb_users'? [Y/n] Y
Fixing broken references ........................................ [FIXED]

Error messages: 2; Warnings: 7; Errors resolved: 9

[root@server0-0-0-0 ~]# plesk repair db

Checking the Plesk database using the native database server tools .. [OK]

Checking the structure of the Plesk database ........................ [OK]

Checking the consistency of the Plesk database ...................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

[root@server0-0-0-0 ~]# plesk repair installation

Reconfiguring the Plesk installation

Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
Stopping sw_engine service... done

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mysqld... mysqld (pid 3320) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 012005030
Version is OK, no need to create psa database.
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.12.5.30-12.5.30.20160718-150558.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.12.5.30-12.5.30.20160718-150608.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
ERROR 1045 (28000): Access denied for user 'billing'@'localhost' (using password: YES)
Trying to reset database user password for 'billing@'... done
Trying to reset database user password for 'pma_Ca7fxpNfP2kV@localhost'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
Trying to resolve hostname 'server0-0-0-0.live-servers.net' and validate its IP address... done

Trying to reset database user password for 'pp_sb_db@server0-0-0-0'... done
Trying to reset database user password for 'billing@localhost'... done
Trying to reset database user password for 'horde@localhost'... done
Trying to reset database user password for 'atmail@localhost'... done
Trying to reset database user password for 'pma_Ca7fxpNfP2kV@localhost'... done

Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: root@%.
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.

===> Plesk database was not upgraded completely. See installation log for details.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp12.5.30-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
rndc: connect failed: 127.0.0.1#953: connection refused
Reconfiguring mail subsystem...
Reconfiguring Apache web server...
[Mon Jul 18 15:07:46 2016] [warn] module ssl_module is already loaded, skipping
Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
Reconfiguring AWStats web statistics...
Reconfiguring WatchDog...
Restoring SELinux contexts...
INFO: [Mon Jul 18 15:08:06 BST 2016]: Serice: kavehost, Action: start
Trying to start service kavehost... kavehost is not running.
Starting kavehost: [FAILED]

WARNING!
Some problems are found during start service kavehost(see log file: /var/log/plesk/rc_actions.log)

Continue...

Reconfiguring SSL ciphers and protocols...
Regenerating web servers' configuration files...
Cleaning active Panel sessions...

Bootstrapper repair finished.
Errors occurred while performing the following actions: cumulative Plesk upgrade and repair revertible stage.
Check '/var/log/plesk/install/plesk_12.5.30_repair.log' and '/var/log/plesk/install/plesk_12.5.30_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Parallels support.
***** problem report *****
Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: root@%.
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.

exit status 1

 

[Lloyd_mcse]

Have you looked at this kb article...

https://kb.plesk.com/en/127983

Regards

Lloyd

 

[adamgp]

Thank you Lloyd, there were no old versions of MySQL to uninstall. I did however make an effort to convert all non 41 character length MySQL passwords to their newer encrypted counterparts (which were variations of the root user @'localhost', @'%').
But this has made little difference to the error at hand. The "plesk repair installation" command Igor suggested has stopped complaining about the old passwords now.

What could it possibly mean when the error states "no such table: tasks" - does it mean a database table or some meta table in the Plesk application itself?

Is there a plesk event log file that would divulge more detailed information laying on the server somewhere?

Thank you