MariaDB - safe way to stop / shutdown

[mzwach]

Hi,

I really appreciate your great work on Termux! It seems to be the best way to have all the options on Android, Linux offers.
GREAT!

My problem is, that I have often troubles, that my MariaDB (innodb) database crashes and cannot be startet
automatically anymore.

So I am excited to get some response, what is the best way to stop/terminate/shutdown Termux, especially MariaDB within Termux?

I have tried also several ways to start the database:

• using manual start with mariadbd-safe
• using sv-enable mysqld
• using start script in ~/.termux/boot/

Some of the options do not seem to work reliable on my device.

But the bigger problem is, that sometimes the database cannot start automatically anymore, having troubles to the innodb tables up again.

Errors like the following appear and mariadb does not start anymore:

2022-02-28 10:41:06 0 (Note] InnoDB: Compressed tables use zlib 1.2.11 2022-02-28 10:41:06 0 [Note] InnoDB: Number of pools: 1 2022-02-28 10:41:06 0 [Note] InnoDB: Using generic crc32 instructions 2022-02-28 10:41:06 0 [Note] mysqld: O_TMPFILE is not supported on /data/data/com. termux/files/usr/tmp (disa bling future attempts) 2022-02-28 10:41:06 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 13421772 8 2022-02-28 10: 41:06 0 [Note] InnoDB: Completed initialization of buffer pool 2022-02-28 10:41:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=2337138,2337138 2022-02-28 10:41:06 0 [ERROR] InnoDB: Malformed log record; set innodb_force_recovery=1 to ignore 2022-02-28 10:41:06 0 (Note] InnoDB: Dump from the start of the mini-transaction (LSN=2337138) to 100 bytes after the record: len100; hex 6c69616e6365075052494d4152590c6e5f646966665f706678303100204302030683b630000e070c070c0a0070706c 69616e63655052494d4152596e5f646966665f706678303100000000046d9200000145127c6214906d000000000000000000000000: asc liance PRIMARY n_diff_pfx01 C 0 ppliancePRIMARYn diff pfx01 Elb m 2022-02-28 10:41:06 0 [Warning] InnoDB: Log scan aborted at LSN 2401792 2022-02-28 10:41:06 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2022-02-28 10:41:06 0 [Note] InnoDB: Starting shutdown. 2022-02-28 10:41:06 0 [ERROR] Plugin " InnoDB• init function returned error 2022-02-28 10:41:06 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed 2022-02-28 10:41:06 0 (Note] Plugin "FEEDBACK' is disabled. 2022-02-28 10:41:06 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2022-02-28 10:41:06 0 [ERROR] Aborting

I really would hear your opinion or your ideas to that problem.

Thank you in advance,
Best Regards,
Michael

[xtkoba]

For reference, this discussion has now been converted to an issue: #9729.