• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Plesk detected db error but cannot be fixed?

raytracy

Basic Pleskian
I did a plesk repair db -n got the following message:

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

Checking the structure of the Plesk database

Wrong attributes for the column 'time_stamp' in the table
'dns_recs': ....................................................... [ERROR]
- The attribute 'default' value mismatch: CURRENT_TIMESTAMP in
the original schema and current_timestamp() in the Plesk
database.

Wrong attributes for the column 'time_stamp' in the table
'dns_recs_t': ..................................................... [ERROR]
- The attribute 'default' value mismatch: CURRENT_TIMESTAMP in
the original schema and current_timestamp() in the Plesk
database.

Wrong attributes for the column 'event_time' in the table
'exp_event': ...................................................... [ERROR]
- The attribute 'default' value mismatch: CURRENT_TIMESTAMP in
the original schema and current_timestamp() in the Plesk
database.

Wrong attributes for the column 'register_date' in the table
'key_history': .................................................... [ERROR]
- The attribute 'default' value mismatch: CURRENT_TIMESTAMP in
the original schema and current_timestamp() in the Plesk
database.

Wrong attributes for the column 'startTime' in the table
'longtasks': ...................................................... [ERROR]
- The attribute 'default' value mismatch: CURRENT_TIMESTAMP in
the original schema and current_timestamp() in the Plesk
database.

Wrong attributes for the column 'time_resp' in the table
'resp_freq': ...................................................... [ERROR]
- The attribute 'default' value mismatch: CURRENT_TIMESTAMP in
the original schema and current_timestamp() in the Plesk
database.

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

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


I try to fix it, plesk notify me all of them has fixed.
But it show same message in above again when I check it with same command.

It seems happened with all of my CentOS 7.3+Onyx 17.5MU#14.
Does that error matter? and how can I fix it?

By the way, I installed MariaDB 10.1/10.2 as backend for plesk.
 
Try to complete the MySQL upgrade using the following command:

# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -u admin --host localhost --port 3306
 
@raytracy: The errors are shown, because you are using MariaDB 10.2, but Plesk only supports MariaDB 10.1. Version 10.2 works alright, but the db repair tool expects a different content in the fields that are adjusted with current_timestamp(), so it reports errors.

According to Plesk support team there is no fix for it, because MariaDB 10.2 is not officially supported. There is no ETA for supporting it.

We run 10.2 on one installation. Other from that you should disable the strict mode in /etc/my.cnf for your users to stay happy and be able to execute their incomplete group by statements and other misdemeanors of their software you should be fine even with the reported errors.
 
Back
Top