Maria / MySQL Fails to Start

OpenSuse Tumbleweed 64 bit

mysqld 10.0.22-MariaDB

systemctl start mysql.d service
Job for mysql.service failed because the control process exited with error code.
See "systemctl  status mysql.service" and "journalctl  -xe" for details.

journalctl  -xe
WARNING: terminal is not fully functional
-  (press RETURN)Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7249]: MySQL didn't start, can't continue
Mar 25 00:38:07 linux-qob4 systemd[1]: **mysql.service: Control process exited, code=exited status=1**
Mar 25 00:38:07 linux-qob4 systemd[1]: **Failed to start MySQL server.**
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--  
-- Unit mysql.service has failed.
--  
-- The result is failed.
Mar 25 00:38:07 linux-qob4 systemd[1]: **mysql.service: Unit entered failed state.**
Mar 25 00:38:07 linux-qob4 systemd[1]: **mysql.service: Failed with result 'exit-code'.**
Mar 25 00:38:07 linux-qob4 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Mar 25 00:38:07 linux-qob4 systemd[1]: Stopped MySQL server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--  
-- Unit mysql.service has finished shutting down.
Mar 25 00:38:07 linux-qob4 systemd[1]: Starting MySQL server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--  
-- Unit mysql.service has begun starting up.
Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7506]: Checking MySQL configuration for obsolete options...
Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7506]: Trying to run upgrade of MySQL databases...
Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7506]: Stale files from previous upgrade detected, cleaned them up
Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7506]: Running protected MySQL...
Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7506]: Waiting for MySQL to start
Mar 25 00:38:07 linux-qob4 mysql-systemd-helper[7506]: 180325  0:38:07 [Note] /usr/sbin/mysqld (mysqld 10.0.22-MariaDB) starting as process 7528 ...

Process continues to attempt restart but fails

/MySQL directory and subfolders and files have correct ownership mysql:mysql

There might be some additional info in

/var/log/mysql/mysqld.log

There is no

/var/log/mysql/mysqld.log

Try:

:~> journalctl --unit=mysql

here is the output from journalctl --unit=mysql

I still do not see anything useful

Mar 11 00:47:02 linux-qob4 systemd[1]: Starting MySQL server...
Mar 11 00:47:02 linux-qob4 mysql-systemd-helper[27653]: Checking MySQL configuration for obsolete options...
Mar 11 00:47:02 linux-qob4 mysql-systemd-helper[27653]: Trying to run upgrade of MySQL databases...
Mar 11 00:47:02 linux-qob4 mysql-systemd-helper[27653]: Running protected MySQL...
Mar 11 00:47:02 linux-qob4 mysql-systemd-helper[27653]: Waiting for MySQL to start
Mar 11 00:47:02 linux-qob4 mysql-systemd-helper[27653]: 180311  0:47:02 [Note] /usr/sbin/mysqld (mysqld 10.0.22-MariaDB) starting as process 27672 ...
Mar 11 00:48:02 linux-qob4 mysql-systemd-helper[27653]: MySQL is still dead
Mar 11 00:48:02 linux-qob4 mysql-systemd-helper[27653]: MySQL didn't start, can't continue
Mar 11 00:48:02 linux-qob4 systemd[1]: **mysql.service: Control process exited, code=exited status=1**
Mar 11 00:48:02 linux-qob4 systemd[1]: **Failed to start MySQL server.**
Mar 11 00:48:02 linux-qob4 systemd[1]: **mysql.service: Unit entered failed state.**
Mar 11 00:48:02 linux-qob4 systemd[1]: **mysql.service: Failed with result 'exit-code'.**
Mar 11 00:48:02 linux-qob4 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Mar 11 00:48:02 linux-qob4 systemd[1]: Stopped MySQL server.
Mar 11 00:48:02 linux-qob4 systemd[1]: Starting MySQL server...


Have you actually configured/installed a database?
What? Where? How?

Yes, I have databases, with users, migrated from my old machine.

MySQL installed from openSuse repositories via Yast.

I have the MySQL database at a custom location set via my.cnf. The directory and all contents have the owner:group mysql:mysql

