Any Known Issues With Installing PhpMyAdmin with mariadb or mysql?
 

A few days ago, the installation of PhpMyAdmin "blew-up" my installation of mariabd. Whether PhpMyAdmin was the actual cause or not, I do not know.

What made this particularly irritating is that simply uninstalling PhpMyAdmin did not make the mariadb accessible again. Simply uninstalling and reinstalling mariadb did not work either.

Now, after carefully following some installation tutorials, I have finally gotten back to the point where mariadb, php, and apache2 appear to be behaving correctly. Before attempting the final step of installing PhpMyAdmin with the possibility that it might "blow-up" again; does anyone know of any compatibility issues between PhpMyAdmin and mariadb before I take this final step over the cliff?

For now, I will be using the terminal/command line.

------------------------------------------

Mint 19.2
mariadb version: 10.1.41
php version: 7.3.8
apache2: 2.4.29

With this last round, I limited my package installation, (to the extent possible) to the packages found on the Mint repository.

It's on my VPS at my hosting provider, but I use phpMyAdmin with MySQL several times a week and have done so for years. Before that, when I had shared hosting, again, no issues. Before that, when I self-hosted (years ago), no issues.

I've had no problems with phpmysql. Note that the version selected needs to match both the version of php and the version of mysql/mariadb being run, as I recall.

Pay careful attention to those dependencies...

I can't offer you anything to prevent you falling over the edge. The only thing I will say is, if it does "blow-up" again then don't rush into starting over. Attempt to troubleshoot the problem, the cause of the "blow up". The primary method of doing this will be looking at logs for errors. Post back here to seek guidance and answers to questions on how to do that troubleshooting.

You'll probably find it's only a pothole, not a cliff.

Now that I have had some time to think about this; my drive has plenty of space so I will create a new partition and install a new install of Mint I will focus on simply getting mariadb, apache2, php, and phpmyadmin working. We will be out-of-town for a few days, so it will be a while.

The last time that I installed mysql and phpmyadmin was approximately six years ago. No issues. I then "dropped in" mariadb to replace mysql. Again no issues. Anyway my computer was getting a bit aged so I bought a new one.

Thanks for responding. That more or less confirms that I made a mistake somewhere along the installation process.

Partial success. I created a (temporary) test platform and I was able to get PhpMyAdmin to work with mariadb.

However, when I attempted it on my main partition, the installation of PhpMyAdmin failed. Even though it failed, my ability to log into my mariadb still works.

So I will still be plugging away at it. Finally got a useful error message: "Version check failed. Got the following error when calling the 'mysql' command line". So far have not located a post with this issue and how to fix.

As a quickie solution, I purged mariadb and reloaded it. But that did no solve the problem. Is there another place in Linux were an official version number is kept?

Re-Installed Mint 19.2 to Resoolve PhpMyAdmin Installation
 

Success. I decided to deploy the nuclear option and made a new install of Mint19.2. My initial install was "fresh" in the sense that I was installing it on a new computer. Much still remains, but none of what is left to be installed presented any problems with the prior install. Nevertheless, it will be a slow tedious process.

I found this website to have one of the better tutorials: Install phpMyadmin, Apache2 and PHP 7.3 on Ubuntu. Many of the websites that I ran across for making this installation are now a bit dated.

A minor footnote point: The following text: "Include /etc/phpmyadmin/apache.conf" needs to be included in the file: "/etc/apache2/apache2.conf", otherwise PhpMyAdmin does not show-up under "localhost/phpadmin".

The Version check failed because the script that does the sanity/verification checks does not know the root user password. To be honest I thought those scripts used a user other than root. Perhaps I'm wrong. However, I imagine you've changed the root password for the DB (as you should), but not updated the scripts configuration. I would disable that script so that I don't need to write the password down.

The third line. What upgrade is that? Potentially that is why phpMyAdmin is struggling.

It would've been useful to see the phpMyAdmin logs.

It's all irrelevant now, anyway.

Thanks very much for your response.