Update Problem to 31.0.8

[ntn]

Support intro

Sorry to hear you’re facing problems.

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

• Official documentation (searchable and regularly updated)
• How to topics and FAQs
• Forum search

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.

The Basics

• Nextcloud Server version (e.g., 29.x.x):
  • 31.0.8.1
• Operating system and version (e.g., Ubuntu 24.04):
  • Debian GNU/Linux 12 (bookworm)
• Web server and version (e.g, Apache 2.4.25):
  • Apache/2.4.62 (Debian)
• PHP version (e.g, 8.3):
  • PHP 8.2.29 (cli)
• Is this the first time you’ve seen this error? (Yes / No):
  • Yes
• When did this problem seem to first start?
  • Today in the morning while i was trying to update Nextcloud

Summary of the issue you are facing:

I was trying to update Nextcloud to Version 31.0.8 and got the Error from the Screenshot.
I finally succeeded by manually changing values in the database ( INSERT INTO oc_migrations (app, version) VALUES (‘core’, ‘31000Date20250731062008’); ) but I think it was not the best way. Now everything is working just fine but there are still some background errors.

Steps to replicate it (hint: details matter!):

1. Just update to ne newest Nextcloud Version (but maybe my System was just a bit unstable idk)

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

|Info|updater|\OC\Updater::maintenanceActive: Maintenance mode is kept active|15.08.2025, 12:07:12||
| --- | --- | --- | --- | --- |
|Info|updater|\OC\Updater::updateEnd: Update successful|15.08.2025, 12:07:12||
|Info|updater|\OC\Updater::finishedCheckCodeIntegrity: Finished code integrity check|15.08.2025, 12:07:12||
|Info|updater|\OC\Updater::startCheckCodeIntegrity: Starting code integrity check...|15.08.2025, 12:06:58||
|Fehlersuche|serverDI|The requested alias "IntegrityCodeChecker" is deprecated. Please request "OC\IntegrityCheck\Checker" directly. This alias will be removed in a future Nextcloud version.|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairInfoEvent: Repair info: Queued background to validate account properties.|15.08.2025, 12:06:58||
|Fehlersuche|no app in context|Exceptiondirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairStepEvent: Repair step: Validate account properties and store phone numbers in a known format for search|15.08.2025, 12:06:58||
|Fehlersuche|no app in context|Exceptiondirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairStepEvent: Repair step: Add cleanup-deleted-users background job|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairStepEvent: Repair step: Remove legacy ".ocdata" file|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairInfoEvent: Repair info: Theming is not used to provide a logo|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairStepEvent: Repair step: Cache logo dimension to fix size in emails on Outlook|15.08.2025, 12:06:58||
|Info|no app in context|core/BackgroundJobs/AppConfigLazyMigration: 0 config values updated|15.08.2025, 12:06:58||
|Fehlersuche|no app in context|Exceptiondirty table reads: SELECT `appid`, `configkey`, `configvalue`, `type`, `lazy` FROM `*PREFIX*appconfig`|15.08.2025, 12:06:58||
|Info|updater|OC\Repair\Events\RepairStepEvent: Repair step: migrate lazy config values|15.08.2025, 12:06:58|

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

• Use the preformatted text formatting option in the editor for all log entries and configuration output.
• If screenshots are useful, feel free to include them.
  • If possible, also include key error output in text form so it can be searched for.
• Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.