I have been a huge fan of https://www.turnkeylinux.org/tracks for quite a while. i am trying to setup a new instance using version18.0 of the ISO. i am having issues with MariaDB. it seems it will only run one time, and as soon as you either reboot the appliance, or restart MariaDB it will no longer start.

I have followed this thread extensively, and unfortunately i am still having the issue: https://www.turnkeylinux.org/forum/support/tue-20240430-1614/cant-get-re...

When i try and restart MariaDB, i get the error below, it seems the issue is with innodb, everything i have found suggests deleting some log files which do not exist for me. Any help or suggestions would be greatly appreciated.

x mariadb.service - MariaDB 10.11.6 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2025-04-13 00:38:12 UTC; 13min ago
Duration: 1h 37min 33.514s
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 6348 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 6349 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 6351 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status>
Process: 6434 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 6434 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 327ms

Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [Note] InnoDB: Starting shutdown...
Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [Note] Plugin 'FEEDBACK' is disabled.
Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [Warning] 'innodb-large-prefix' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Apr 13 00:38:12 tracks mariadbd[6434]: 2025-04-13 0:38:12 0 [ERROR] Aborting
Apr 13 00:38:12 tracks systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Apr 13 00:38:12 tracks systemd[1]: mariadb.service: Failed with result 'exit-code'.
Apr 13 00:38:12 tracks systemd[1]: Failed to start mariadb.service - MariaDB 10.11.6 database server.
Forum: 
Jeremy Davis's picture

Argh! Thanks for reporting! It looks like I dropped the ball there. :(

I have updated the build code for all the Rails based apps (including Tracks) but for some reason the updated Tracks appliance - with the required fix - isn't on the mirror?!

I have a few other appliances to update so I'll add that to the batch. Hopefully should get them done and released by the end of next week.

In the meantime, I'll see if I can tweak the (hacky) Redmine script so it works with Tracks too.

Jeremy, thank you, the redmine script seems to have done the trick!! Very much appreciated!!! Thanks, Rick
Jeremy Davis's picture

Great, thanks for confirming and glad that it's now up and running.

It's somewhat irrelevant to you now, but I'll try to get the updated/fixed Tracks image built and uploaded to the mirror ASAP. Unfortunately I'm having some issues with my work PC that I'll need to resolve before I can move on to that so my timeframe for when I'll complete that has blown out and I do not have a new ETA... :(

Add new comment