Applicable to:
- Plesk Onyx 17.8 for Linux
- Plesk Onyx 17.8 for Windows
Symptoms
-
The following error appears when clicking on Domains button in the Plesk UI or logging in to Plesk:
PLESK_ERROR: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'rnameType' in 'field list', query was: select id, name, displayName, email, status, syncRecords, syncSoa, type, ttl, ttl_unit, refresh, refresh_unit, retry, retry_unit, expire, expire_unit, minimum, minimum_unit, serial, serial_format, external_id, rnameType from dns_zone where id=47
Or:
The following error occurs while migrating or restoring a backup on Plesk Onyx 17.8:
PLESK_ERROR: Element 'dns-zone', attribute 'rnameType': The attribute 'rnameType' is not allowed.
-
The following is shown when "plesk repair db -n" is run:
CONFIG_TEXT: Checking the structure of the Plesk database
Column rnameType is absent in the table dns_zone .................. [ERROR] -
Plesk Onyx 17.8 #MU 22 is installed.
-
There is no
/usr/local/psa/bootstrapper/pp17.8.11-bootstrapper/migrations/17.8.11/2017-12-09-00-00-01_add_rname_type_to_dns_zone.php
file:# ls -l /usr/local/psa/bootstrapper/pp17.8.11-bootstrapper/migrations/17.8.11/2017-12-09-00-00-01_add_rname_type_to_dns_zone.php
ls: cannot access /usr/local/psa/bootstrapper/pp17.8.11-bootstrapper/migrations/17.8.11/2017-12-09-00-00-01_add_rname_type_to_dns_zone.php: No such file or directory -
Unable to retrieve the DNS records using CLI:
# plesk bin dns --info example.net
DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'rnameType' in 'field list', query was: select `id`, `name`, `displayName`, `email`, `status`, `syncRecords`, `syncSoa`, `type`, `ttl`, `ttl_unit`, `refresh`, `refresh_unit`, `retry`, `retry_unit`, `expire`, `expire_unit`, `minimum`, `minimum_unit`, `serial`, `serial_format`, `external_id`, `rnameType` from `dns_zone` where `id`=1 exit status 1
Cause
During the micro-update, database scheme migration was not performed correctly.
This is Plesk bug with ID PPPM-9351, which is planned to be fixed in one of the future product updates.
Resolution
As a workaround, re-initialize the database scheme migration.
-
Log into the server via SSH.
-
Execute the following command via the command line
# plesk installer update
In case it did not help, use the repair utility to adjust the database:
# plesk repair db
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database
Column rnameType is absent in the table dns_zone .................. [ERROR]
Repair table 'dns_zone'? [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.20180924-110248.dump.gz
Repairing table 'dns_zone' ...................................... [FIXED]
-
Log into the server via RDP.
-
Start a command prompt as an Administrator and run the repair utility to fix the database:
C:\> plesk repair db
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database
Column rnameType is absent in the table dns_zone .................. [ERROR]
Repair table 'dns_zone'? [Y/n] y
Creating a database dump ........................................ [OK]
Repairing table 'dns_zone' ...................................... [FIXED]
Comments
4 comments
running plesk installer update on both WINDOWS machines fixes the issue
'plesk repair db' did not fix the problem for our server (Linux), running the installer again did fix the problem. This bug seems to occur inconsequently, can this be addressed?
Hi,
If the issue still occurs for you every once in a while on some servers, please submit a request to us in order to investigate it: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-
Work for me
Please sign in to leave a comment.