• 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

plesk - mysql - table issue

cpartassides

New Pleskian
centos plesk 10.3.1
------------------------------------------------
adding into my.cnf LOWER_CASE_TABLE_NAMES = 1 which is necessary for my applications work which use mix case SQL queries produced the following error on plesk access.
------------------------------------------------
ERROR: PleskMainDBException
MySQL query failed: Table 'psa.skins' doesn't exist

0: common_func.php3:200
db_query(string 'select `id`,`name`,`place` from Skins where `id`=1')
1: Table.php:154
Table->select()
2: Skin.php:120
Skin->__construct(integer '1')
3: common_func.php3:3262
objectMaker(string 'Skin', integer '1', boolean false, NULL null)
4: common_func.php3:3271
objectMakerEx(string 'Skin', integer '1')
5: Skin.php:588
Skin::initSkin()
6: auth.php3:513
------------------------------------------------
switching back LOWER_CASE_TABLE_NAMES = 0 or removing the entry reverses the issue


Anyone with ideas ?
 
There a lot of system tables with uppercase names in psa database and I think it is not good idea to do something with LOWER_CASE_TABLE_NAMES option.

mysql> show tables;
+-------------------------------+
| Tables_in_psa |
+-------------------------------+
| APSApplicationItems |
| APSCatalogUpdates |
| APSClientApplicationItems |
| APSLicenseTypes |
| APSLicenses |
| ApiRpcCallsStat |
| BackendCache |
| BackupsScheduled |
| BackupsSettings |
| Cards |
| ClientsTraffic |
| Components |
| Configurations |
| DashboardPreset |
| DashboardPresetConfig |
| DatabaseServers |
| DomainServices |
| DomainsTraffic |
| GL_remote_domains |
| GL_settings |
| IP_Addresses |
| IpAddressesCollections |
| IpCollections |
| Limits |
| Logos |
| MailLists |
| MailMessagesStat |
| Modules |
| Notes |
| Notifications |
| PMM |
| PMMDefault |
| Parameters |
| Permissions |
| PersistentCache |
| PlanItemProperties |
| PlanItems |
| PlansSubscriptions |
| PleskPagesStat |
| Repository |
| SBConfig |
| SBResellers |
| SBSites |
| SSOBranding |
| SiteAppFiles |
| SiteAppPackages |
| SiteAppResources |
| SiteApps |
| SiteAppsHitsStat |
| SitePagesStat |
| Skins |
| SubscriptionProperties |
| Subscriptions |
| Templates |
| TmplData |
| WebApps |
| Webmails |
| accounts |
| actions |
| ai_vendor_sources |
| anon_ftp |
| apsContexts |
| apsContextsApplications |
| apsResources |
| apsResourcesParameters |
| apscategories |
| badmailfrom |
| certificates |
| cl_param |
| clients |
| cp_access |
| custom_buttons |
| data_bases |
| db_users |
| disk_usage |
| dns_recs |
| dns_recs_t |
| dns_zone |
| dom_level_usrs |
| dom_param |
| domainaliases |
| domains |
| event_handlers |
| exp_event |
| externalWebmails |
 
I always thought that plesk panel uses its own http server and db for some reason .

Switching from windows to linux did seem as easy as i thought !!!

C.
 
Yes, Plesk admin's interface uses own sw-cp-server (modified lighttpd) and own psa database. But when you modify /etc/my.cnf file it affects all databases on MySQL server - system Plesk databases and customer databases.
 
Back
Top