• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue mariadb version on phpmyadmin is old version why?

dj ramc

Basic Pleskian
Hi

i've just installed latest version of mariadb via packages upgrade by plesk. ( 10.2.31)
when i run on shell
Code:
mysql -V
it shows
mysql Ver 15.1 Distrib 10.2.31-MariaDB, for Linux (x86_64) using readline 5.1

but when i start phpmyadmin via plesk its shows
Serverversie: 10.2.25-MariaDB - MariaDB Server

how could i push phpmyadmin to use latest version of mariadb ?

thanks you
 
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.
 
[root@ns1 httpdocs]# systemctl status mariadb.service
● mariadb.service - MariaDB 10.2.31 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Sat 2020-02-01 14:12:48 CET; 16s ago
Docs: man:mysqld(8)
systemd
Process: 33304 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 33258 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 33255 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 33304 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

Feb 01 14:12:17 ns1.***.**mysqld[33304]: 2020-02-01 14:12:17 1405876....
Feb 01 14:12:17 ns1.***.**mysqld[33304]: 2020-02-01 14:12:17 1405876....
Feb 01 14:12:17 ns1.***.**mysqld[33304]: 2020-02-01 14:12:17 1405876...s
Feb 01 14:12:48 ns1.***.**mysqld[33304]: 2020-02-01 14:12:48 1405876...'
Feb 01 14:12:48 ns1.***.**mysqld[33304]: 2020-02-01 14:12:48 1405876....
Feb 01 14:12:48 ns1.***.**mysqld[33304]: 2020-02-01 14:12:48 1405876....
Feb 01 14:12:48 ns1.***.**systemd[1]: mariadb.service: main process ...E
Feb 01 14:12:48 ns1.***.**systemd[1]: Failed to start MariaDB 10.2.3....
Feb 01 14:12:48 ns1.***.**systemd[1]: Unit mariadb.service entered f....
Feb 01 14:12:48 ns1.***.**systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
 
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.
 
thank you so much
i've founded by ps aux | grep mysql and kill the process manually and started again mariadb.
now its running on latest version
 
Back
Top