my /etc/my.cnf

# This is default example of MySQL/MariaDB configuration provided with openSUSE package
# It is based on upstream defaults with some additional examples.




# The following options will be passed to all MariaDB clients
[client]
# password  = your_password
# port       = 3306
# socket     = /var/run/mysql/mysql.sock


[mysqld]


# Remove leading # if you don't want to listen on network (only socket - safer)
# skip-networking


# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M


# Using newer file format that supports dynamic and compressed row formats.
# If you are using replication you have to make sure, that these options are
# set everywhere the same way (probably comment them out is the easiest way)
innodb_file_format=Barracuda
innodb_file_per_table=ON


# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin=mysql-bin
# binlog_format=mixed


# Remove leading # if you want to store your database elsewhere
datadir	= /home/xyz/MySQL


# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id	= 1


# These are commonly set, remove the # and set as required.
# port = 3306
# socket = /var/run/mysql/mysql.sock


# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
# skip-networking


# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M 


sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES


[mysqld_multi]
mysqld     = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin
log        = /var/log/mysqld_multi.log


# If you want to use mysqld_multi uncomment 1 or more mysqld sections
# below or add your own ones.


# WARNING
# --------
# If you uncomment mysqld1 than make absolutely sure, that database mysql,
# configured above, is not started.  This may result in corrupted data!
#
# [mysqld1]
# port       = 3306
# datadir    = /var/lib/mysql
# pid-file   = /var/lib/mysql/mysqld.pid
# socket     = /var/lib/mysql/mysql.sock
# user       = mysql


# [mysqld2]
# port       = 3307
# datadir    = /var/lib/mysql-databases/mysqld2
# pid-file   = /var/lib/mysql-databases/mysqld2/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld2/mysql.sock
# user       = mysql


# [mysqld3]
# port       = 3308
# datadir    = /var/lib/mysql-databases/mysqld3
# pid-file   = /var/lib/mysql-databases/mysqld3/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld3/mysql.sock
# user       = mysql


# [mysqld6]
# port       = 3309
# datadir    = /var/lib/mysql-databases/mysqld6
# pid-file   = /var/lib/mysql-databases/mysqld6/mysql.pid
# socket     = /var/lib/mysql-databases/mysqld6/mysql.sock
# user       = mysql


!includedir /etc/my.cnf.d



Try:

sudo systemctl start mysql

Check that the mysql user can access (navigate to) /home/xyz/MySQLother will need access to /home/xyz. Each database will be in its own directory within MySQL.

Why are the logs two weeks old?

MySQL installed from openSuse repositories via Yast.

I do not understand this. A fully functional MariaDB is installed in Tumbleeweed by default. It is used by e.g. KDE. All I had to do was copy a database folder from a server to /home/testData, point “datadir” to the testData and “systemctl start mysql” to be able to query the database with a “mysql oldDb” command.

Yes, as previously mentioned, and I checked again

/home/xyz/MySQL

has the following owner and group - mysql:mysql

as do all directories and files below it.

the logs from two weeks ago are the same as last night and today, it is still the same problem. I just took the first entries from the log.

Nor, do I understand the problem either, because I have set up and migrated MySQL databases multiple times previously. I also copied the MySQL directory over from the old machine. In the pas this worked also.

I am missing something, hence I am asking for help / suggestions.

I am already issuing the following command to attempt to start MySQL, as mentioned above, and receiving the uninformative error messages and log entries I have posted.

systemctl start mysql

Based on your original post,
Sounds to me that you have databases you might have tried to “forklift” from another installation (and you said they were from your “old machine”).

If the version of MaridaDB/MySQL is very different from what you were running before, that won’t work.
You need to run the same version of MariaDB/MySQL that was running on your “old machine,” export your databases and import into your newer MariaDB/MySQL, or do an in-place upgrade that’s supposed to upgrade the databases along with the application.

So,
What exactly was this “old machine?”
Does it still exist?

