Facebook
Twitter
-
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
Issue mariadb version on phpmyadmin is old version why?
- Thread starter dj ramc
- Start date
Good question. For sure phpMyAdmin is using exactly the active version of the database server. There can be several reasons why it is displaying a different version number.
I'd check this first:
# plesk db
and see what this says as version information. If it still uses the "old" version, then the database server needs to be restarted. In one occasion I had to restart the whole system, because MariaDB just would not close a running process to reload its updated libraries on "service mariadb restart". So it could very well be that you have upgraded the libraries, but they are not yet used.
Then check a simple browser page "reload", too, on the phpMyAdmin page. Maybe you are not seeing the actual page, but a cache copy that your browser had previously saved.
I'd check this first:
# plesk db
and see what this says as version information. If it still uses the "old" version, then the database server needs to be restarted. In one occasion I had to restart the whole system, because MariaDB just would not close a running process to reload its updated libraries on "service mariadb restart". So it could very well be that you have upgraded the libraries, but they are not yet used.
Then check a simple browser page "reload", too, on the phpMyAdmin page. Maybe you are not seeing the actual page, but a cache copy that your browser had previously saved.
So restarting the process failed. This is the reason why you are still seeing the old process. The underlying cause in this situation normally is that a database process cannot be stopped. Normally you need to first stop the database service with the official command that fits your OS, like
# service mariadb stop
Then verify that it has stopped (it probably has not)
# ps aux | grep mariadb
# ps aux | grep mysql
If it did not stop, check the logs for the cause. Normally, the solution will be to kill the processes manually and then restart the database server. But check the /var/log/messages log on the MariaDB details first. Normally, MariaDB errors are very verbose, so by looking at the error messages closely and maybe researching for major keywords of them in the plesk knowledge base you will find the proper solution.
# service mariadb stop
Then verify that it has stopped (it probably has not)
# ps aux | grep mariadb
# ps aux | grep mysql
If it did not stop, check the logs for the cause. Normally, the solution will be to kill the processes manually and then restart the database server. But check the /var/log/messages log on the MariaDB details first. Normally, MariaDB errors are very verbose, so by looking at the error messages closely and maybe researching for major keywords of them in the plesk knowledge base you will find the proper solution.
Similar threads
- Sticky
