• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Mysql Version different to DBA Admin Error

toomanylogins

Basic Pleskian
Hello, Just ran the up on update for 12.5.30 to update mysql to 5.5.52 due to the latest vulnerability. Plesk is showing the version as

localhost (default for MySQL) 3306 5.5.50

but if you go into DBA Admin link

Server version: 5.5.52-0ubuntu0.12.04.1 - (Ubuntu)

so it looks like an incorrect version is being displayed by Plesk. This is with.

12.5.30 Update #48, last updated at Sept 26, 2016 10:19 AM

I just tried the same update on a second plesk server ubuntu 14.04 with same result the plesk mysql version displayed is the old version pre plesk update in this case 5.5.47 but phpmyadamin

Server version: 5.5.52-0ubuntu0.14.04.1 - (Ubuntu)

regards
Paul
 
Last edited:
Try to Refresh Server Components in Tools&Settings and check versions after that.
Note, we do not ship mysql for Ubuntu. Version from OS repository is using for Ubuntu OS.
 
Thanks Igor,

Iif you refresh components the version in list is correct
mysql5.5.52-0ubuntu0.12.04.1
If you go to Tools settings/Database servers version displayed is 5.5.50 so looks like a bug on this page.
 
Yes, there is some kind of caching information issue. As possible workaround, you can just click on database server in Tools settings/Database servers and cache with correct name will be updated.
 
Back
Top