Otherwise…
The only way you can start your MariaDB/MySQL on this TW machine is to do one of the following

  • Remove the database files
  • Configure your MariaDB/MySQL to launch a non-default named instance that won’t use the same database file location
  • Configure your MariaDB/MySQL instance to just use a different database file location.

Of course the options above won’t try to run your existing databases.

TSU

TSU

It is difficult to help if you refuse to show us what you are doing and what happens. Telling us what you intended and posting edited extracts do not allow anyone to spot anything amiss. Most people will just give up guessing from incomplete (withheld) information.

Please:
What exactly do you mean by

MySQL installed from openSuse repositories via Yast.

MariaDB is installed with the “mariadb” package from the Tumbleweed-OSS repository.

/home/xyz/MySQL has the following owner and group - mysql:mysql

Does not tell us whether user mysql can traverse /home/xyz to reach the database. Ownership != permission.

Please show your current version of:

y3:~ # ls -lah /home/rayh/testData
total 109M
drwxr-xr-x 1 mysql users  288 Mar 26 04:03 .
drwxr-xr-x 1 rayh  users 1.6K Mar 25 14:49 ..
-rw-rw---- 1 mysql mysql  16K Mar 26 04:03 aria_log.00000001
-rw-rw---- 1 mysql mysql   52 Mar 26 04:03 aria_log_control
drwxr-xr-x 1 mysql mysql  492 Mar 25 16:14 gmbeDb
-rw-rw---- 1 mysql mysql 2.8K Mar 26 04:03 ib_buffer_pool
-rw-rw---- 1 mysql mysql  48M Mar 26 04:03 ib_logfile0
-rw-rw---- 1 mysql mysql  48M Mar 25 15:41 ib_logfile1
-rw-rw---- 1 mysql mysql  12M Mar 26 04:03 ibdata1
-rw-rw---- 1 mysql mysql    0 Mar 25 15:41 multi-master.info
drwx------ 1 mysql root  2.6K Mar 25 15:41 mysql
-rw------- 1 root  root     4 Mar 25 15:41 mysql_upgrade_info
drwx------ 1 mysql mysql   12 Mar 25 15:41 performance_schema
drwx------ 1 mysql root     0 Mar 25 15:41 test

y3:~ # ls -lah /home/rayh/testData/gmbeDb
total 170M
drwxr-xr-x 1 mysql mysql  492 Mar 25 16:14 .
drwxr-xr-x 1 mysql users  288 Mar 26 04:03 ..
-rw-rw---- 1 mysql mysql  16K Mar 25 16:14 aria_log.00000001
-rw-rw---- 1 mysql mysql   52 Mar 25 16:14 aria_log_control
-rw-rw---- 1 mysql mysql  58M Mar 25 15:41 calls.MAD
-rw-rw---- 1 mysql mysql 4.3M Mar 25 15:41 calls.MAI
-rw-rw---- 1 mysql mysql 8.6K Dec 11  2015 calls.frm
-rw-rw---- 1 mysql mysql 264K Mar 25 15:41 clients.MAD
-rw-rw---- 1 mysql mysql  16K Mar 25 15:41 clients.MAI
-rw-rw---- 1 mysql mysql  11K Nov 22 07:15 clients.frm
-rw-rw---- 1 mysql mysql 2.8K Mar 25 16:14 ib_buffer_pool
-rw-rw---- 1 mysql mysql  48M Mar 25 16:14 ib_logfile0
-rw-rw---- 1 mysql mysql  48M Mar 25 15:57 ib_logfile1
-rw-rw---- 1 mysql mysql  12M Mar 25 16:14 ibdata1
-rw-rw---- 1 mysql mysql    0 Mar 25 15:57 multi-master.info
drwx------ 1 mysql root  2.6K Mar 25 15:57 mysql
-rw------- 1 root  root     4 Mar 25 15:57 mysql_upgrade_info
drwx------ 1 mysql mysql   12 Mar 25 15:57 performance_schema
drwx------ 1 mysql root     0 Mar 25 15:57 test

y3:~ # systemctl start mysql

