Dev1 Galaxy Forum / mariadb on ceres

Re: mariadb on ceres

dummy@example.com (nixer) — Thu, 20 Oct 2022 14:06:00 +0000

This forum thread is not that old, yet, so I thought I would add to it. I too had this same exact problem and it kept showing up "sometimes" when I had to reboot or restart the mysql service. I finally found what I "think" is a solution. I was having to delete the /var/lib/mysql/ib_logfile0 file to get mysql (mariadb-server) to start. I have been using this for a few weeks on more than one server and have not had any problems, yet. Also, my problem was showing up on chimaera, not ceres.

Steps involved:
- Stop mysql service before editing the file below
- In /etc/mysql/mariadb.conf.d/50-server.cnf file, add this (toward the bottom)

Under this line:

[mariadb]

Add this content:

innodb_fast_shutdown = 0

I hope this helps.

Re: mariadb on ceres

dummy@example.com (chris2be8) — Thu, 25 Aug 2022 16:15:10 +0000

mknoop wrote:

/var/lib/mysql$ stat aria_log_control
File: aria_log_control
Size: 52 Blocks: 8 IO Block: 4096 regular file
Device: 801h/2049d Inode: 404111 Links: 1
Access: (0660/-rw-rw----) Uid: ( 112/ mysql) Gid: ( 120/ mysql)
Access: 2022-08-24 14:52:13.500000000 -0500
Modify: 2022-08-24 14:37:32.160000000 -0500
Change: 2022-08-24 14:37:32.160000000 -0500
Birth: 2020-09-11 16:02:07.848000000 -0500
I do not know how to interpret this.

That says the file is owned by mysql, has group mysql and can be read and written by user mysql and any user in group mysql. Which all looks OK to me.

The last 4 lines of output say when it was last accessed (ie read), modified (written to), had it's directory entry changed and when it was first created.

Unfortunately the man page for stat is not very clear. But running it against a few files with known characteristics it's fairly easy to work out what it means.

As I said I don't run mariadb, so I was just guessing from the first error message in the log extract. So kudos to rbit.

Re: mariadb on ceres

dummy@example.com (mknoop) — Thu, 25 Aug 2022 04:21:59 +0000

That's it!

I did that and tried to start mariadb. That worked, so I did another apt-get upgrade. The server finished installing, stopped, and then started again succesfully.

Thank you very much, rbit.

Re: mariadb on ceres

dummy@example.com (rbit) — Thu, 25 Aug 2022 00:01:36 +0000

These log entries look very similar to an issue I had at the beginning of the year.

mknoop wrote:

Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1651026,1651026
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] InnoDB: Missing FILE_CHECKPOINT at 1651026 between the checkpoint 1651026 and the end 1651038.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] Plugin 'InnoDB' init function returned error.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] Unknown/unsupported storage engine: InnoDB

