InnoDB Crash after Update

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1

Hey there. My Docker container automatically updated itself overnight and afterward could not recover to a normal state.

Container logs show:

Starting PHP-fpm
Starting Apache
Starting mariaDB
2022-03-03 21:11:33 0 [Note] mysqld (mysqld 10.5.12-MariaDB-0+deb11u1) starting as process 105 ...
2022-03-03 21:11:33 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
2022-03-03 21:11:33 0 [Warning] The parameter innodb_buffer_pool_instances is deprecated and has no effect.
2022-03-03 21:11:33 0 [Note] InnoDB: Uses event mutexes
2022-03-03 21:11:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-03-03 21:11:33 0 [Note] InnoDB: Number of pools: 1
2022-03-03 21:11:33 0 [Note] InnoDB: Using ARMv8 crc32 + pmull instructions
2022-03-03 21:11:33 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-03-03 21:11:33 0 [Note] InnoDB: Using Linux native AIO
2022-03-03 21:11:33 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2022-03-03 21:11:33 0 [Note] InnoDB: Completed initialization of buffer pool
2022-03-03 21:11:34 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.31.
2022-03-03 21:11:34 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-03-03 21:11:34 0 [Note] InnoDB: Starting shutdown...
2022-03-03 21:11:34 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-03-03 21:11:34 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-03-03 21:11:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-03-03 21:11:34 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-03-03 21:11:34 0 [ERROR] Aborting

I am running the Docker image on Ubuntu 20.04 LTS with the latest updates on an ARM64 device (ODROID N2). I have the currently newest image available of NCP on Docker Hub v1.47.1

Any advice on how to fix it or what happened?

1 Like
2

Ran into the same issue today. Seems like there was a version increase (2 days ago vs. 5 months ago for the images before) for the stable images by the nextcloudpi developers recently.

I changed the docker tag from latest to v1.40.4 and started the container - everything is working again as expected.

docker pull ownyourbits/nextcloudpi-x86:v1.40.4
1 Like
3

Yep worked. The newest NCP image is just broken.

4

Sadly didnt work for me. I am using docker compose and container will stop with starting maria db:

nextcloudpi | 2022-03-05 14:54:22 0 [Note] mysqld (mysqld 10.3.29-MariaDB-0+deb10u1) starting as process 106 …

Allready removed container and image. I think I have to wait for a new docker image :frowning:

5

Are you sure you are not using the latest image? Did it work before? Maybe also upgrade your dist. Or give us more details about your system.

6

Using Debian 11 on an x64 machine. Docker and docker compose is from standard debian repository. My docker compose file before change:
version: ‘3’
services:
nextcloudpi:
image: ownyourbits/nextcloudpi-x86
restart: always
command: “${IP}”
ports:
- “80:80”
- “443:443”
- “4443:4443”
volumes:
- /media/nextcloud/ncdata:/data
- /media/nextcloud/ssl:/ssl
- /etc/localtime:/etc/localtime:ro
container_name: nextcloudpi

volumes:
ncdata:

and with 1.40.4 tag:
version: ‘3’
services:
nextcloudpi:
image: ownyourbits/nextcloudpi-x86:v1.40.4
restart: always
command: “${IP}”
ports:
- “80:80”
- “443:443”
- “4443:4443”
volumes:
- /media/nextcloud/ncdata:/data
- /media/nextcloud/ssl:/ssl
- /etc/localtime:/etc/localtime:ro
container_name: nextcloudpi

volumes:
ncdata:

Docker only stops with 1.40.4 tag, without it seems that everything is starting normaly but cant reach nc with chrome -maintaince error (The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.)

Edit:
Fixed permissions with:
sudo chown root:root -R bin/
sudo chown root:root -R etc/
sudo chown systemd-timesync:systemd-journal -R database/
sudo chown root:www-data -R ncp/
sudo chown www-data:www-data -R nextcloud/

My “normal” nc instance wasnt working with it, but backup works. Thanks for helping!

7

You don’t mean the maintenance of NCP, right? Because that you can configure yourself.

8

Yes, it wasnt the normal nc maintaince mode. It was an http error (dont know the code)

9

Two months later and I tried again the latest version of NCP and the bug is still existing… can somebody take care of this?