[SOLVED] Some asistance in understanding mysql status

plisken · 01-14-2021, 03:00 AM

I have the following example for running service mysql status and would appreciate some feedback on exactly what I am seeing.
I've recently brought this system back up after a failure and things not quite happening as they should, so my limited investigation is leading me to believe there is a database issue.

Firstly, service mysql status

Code:

service mysql status
● mysql.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql)
   Active: active (running) since Tue 2021-01-12 16:16:36 GMT; 1 day 16h ago
  Process: 7366 ExecStop=/etc/init.d/mysql stop (code=exited, status=1/FAILURE)
  Process: 7500 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/mysql.service
           ├─2102 /bin/sh /usr/bin/mysqld_safe
           └─2169 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/lib/mysql/dlm05u.err --pid-file=/var/lib/mysql/dlm05u.pid

Jan 12 16:16:36 dlm05u mysql[7500]: /etc/init.d/mysql: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz ... (warning).
Jan 12 16:16:36 dlm05u mysql[7500]: Starting MySQL database server: mysqld already running.
Jan 12 16:16:36 dlm05u systemd[1]: Started LSB: Start and stop the mysql database server daemon.

Next up, service mysql_master status

Code:

service mysql_master status
● mysql_master.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql_master)
   Active: active (exited) since Tue 2021-01-12 16:16:44 GMT; 1 day 16h ago
  Process: 7428 ExecStop=/etc/init.d/mysql_master stop (code=exited, status=1/FAILURE)
  Process: 7568 ExecStart=/etc/init.d/mysql_master start (code=exited, status=0/SUCCESS)

Jan 12 16:16:44 dlm05u mysql_master[7568]: Starting MySQL database server: mysqld already running.
Jan 12 16:16:44 dlm05u mysql_master[7568]: [61B blob data]
Jan 12 16:16:44 dlm05u mysql_master[7568]: error: 'Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)'
Jan 12 16:16:44 dlm05u systemd[1]: Started LSB: Start and stop the mysql database server daemon.

Finally, service mysql_slave status

Code:

service mysql_slave status
● mysql_slave.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql_slave)
   Active: failed (Result: exit-code) since Tue 2021-01-12 15:53:14 GMT; 1 day 16h ago
  Process: 6379 ExecStart=/etc/init.d/mysql_slave start (code=exited, status=1/FAILURE)

Jan 12 15:53:00 dlm05u mysqld[6842]: 210112 15:53:00 [Note] Plugin 'InnoDB' is disabled.
Jan 12 15:53:00 dlm05u mysqld[6842]: 210112 15:53:00 [Note] Plugin 'FEDERATED' is disabled.
Jan 12 15:53:00 dlm05u mysqld[6842]: 210112 15:53:00 [ERROR] Unknown/unsupported storage engine: InnoDB
Jan 12 15:53:00 dlm05u mysqld[6842]: 210112 15:53:00 [ERROR] Aborting
Jan 12 15:53:00 dlm05u mysqld[6842]:
Jan 12 15:53:00 dlm05u mysqld[6842]: 210112 15:53:00 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 12 15:53:14 dlm05u mysql_slave[6379]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
Jan 12 15:53:14 dlm05u systemd[1]: mysql_slave.service: control process exited, code=exited status=1
Jan 12 15:53:14 dlm05u systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jan 12 15:53:14 dlm05u systemd[1]: Unit mysql_slave.service entered failed state.

Master should be running on 3307 with slave on 3306 I belive.

Thanks in advance...

berndbausch · 01-14-2021, 05:55 AM

The config file /etc/mysql/my.cnf can't be read. I'd fix that first before looking at any other errors.

plisken · 01-14-2021, 07:00 AM

Quote:

Originally Posted by berndbausch

The config file /etc/mysql/my.cnf can't be read. I'd fix that first before looking at any other errors.

That was misleading, apologies, yes that file has never existed as far as I am aware and indeed into only mysql_master and mysql_slave that should be started and running on 3307 and 3306 respectively.

plisken · 01-20-2021, 01:50 AM

An update and a bit of closure to this...

I was unable to resolve or fully understand these errors, so opted instead to start the instances using mysqld_multi which meant I modified both the my_master.cnf and my_slave.cnf files but interestingly, I also had to comment out the skip_innodb option in the configuration files, after which, I was able to bring both instances up as expected.

This really does puzzle me though as this system had been running for a number of years, without any changes to configuration files etc, but time is short, so moving on.

mysqld_multi simplified things for me somewhat.