MariaDB service hangs on startup

ℹ️ Support
1

Hello,

I installed nextcloud and it worked for a while, but after rebooting, the nextcloud website always returns the “Internal server error” message. After some testing, I found that mariadb never completes starting. It gets stuck in the activating phase.

How can this issue be solved?

Below are the terminal messages, when attempting to start mariadb, as well as the error logs.

systemctl status mariadb.service
● mariadb.service - MariaDB 10.1.48 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: activating (start) since Fri 2023-04-14 20:29:00 CEST; 2min 57s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 11218 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=cd /usr/bin/..; /usr/bin/galera_recovery; [ $? -eq 0 ] && syste
Process: 11202 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 11180 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 11294 (mysqld)
Status: "InnoDB: Error: We scanned the log up to 710569984. A checkpoint was at 710570489 and the maximum LSN on a database page was 0. It is possible that
Tasks: 15 (limit: 4181)
CGroup: /system.slice/mariadb.service
└─11294 /usr/sbin/mysqld

service mysql start

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===

Authentication is required to start ‘mariadb.service’.

Authenticating as: user1, (user1)

Password:

==== AUTHENTICATION COMPLETE ===

Job for mariadb.service failed because a fatal signal was delivered causing the control process to dump core.

See “systemctl status mariadb.service” and “journalctl -xe” for details.

journalctl -xe

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Present: 0x01fb0000 | Host ctl: 0x00000017

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Power: 0x00000001 | Blk gap: 0x00000000

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Wake-up: 0x00000000 | Clock: 0x00000007

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Timeout: 0x0000000e | Int stat: 0x00000000

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b

Apr 14 20:51:27 clb-Jetson kernel: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Caps: 0x376cd08c | Caps_1: 0x10006f73

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Cmd: 0x0000113a | Max curr: 0x00000000

Apr 14 20:51:27 clb-Jetson kernel: sdhci: Host ctl2: 0x0000308b

Apr 14 20:51:27 clb-Jetson kernel: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000ffefe410

Apr 14 20:51:27 clb-Jetson kernel: sdhci: ===========================================

Apr 14 20:51:27 clb-Jetson kernel: mmcblk0: error -110 transferring data, sector 36511078, nr 2, cmd response 0x900, card status 0x0

Apr 14 20:51:27 clb-Jetson kernel: blk_update_request: I/O error, dev mmcblk0, sector 36511078

Apr 14 20:51:39 clb-Jetson kernel: mmc0: Data timeout error

Apr 14 20:51:39 clb-Jetson kernel: sdhci: =========== REGISTER DUMP (mmc0)===========

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Sys addr: 0x00000008 | Version: 0x00000303

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000001

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Argument: 0x022d1d67 | Trn mode: 0x00000013

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Present: 0x01fb0000 | Host ctl: 0x00000017

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Power: 0x00000001 | Blk gap: 0x00000000

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Wake-up: 0x00000000 | Clock: 0x00000007

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Timeout: 0x0000000e | Int stat: 0x00000000

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b

Apr 14 20:51:39 clb-Jetson kernel: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Caps: 0x376cd08c | Caps_1: 0x10006f73

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Cmd: 0x0000113a | Max curr: 0x00000000

Apr 14 20:51:39 clb-Jetson kernel: sdhci: Host ctl2: 0x0000308b

Apr 14 20:51:39 clb-Jetson kernel: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000ffefe410

Apr 14 20:51:39 clb-Jetson kernel: sdhci: ===========================================

Apr 14 20:51:39 clb-Jetson kernel: mmcblk0: error -110 transferring data, sector 36511079, nr 1, cmd response 0x900, card status 0x0

Apr 14 20:51:39 clb-Jetson kernel: blk_update_request: I/O error, dev mmcblk0, sector 36511079

Apr 14 20:51:39 clb-Jetson systemd[1]: mariadb.service: Main process exited, code=dumped, status=6/ABRT

Apr 14 20:51:39 clb-Jetson systemd[1]: mariadb.service: Failed with result ‘core-dump’.

Apr 14 20:51:39 clb-Jetson systemd[1]: Failed to start MariaDB 10.1.48 database server.

– Subject: Unit mariadb.service has failed

– Defined-By: systemd

– Support: http://www.ubuntu.com/support

–

– Unit mariadb.service has failed.

–

– The result is RESULT.

Nextcloud version (eg, 20.0.5): 25.0.4.1
Operating system and version (eg, Ubuntu 20.04): 18.04
Apache or nginx version (eg, Apache 2.4.25): 2.4.29
PHP version (eg, 7.4): 8.1

2

Could you please clarify how you’ve installed Nextcloud. Thanks!

Can you recall last steps of maintenance or other changes made to your system previous to the reboot?
If you have a backup you could rollback.

3

I used the following tutorial to install nextcloud:
Pi Nextcloud Server Install

The main steps are:

sudo wget https://download.nextcloud.com/server/releases/latest.tar.bz2
sudo tar -xvf latest.tar.bz2

The only changes before the issue were running an occ scan to add manually added files and installing an image previewer, as well as running the script to generate the preview images.

Command to run file scan:

sudo -u www-data php /path/to/nextcloud/occ files:scan --all

After running the file scan, I ran into the bug, where it locked files, since the command got interrupted by the ssh terminal disconnecting. Found this Post with the exact same error as me, but wasn’t able to solve that issue. I am not sure, it’s related to Nextcloud not working at all though, because the error only prevents the file scan to run again.

Image preview app: image preview
Command to generate previews:

./occ preview:generate-all

Apart from these two commands, the only other thing I did was reboot, after which Nextcloud wouldn’t run anymore.

4

Did you try any of the recommended solutions? You could try occ maintenance:repair or google it + nextcloud to learn more.

Checkout screen or tmux to avoid encountering this problem in the future. :heart:

1 Like
5

as you correctly identified the issue is related to MariaDB. I would recommend to reach out with their community for best support.

MariaDB 10.1 is quite old. does you system have all the prerequisites installed to support this version?

6

Updated to MariaDB 10.4, as well as reinstalling Nextcloud.
Now the issue is fixed.