• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Dash in DB name causes plesk exception when viewing full resource statistics

Mshaker

Basic Pleskian
OS: centos 5 x64
Plesk version: 9.5.2 CentOS 5 95100504.10

When you create a database containing the '-' character it creates the database as expected however on disk the database directory path '-' gets created as '@002d'.

Eg. create database name called example-database
Database name: example-database
On disk: /var/lib/mysql/example@002ddatabase/

After the database is created you can no longer view the domains "Full Summary" report as it now throws a "PleskUtilException"

get_dir_size: Error: unable to get dir size for /var/lib/mysql/example-database

System error 2: No such file or directory

0: DatabaseManagerMySQL.php:284
DatabaseManagerMySQL->getDatabaseSizeImpl(string 'example-database', resource)
1: DatabaseManager.php:323
DatabaseManager->getDatabaseSize(object of type Database)
2: class.DomainReport.php:673
DomainReport->make_report_full_databases_()
3: class.Report.php:277
Report->make_report(integer '61')
4: ReportUIPointer.php:40
ReportUIPointer->accessItem(string 'POST', NULL null)
5: UIPointer.php:596
UIPointer->access(string 'POST')
6: plesk.php:38

Just a note that dumping the database and recreating it without the '-' will fix the exception.
 
Right, it is known issue. I hope it will be fixed soon. Now we can recommend you do not use any special symbols for database names.
 
Hi,

We have experienced this problem in version 9.5.3 CentOS 5 95101022.06 - do you know when this will finally be resolved?

Thanks
 
Back
Top