Pi Bullseye Update Failed :(

I just tried to do the update of the NextCloudPi docker container running on my Pi3 under HypriotOS and it’s all gone wrong :frowning:

I stopped the container and removed it, pulled the new Bullseye image and did the usual commands to install it using the previous mounted data volume. If I look in the logs of the container I see the following:

Conf php7.3-fpm disabled.,
To activate the new configuration, you need to run:,
  service apache2 reload,
Enabling conf php7.4-fpm.,
To activate the new configuration, you need to run:,
  service apache2 reload,
Starting PHP-fpm,
Starting Apache,
Starting mariaDB,
2022-04-04 18:28:28 0 [Note] mysqld (mysqld 10.5.12-MariaDB-0+deb11u1) starting as process 143 ...,
2022-04-04 18:28:28 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-04-04 18:28:28 0 [Warning] The parameter innodb_buffer_pool_instances is deprecated and has no effect.,
2022-04-04 18:28:28 0 [Note] InnoDB: Uses event mutexes,
2022-04-04 18:28:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2022-04-04 18:28:28 0 [Note] InnoDB: Number of pools: 1,
2022-04-04 18:28:28 0 [Note] InnoDB: Using generic crc32 instructions,
2022-04-04 18:28:28 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts),
2022-04-04 18:28:29 0 [Note] InnoDB: Using Linux native AIO,
2022-04-04 18:28:29 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728,
2022-04-04 18:28:29 0 [Note] InnoDB: Completed initialization of buffer pool,
2022-04-04 18:28:29 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.34.,
2022-04-04 18:28:29 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error,
2022-04-04 18:28:29 0 [Note] InnoDB: Starting shutdown...,
2022-04-04 18:28:29 0 [ERROR] Plugin 'InnoDB' init function returned error.,
2022-04-04 18:28:29 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.,
2022-04-04 18:28:29 0 [Note] Plugin 'FEEDBACK' is disabled.,
2022-04-04 18:28:29 0 [ERROR] Unknown/unsupported storage engine: InnoDB,
2022-04-04 18:28:29 0 [ERROR] Aborting,
Starting PHP-fpm,
Starting Apache,
Starting mariaDB,
2022-04-04 18:41:01 0 [Note] mysqld (mysqld 10.5.12-MariaDB-0+deb11u1) starting as process 124 ...,
2022-04-04 18:41:01 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-04-04 18:41:01 0 [Warning] The parameter innodb_buffer_pool_instances is deprecated and has no effect.,
2022-04-04 18:41:01 0 [Note] InnoDB: Uses event mutexes,
2022-04-04 18:41:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,
2022-04-04 18:41:01 0 [Note] InnoDB: Number of pools: 1,
2022-04-04 18:41:01 0 [Note] InnoDB: Using generic crc32 instructions,
2022-04-04 18:41:01 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts),
2022-04-04 18:41:01 0 [Note] InnoDB: Using Linux native AIO,
2022-04-04 18:41:01 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728,
2022-04-04 18:41:01 0 [Note] InnoDB: Completed initialization of buffer pool,
2022-04-04 18:41:01 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.34.,
2022-04-04 18:41:01 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error,
2022-04-04 18:41:01 0 [Note] InnoDB: Starting shutdown...,
2022-04-04 18:41:01 0 [ERROR] Plugin 'InnoDB' init function returned error.,
2022-04-04 18:41:01 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.,
2022-04-04 18:41:01 0 [Note] Plugin 'FEEDBACK' is disabled.,
2022-04-04 18:41:01 0 [ERROR] Unknown/unsupported storage engine: InnoDB,
2022-04-04 18:41:01 0 [ERROR] Aborting,

Is there any way I can get things back again, or do I have to stop everything, move the volume folder to somewhere different and then start again and try to migrate the stored files and folders back in again?

I’m not sure what the crash that the log is talking about may be. This came up immediately when I tried to access after starting the new container, and the old container was running OK before and to my knowledge was as up to date as the internal updater allowed.

If I try to access the web interface I get this:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Can it be recovered or is it a rebuild job? I’m no expert on docker, so guidance is needed please!

I don’t know, I think it should be recoverable by removing the old and pulling the new image

It looks like it’s run the upgrade from that log, which commands did you use?

@ZendaiOwl - In the end I gave up and rebuilt everything fresh on a new Pi4 8GB under RaspiOS Lite 64 bit using the 64 bit docker image.

It’s working, but the HTB service keeps going down on me. I can usually fix it by rebooting, but it’s not exactly the reliability I’m after from the app.

Is that a known issue that could be stabilised? When it’s down I get the same error as above, although I guess that’s more a generic notice that things aren’t working rather than anything too specific.

I don’t know at the moment, I’m back working on my studies atm, one exam coming up on Monday which is 72 hours & another just the same the following Monday.

These are the final exam in the Android application course in my university program, after these I have another 2 courses I need to complete before December 5th to apply for the graduation exam project.

So I don’t have much time to spare right now :pray: you can look through the issues on GitHub and here on the forum using ncp tag, someone else might also come in here with the answer giving it a little time.

I don’t know but I think you can use version 1.49.1 as a stable version for now or the 1.50.3, iirc, unless you’re already running this ofc then you could try with 1.49.1

At the moment the newly installed container is 1.50.2, although it’s offering me 1.50.3 as an upgrade.

I’ll have a search around. Best of luck with the exams!

1 Like

Correct, HPB needs adjusting within the Docker image and is a known issue on the repo. Fixing the pre-built images took priority over the Docker images.

I certainly hope you were running a 64 bit distro before. Impossible to say based on what you posted before, but RaspiOS Lite 64 should do fine. Limit for you will be still using a pi3, which is the barest minimum to have 64bit arm.

Before I was on HypriosOS using the 32-bit image on a Pi3B.

It was an old install, and as that OS seems to be dying off and becoming unsupported, I bit the bullet and upgraded everything to a new Pi, card and OS. It’s now on a Pi4 8GB and Bullseye Lite 64 bit.

If it’s a known issue I’ll look further via your link above, and wait for a resolution.
It’s not a show-stopper, just gets annoying to keep having to restart the container fairly frequently.

32bit support was discontinued (by Nextcloud) so makes sense you ran into trouble there. Docs were released to help everyone migrate, but sounds like you reinstalled on the pi4, which is what many of us did.

https://help.nextcloud.com/t/32-bit-support-is-no-longer-available-from-nextcloud-what-are-the-takeaways/143879/2

Correct. I had it available, and given the status of HypriotOS I thought it time to move the whole server Pi onto the new hardware and OS.

It’s now just got this annoying HPB item, but I’m fine to wait for a resolution to that is it’s more an annoyance and it’s an already known issue.

Thanks for the help :slight_smile: