|
I am dealing with a mystery either caused by <bad memory> or a--
complete system shutdown and restart....
Here is the issue. I have relocated my IBM i to a new co-lo which
meant it was shut down, traveled across state lines and came up just
fine about 5 days later. It took a while to get all of the firewall
and access established and although the websites hosted on the i are
running, my WordPress sites threw database errors a la "Error
establishing a database connection". I had been starting mariadb from
SSH with this command: /QOpenSys/usr/bin/sh
/usr/local/mariadb/bin/mysql.sh start Which runs just fine. Except
that didn't solve the connection error. So, from SSH I attempted to
log in to Mariadb directly and get "ERROR 2002 (HY000): Can't connect
to local server through socket '/QOpenSys/var/lib/mysql/mysql.sock'
(2)" which is very weird since my SQL tool, Navicat, CAN open the
databases and they appear to be up to date.
So, I checked the DB connections in the WordPress instances and noted
that they were connecting though port 3307. Navicat was connecting
though port 3306. Starting MariaDB with the command above, I see this
in the logs:
2025-05-13 20:53:14 1 [Note] /usr/local/mariadb/bin/mysqld: ready for
connections.
Version: '10.1.21-MariaDB' socket:
'/usr/local/mariadbdata/mariadb.sock' port: 3306 Source distribution
So it seems like all is well, except the port doesn't match what is
configured in the WP instances. It *should* be 3307 and I know I
didn't change it. So I headed over to "Open Source Package
Management" to check to see what was installed. Package manager says
10.6.12-3 is installed, which doesn't match what I see in the logs.
Taking a look at the installed files for the package, I see a
/QOpenSys/var/lib/mariadb/data folder and in that folder are the
folders containing my DB files.
So, finally, the question: Since I only recall using the mysql start
command above, how was the "other" instance of MariaDB running and how
do I find out how to start it? I remember upgrading MariaDB but I
don't recall running any command to start that instance, but I have
slept many nights since that upgrade....
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.