y3:~ # systemctl status -l mysql
● mariadb.service - MySQL server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset:
   Active: active (running) since Mon 2018-03-26 05:17:02 BST; 25s ago
  Process: 25710 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade (code=exit
  Process: 25699 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install (code=exit
 Main PID: 25721 (mysqld)
   Status: "Taking your SQL requests now..."
    Tasks: 30 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           └─25721 /usr/sbin/mysqld --defaults-file=/etc/my.cnf --user=mysql

Mar 26 05:17:02 y3.scunnert.net systemd[1]: Starting MySQL server...
Mar 26 05:17:02 y3.scunnert.net mysql-systemd-helper[25721]: 2018-03-26  5:17:02 139
Mar 26 05:17:02 y3.scunnert.net systemd[1]: Started MySQL server.

y3:~ # ls -lah /var/log/mysql/
total 24K
drwx------ 1 mysql mysql  152 Mar 26 00:00 .
drwxr-xr-x 1 root  root  1.1K Mar 25 17:51 ..
-rw-rw---- 1 mysql mysql 9.7K Mar 26 05:17 mysqld.log
-rw-rw---- 1 mysql mysql 1.2K Mar 20 20:02 mysqld.log-20180321.xz
-rw-rw---- 1 mysql mysql 1.2K Mar 23 04:06 mysqld.log-20180324.xz
-rw-rw---- 1 mysql mysql 2.1K Mar 25 16:15 mysqld.log-20180326.xz
y3:~ # 

I’ve seen this a couple of years ago, at least that’s what it looks like. A version mismatch between current mariadb and the one from the old machine. Solved it by dumping and importing the databases in a clean mysql setup.

My test db was previously run with mariadb-5.5.46 on OpenSUSE-13.2 and before that with mysql-community-server-5.1.71 on openSUSE-11.4. It originated in 1999. The switch from MyISAM to InnoDB was handled almost seamlessly during a MariaDB version update. When I tried with a really old MySAM db there was a sensible “database not recognised” output, and when the mysql user couldd not traverse th directory tree to the db file it reported “database not found” (those last two messages are approximate and from my less than good memory).

Does your original machine still exist?

TSU

The 1999 SuSE 6.1 server? Alas all that is left is the manual. The oldest (occasionally) running SuSE machine is with 8.1 – and it has the folding pack with 7 CDs and a DVD. There is still an OpenSUSE-11.4 workstation in regular use and next month I am scheduled to upgrade a retired mini server from 11.4 to Leap-15 (as a backup data server).

The problem with running old software is that it does not have drivers for modern hardware and virtual machines do not provide virtualization for old hard drives. I have an old dual Cyrix 686 with two SCSI-2 buses that can run either Ygdrasil (the first “self-installing” live Linux CD) or SCO Unix. It would be great to be able to run Yggdrasil in VirtualBox on a laptop. I suppose it might not be to difficult to rebuild with a newer kernel than 0.99.5.

You can emulate practically every computing device that has ever existed using QEMU.

But,
That may not be absolutely necessary.
I’m asking if the machine from which you pulled your databases from still existed (In last upgraded and running state).
Software is most important here, not the hardware.
Do you know the <exact> version of MariaDB/MySQL you were running with your mounted databases?

If the machine still exists, then it’s likely trivial to export your databases for later re-import.
If the machine doesn’t exist, you still need to know the database application version.

TSU

Ah! a misunderstanding. I am not the OP with the problem.

I did not believe the contents of the OP’s CODE tags, so I grabbed an archived db directory and copied it to my TW laptop. It already had MariaDB installed without me doing anything specific. All I had to do was adjust the datadir and file permissions, then start mysql.service and every thing worked fine. I could open the db with the mysql command and query the data. This InnoDB db came from an in-service MariaDB-5.5.46, but had been converted from MyISAM on a Mysql-Community-Server-5.1.7. No manual conversion was necessary, the db directory was just copied from machine to machine.

This makes me suspect that the OP has done something that has not been disclosed yet. Also if MariaDB cannot access or process the database files it produces a sensible message to that effect. I think that there must be some other reason that the OPs system is not running.

It is difficult to help if you refuse to show us what you are doing and what happens. Telling us what you intended and posting edited extracts do not allow anyone to spot anything amiss. Most people will just give up guessing from incomplete (withheld) information.

@eng-ing far from witholding information, if I am asked for specific information, I will provide it, as follows.

# ll MySQL
total 3421176
drwxr-xr-x 2 mysql     mysql       4096 Jan 31  2014 **amarokdb**
-rwxrwxrwx 1 mysql     mysql    1064960 Mar 27 19:19 aria_log.00000001
-rwxrwxrwx 1 mysql     mysql         52 Mar 27 19:19 aria_log_control
drwxr-xr-x 2 mysql     mysql       4096 Feb 15  2013 **coeff_coeff**
drwxr-xr-x 2 mysql     mysql       4096 Nov 18  2012 **creative_creative**
drwxr-xr-x 2 mysql     mysql       4096 Jan 11 14:05 **digikam5**
-rwxrwxrwx 1 xyz       users        246 Mar 11 00:22 .directory
drwxr-xr-x 2 mysql     mysql      61440 Dec 12  2012 **fvisions_fvisions**
-rwxrwxrwx 1 mysql     mysql       7077 Jan 14 13:58 ib_buffer_pool
-rwxrwxrwx 1 mysql     mysql 2854223872 Jan 14 13:58 ibdata1
-rwxrwxrwx 1 xyz       users  547094528 Jan 26  2015 .ibdata1.fYeplD
-rwxrwxrwx 1 mysql     mysql   50331648 Jan 14 13:58 ib_logfile0
-rwxrwxrwx 1 mysql     mysql   50331648 Jan 14 13:56 ib_logfile1
drwxr-xr-x 2 mysql     mysql       4096 Aug  4  2014 **mor1013510315506**
-rwxrwxrwx 1 mysql     mysql          0 Nov  4  2014 multi-master.info
drwxr-xr-x 2 mysql     mysql       4096 Dec  5 17:29 **mysql**
-rwxrwxrwx 1 mysql     mysql          4 Dec  5 17:29 mysql_upgrade_info
drwxr-xr-x 2 mysql     mysql       4096 Feb  6  2013 **nsl_nsl**
drwxr-xr-x 2 mysql     mysql       4096 Dec  5 17:29 **performance_schema**
drwxr-xr-x 2 mysql     mysql       4096 Jul 21  2014 **phpmyadmin**
-rwxrwxrwx 1 xyz       users          0 Jan 14 15:58 .run-mysql_upgrade
drwxr-xr-x 2 mysql     mysql       4096 Jan  2  2013 **ssrs_ssrs**
drwxr-xr-x 2 mysql     mysql       4096 Jan 20  2013 **test_wordpress


**# ll MySQL/mysql
total 1284
-rwxrwxrwx 1 mysql mysql   2110 Dec  5 17:29 columns_priv.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:28 columns_priv.MYD
-rwxrwxrwx 1 mysql mysql   4096 Dec  5 17:28 columns_priv.MYI
-rwxrwxrwx 1 mysql mysql   2602 Dec  5 17:29 column_stats.frm
-rwxrwxrwx 1 mysql mysql      0 Nov 30 14:57 column_stats.MYD
-rwxrwxrwx 1 mysql mysql   4096 Nov 30 14:57 column_stats.MYI
-rwxrwxrwx 1 mysql mysql   2677 Dec  5 17:29 db.frm
-rwxrwxrwx 1 mysql mysql  10744 Dec 11 00:22 db.MYD
-rwxrwxrwx 1 mysql mysql   9216 Dec 11 00:38 db.MYI
-rwxrwxrwx 1 mysql mysql     59 Apr  5  2016 .directory
-rwxrwxrwx 1 mysql mysql   3695 Dec  5 17:29 event.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:29 event.MYD
-rwxrwxrwx 1 mysql mysql   2048 Dec  5 17:29 event.MYI
-rwxrwxrwx 1 mysql mysql   1582 Dec  5 17:28 func.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:29 func.MYD
-rwxrwxrwx 1 mysql mysql   1024 Dec  5 17:29 func.MYI
-rwxrwxrwx 1 mysql mysql     35 Dec  5 17:29 general_log.CSM
-rwxrwxrwx 1 mysql mysql      0 Jun  9  2012 general_log.CSV
-rwxrwxrwx 1 mysql mysql   8776 Sep 21  2012 general_log.frm
-rwxrwxrwx 1 mysql mysql   1024 Nov  4  2014 gtid_slave_pos.frm
-rwxrwxrwx 1 mysql mysql  98304 Nov  4  2014 gtid_slave_pos.ibd
-rwxrwxrwx 1 mysql mysql   1706 Dec  5 17:29 help_category.frm
-rwxrwxrwx 1 mysql mysql   1072 Sep 22  2015 help_category.MYD
-rwxrwxrwx 1 mysql mysql   3072 Sep 22  2015 help_category.MYI
-rwxrwxrwx 1 mysql mysql   8612 Jun  9  2012 help_keyword.frm
-rwxrwxrwx 1 mysql mysql  89241 Jun  9  2012 help_keyword.MYD
-rwxrwxrwx 1 mysql mysql  16384 Jun  9  2012 help_keyword.MYI
-rwxrwxrwx 1 mysql mysql   8630 Jun  9  2012 help_relation.frm
-rwxrwxrwx 1 mysql mysql   8937 Jun  9  2012 help_relation.MYD
-rwxrwxrwx 1 mysql mysql  18432 Jun  9  2012 help_relation.MYI
-rwxrwxrwx 1 mysql mysql   1776 Dec  5 17:29 help_topic.frm
-rwxrwxrwx 1 mysql mysql 423048 Sep 22  2015 help_topic.MYD
-rwxrwxrwx 1 mysql mysql  16384 Sep 22  2015 help_topic.MYI
-rwxrwxrwx 1 mysql mysql   1897 Dec  5 17:29 host.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:29 host.MYD
-rwxrwxrwx 1 mysql mysql   2048 Dec  5 17:29 host.MYI
-rwxrwxrwx 1 mysql mysql   1629 Nov  4  2014 index_stats.frm
-rwxrwxrwx 1 mysql mysql      0 Nov  4  2014 index_stats.MYD
-rwxrwxrwx 1 mysql mysql   4096 Nov  4  2014 index_stats.MYI
-rwxrwxrwx 1 mysql mysql   4998 Dec  5 17:29 innodb_index_stats.frm
-rwxrwxrwx 1 mysql mysql 196608 Jan 11 14:13 innodb_index_stats.ibd
-rwxrwxrwx 1 mysql mysql   1503 Dec  5 17:29 innodb_table_stats.frm
-rwxrwxrwx 1 mysql mysql  98304 Jan 11 14:12 innodb_table_stats.ibd
-rwxrwxrwx 1 mysql mysql   1518 Dec  5 17:29 plugin.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:29 plugin.MYD
-rwxrwxrwx 1 mysql mysql   1024 Dec  5 17:29 plugin.MYI
-rwxrwxrwx 1 mysql mysql   3418 Dec  5 17:29 proc.frm
-rwxrwxrwx 1 mysql mysql   3504 Dec  5 17:29 proc.MYD
-rwxrwxrwx 1 mysql mysql   4096 Dec  5 17:29 proc.MYI
-rwxrwxrwx 1 mysql mysql   2874 Dec  5 17:29 procs_priv.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:29 procs_priv.MYD
-rwxrwxrwx 1 mysql mysql   4096 Dec  5 17:29 procs_priv.MYI
-rwxrwxrwx 1 mysql mysql   2839 Dec  5 17:29 proxies_priv.frm
-rwxrwxrwx 1 mysql mysql   2538 Feb  5  2017 proxies_priv.MYD
-rwxrwxrwx 1 mysql mysql  10240 Feb  5  2017 proxies_priv.MYI
-rwxrwxrwx 1 mysql mysql   1661 Nov  4  2014 roles_mapping.frm
-rwxrwxrwx 1 mysql mysql      0 Nov  4  2014 roles_mapping.MYD
-rwxrwxrwx 1 mysql mysql   4096 Nov  4  2014 roles_mapping.MYI
-rwxrwxrwx 1 mysql mysql   2703 Dec  5 17:29 servers.frm
-rwxrwxrwx 1 mysql mysql      0 Nov  4  2014 servers.MYD
-rwxrwxrwx 1 mysql mysql   1024 Nov  4  2014 servers.MYI
-rwxrwxrwx 1 mysql mysql     35 Dec  5 17:29 slow_log.CSM
-rwxrwxrwx 1 mysql mysql      0 Nov 30 14:57 slow_log.CSV
-rwxrwxrwx 1 mysql mysql   2374 Dec  5 17:29 slow_log.frm
-rwxrwxrwx 1 mysql mysql   2957 Dec  5 17:29 tables_priv.frm
-rwxrwxrwx 1 mysql mysql      0 Dec  5 17:28 tables_priv.MYD
-rwxrwxrwx 1 mysql mysql   4096 Dec  5 17:28 tables_priv.MYI
-rwxrwxrwx 1 mysql mysql   1374 Nov  4  2014 table_stats.frm
-rwxrwxrwx 1 mysql mysql      0 Nov  4  2014 table_stats.MYD
-rwxrwxrwx 1 mysql mysql   2048 Nov  4  2014 table_stats.MYI
-rwxrwxrwx 1 mysql mysql   8636 Jun  9  2012 time_zone.frm
-rwxrwxrwx 1 mysql mysql   8624 Jun  9  2012 time_zone_leap_second.frm
-rwxrwxrwx 1 mysql mysql      0 Jun  9  2012 time_zone_leap_second.MYD
-rwxrwxrwx 1 mysql mysql   1024 Jun  9  2012 time_zone_leap_second.MYI
-rwxrwxrwx 1 mysql mysql      0 Jun  9  2012 time_zone.MYD
-rwxrwxrwx 1 mysql mysql   1024 Jun  9  2012 time_zone.MYI
-rwxrwxrwx 1 mysql mysql   8606 Jun  9  2012 time_zone_name.frm
-rwxrwxrwx 1 mysql mysql      0 Jun  9  2012 time_zone_name.MYD
-rwxrwxrwx 1 mysql mysql   1024 Jun  9  2012 time_zone_name.MYI
-rwxrwxrwx 1 mysql mysql   8686 Jun  9  2012 time_zone_transition.frm
-rwxrwxrwx 1 mysql mysql      0 Jun  9  2012 time_zone_transition.MYD
-rwxrwxrwx 1 mysql mysql   1024 Jun  9  2012 time_zone_transition.MYI
-rwxrwxrwx 1 mysql mysql   8748 Jun  9  2012 time_zone_transition_type.frm
-rwxrwxrwx 1 mysql mysql      0 Jun  9  2012 time_zone_transition_type.MYD
-rwxrwxrwx 1 mysql mysql   1024 Jun  9  2012 time_zone_transition_type.MYI
-rwxrwxrwx 1 mysql mysql   3191 Dec  5 17:29 user.frm
-rwxrwxrwx 1 mysql mysql   1876 Dec 11 00:22 user.MYD
-rwxrwxrwx 1 mysql mysql   4096 Dec 11 00:38 user.MYI



I followed one of the suggestions and commented out the custom datadir, so that MySQL would start with the default directory. The result is that MySQL started up just fine. So it would appear it is one of the issues suggested, either MySQL cannot traverse the directories, or there is a version mismatch.

I do not know the version on the “old” machine because I can not get it to start up. There are now hardware issues. The “old” machine was running a version of Tumbleweed from January I believe.

If I can provide more information, please be specific as to what you need.

Your help and input is greatly appreciated.

Update

Since I have MySQL running from the default location, I stopped it, I copied one of the database directories over from the custom location and restarted MySQL. Success!

I have repeated the process with a second DB directory and this also works.

I will continue with the remainder. When everything works, I will rename the custom directory, copy the default directory to the custom and see if it starts up.

From what I can see, it is the main MySQL database that is the issue, perhaps it is indeed the compatibility issue after all.