What fixed it for me was removing (actually, renaming, in case it was needed later; it wasn't) the file /var/lib/mysql/ib_logfile0

cd /var/lib/mysql
mv ib_logfile0 ib_logfile0.bad-renamed
service mariadb start

Re: mariadb on ceres

dummy@example.com (mknoop) — Wed, 24 Aug 2022 19:56:24 +0000

/var/lib/mysql$ stat aria_log_control
File: aria_log_control
Size: 52 Blocks: 8 IO Block: 4096 regular file
Device: 801h/2049d Inode: 404111 Links: 1
Access: (0660/-rw-rw----) Uid: ( 112/ mysql) Gid: ( 120/ mysql)
Access: 2022-08-24 14:52:13.500000000 -0500
Modify: 2022-08-24 14:37:32.160000000 -0500
Change: 2022-08-24 14:37:32.160000000 -0500
Birth: 2020-09-11 16:02:07.848000000 -0500

I do not know how to interpret this.

Re: mariadb on ceres

dummy@example.com (chris2be8) — Wed, 24 Aug 2022 16:48:20 +0000

Does /var/lib/mysql/aria_log_control exist?
Would mysqld be able to write to it? Post output from stat '/var/lib/mysql/aria_log_control' if you are not sure.
Would mysqld be able to write to /var/lib/mysql/ ?

I'm just guessing what to look at, I don't run mariadb myself.

Re: mariadb on ceres

dummy@example.com (mknoop) — Wed, 24 Aug 2022 07:41:03 +0000

I found this in syslog. Does anyone see a clue?

Aug 24 02:19:07 devuan-ceres mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql
Aug 24 02:19:07 devuan-ceres mysqld_safe: Starting mariadbd daemon with databases from /var/lib/mysql
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] /usr/sbin/mariadbd (server 10.6.9-MariaDB-1) starting as process 1443 ...
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] /usr/sbin/mariadbd (server 10.6.9-MariaDB-1) starting as process 1441 ...
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] mariadbd: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Number of pools: 1
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Using generic crc32 instructions
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Using liburing
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Completed initialization of buffer pool
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1651026,1651026
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] InnoDB: Missing FILE_CHECKPOINT at 1651026 between the checkpoint 1651026 and the end 1651038.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] InnoDB: Starting shutdown...
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] Plugin 'InnoDB' init function returned error.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [Note] Plugin 'FEEDBACK' is disabled.
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Aug 24 02:19:07 devuan-ceres mysqld: 2022-08-24 2:19:07 0 [ERROR] Aborting

Re: mariadb on ceres

dummy@example.com (Andre4freedom) — Tue, 23 Aug 2022 10:20:55 +0000

Sorry it didn't help.
I was referring to your post:

sudo mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!

Re: mariadb on ceres

dummy@example.com (mknoop) — Mon, 22 Aug 2022 18:00:17 +0000

I was not sure which script you were referring to, so I tried it on both "./mariad start" and "mysql_secure_installation".

No difference from using sudo.

Re: mariadb on ceres

dummy@example.com (Andre4freedom) — Mon, 22 Aug 2022 17:51:49 +0000

Just an idea: sudo is not always the same as root.
I suggest to do a
su -
That switches your shell to the root account. Then try to change to the script directory and run it (as root user)
After the (hopefully) successful installation you just leave the root shell
Ctrl-D
And your shell will be back to your user again.
Good luck.

Re: mariadb on ceres

dummy@example.com (mknoop) — Mon, 22 Aug 2022 17:21:47 +0000

Here is what happened:

sudo mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
haven't set the root password yet, you should just press enter here.

Enter current password for root (enter for none):
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Enter current password for root (enter for none):
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Enter current password for root (enter for none):
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Enter current password for root (enter for none):
Aborting!

Cleaning up...

I tried typing the root password, and I tried just hitting enter. I got the same resuilt,.

Re: mariadb on ceres

dummy@example.com (etech) — Mon, 22 Aug 2022 08:39:57 +0000

Hi mknoop,
Have you run 'mysql_secure_installation' before trying to launch the service?
Mariadb works flawlessly on my Devuan Daedalus machines.

Re: mariadb on ceres

dummy@example.com (mknoop) — Sun, 21 Aug 2022 17:35:23 +0000

I went into /etc/init.d - entered sudo ./mariadb start and got:

Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!

Not interesting.

Everything was fine before the upgrade.

It is an old system running on a QEMU virtual machine.
I have a parallel debian-sid vm, and the upgrade there went fine.

Re: mariadb on ceres

dummy@example.com (chris2be8) — Sun, 21 Aug 2022 15:54:26 +0000

The interesting part looks to be:

mknoop wrote:

Starting MariaDB database server: mariadbd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mariadb, action "start" failed.

What happens if you invoke the start script manually? Does that produce any interesting messages?

Was mariadb running OK before the upgrade (or is this a new install)?

If it's a new install do you need to do any first time setup steps?

Re: mariadb on ceres

dummy@example.com (mknoop) — Sun, 21 Aug 2022 05:38:26 +0000

I tried them both, but neither helps. I've been poking around /var/log files and /usr/share/doc/mariadb-server-10.6, but I can't figure anything out.