AIO 14.0.0 Beta – HPB warning and dirty table reads

vawaver · September 2, 2026, 3:51pm

AIO 14.0.0 Beta – HPB warning and dirty table reads

Hi,

I have updated my Nextcloud AIO instance to AIO 14.0.0 Beta.

The instance is running on:

Ubuntu 24.04 LTS, fully updated
Nextcloud AIO: 14.0.0 Beta
Nextcloud: 34.0.3
Talk High-performance backend: 2.1.1~docker

After the update I noticed two warnings/errors and I would like to check whether these are currently expected with the beta version.

Talk High-performance backend

In Administration settings → Overview I see:

High-performance backend

Warning: Running version: 2.1.1~docker;
Server does not support all features of this Talk version,
missing features: changed-users

The Talk HPB itself seems to be running normally.

I found that the same changed-users warning has already been reported for Nextcloud 34 with HPB 2.1.1~docker:

github.com/nextcloud/spreed

HPB compatibility warning: missing capability "changed-users" with Nextcloud 34.0.1 (AIO)

otvorené 11:20AM - 28 Jul 26 UTC

zatvorené 11:56AM - 28 Jul 26 UTC

ricokulzk-dotcom

Needs triage bug

## Describe the bug After updating my Nextcloud AIO installation to the latest …version, the Talk administration page shows the following warning: > Running version: 2.1.1~docker; The server does not support all features required by this Talk version. Missing capabilities: changed-users ## Environment - Nextcloud AIO - Nextcloud 34.0.1 - Talk app 24.0.3 - HPB 2.1.1~docker ## What I verified - All AIO containers recreated successfully. - All containers are healthy. - HPB starts without errors. - Janus is running. - Calls are working. - HPB successfully connects to Nextcloud and retrieves the capabilities. The HPB log shows: ``` Starting up version 2.1.1~docker Using janus MCU Listening on [::]:8081 ``` The capabilities are successfully retrieved, but the capability `changed-users` is missing, causing the compatibility warning. Is this an expected version mismatch or a bug in the capability check? ## Additional information Docker image: `ghcr.io/nextcloud-releases/aio-talk:latest` Nextcloud version: `34.0.1` Talk version: `24.0.3`

There is also a related signaling server issue:

github.com/strukturag/nextcloud-spreed-signaling

Nextcloud Talk 24.0.3 issues a warning of a missing feature_changed_users

otvorené 06:38PM - 24 Jul 26 UTC

kaynemo

Hi all! Nextcloud Talk 24.0.3 app issues a yellow warning that a changed_users f…eature connecting to 2.1.1 signaling server. 2.1.1 signaling server X-Spreed-Signaling-Features: audio-video-permissions, chat-relay, dialout, federation, hello-v2, incall-all, join-features, mcu, offer-codecs, recipient-call, serverinfo, simulcast, switchto, transient-data, transient-sessiondata, update-sdp, welcome 24.0.3 Talk sed -n '/getSignalingServerMissingFeatures/,/^\t}/p' apps/spreed.24.0.3.bak/lib/Signaling/Manager.php $missingFeatures = $this->getSignalingServerMissingFeatures($features); if (!empty($missingFeatures)) { return [ 'status' => Http::STATUS_OK, 'data' => [ 'warning' => 'UPDATE_OPTIONAL', 'features' => $missingFeatures, 'version' => $data['version'], ], ]; } /** * Store appconfig for some optional features that require different * behaviour on PHP backend side */ if (in_array('changed-users', $features, true)) { $this->appConfig->setAppValueBool(Manager::HAS_FEATURE_CHANGED_USERS, true); } return [ 'status' => Http::STATUS_OK, 'data' => [ 'version' => $data['version'], ], ]; } catch (ConnectException) { return [ 'status' => Http::STATUS_INTERNAL_SERVER_ERROR, 'data' => [ 'error' => 'CAN_NOT_CONNECT', ], ]; } catch (\Exception $e) { return [ 'status' => Http::STATUS_INTERNAL_SERVER_ERROR, 'data' => [ 'error' => (string)$e->getCode(), ], ]; } } protected function getSignalingServerMissingFeatures(array $features): array { $optionFeatures = [ 'dialout', 'join-features', 'chat-relay', 'changed-users', ]; return array_values(array_diff($optionFeatures, $features)); } Just thought you should know. The missing feature is an "update optional" class, but I am sure a lot of people running a setup similar to mine will freak out.

Is this currently an expected temporary mismatch between the Talk version included with NC34 and the signaling/HPB version shipped with AIO 14 Beta?

Is any action required, or should AIO users simply wait for an updated HPB image?

`dirty table reads` in the log

I also found this entry in the Nextcloud log:

Debug
no app in context

Exception

dirty table reads:
SELECT * FROM `*PREFIX*jobs`
WHERE (`reserved_at` <= :dcValue1)
AND (`last_checked` <= :dcValue2)
ORDER BY `last_checked` ASC
LIMIT 1

Administration Overview currently shows:

Errors in the log
1 error in the logs since 26 August 2026

I found similar reports in the Nextcloud server tracker, for example:

github.com/nextcloud/server

[Bug]: Prevent/hide "dirty table reads" messages during updates by default

otvorené 11:06AM - 15 Mar 25 UTC

iasdeoupxe

bug 0. Needs triage feature: install and update feature: logging 30-feedback feature: database

### ⚠️ This issue respects the following points: ⚠️ - [x] This is a **bug**, no…t a question or a configuration/webserver/proxy issue. - [x] This issue is **not** already reported on [Github](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR [Nextcloud Community Forum](https://help.nextcloud.com/) _(I've searched it)_. - [x] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions. - [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/). ### Bug description When doing an update (e.g. here from 30.0.6 to 30.0.7) the messages about `dirty table reads` below are showing up in the `nextcloud.log`. As discussed here these are no errors: - #49088 - https://help.nextcloud.com/t/dirty-table-reads-excessive-logging-reproducible/194809 and are only shown if the Loglevel is set to `0`. The problems here are: 1. the updater is setting the Loglevel to `0` / this value automatically during an update (see next log) 2. this is causing a flood of the logs (`grep "dirty table reads" nextcloud.log | wc -l` showed `40` entries just happening during an update), especially as these messages seems to be quite big / long 3. this prevents the focus on the actual important info happening during an update 4. users might get confused by such messages including e.g. `dirty` during updates ``` { "reqId": "***", "level": 1, "time": "***", "remoteAddr": "", "user": "--", "app": "updater", "method": "", "url": "--", "message": "\\OC\\Updater::resetLogLevel: Reset log level to Warning(2)", "userAgent": "--", "version": "30.0.7.2", "data": { "app": "updater" } } ``` ### Steps to reproduce 1. Have 30.0.6 installed 2. Update to 30.0.7 manually (`sudo -u www-data php occ upgrade`) 3. Check `data/nextcloud.log` ### Expected behavior No `dirty table reads` messages in the log file during an update (updater could "hide" these kind of messages during an update by default) so that one can focus on the relevant info on the update (e.g. done repair steps etc.). ### Nextcloud Server version 30 ### Operating system Debian/Ubuntu ### PHP engine version PHP 8.2 ### Web server Nginx ### Database engine version MariaDB ### Is this bug present after an update or on a fresh install? Updated from a MINOR version (ex. 32.0.1 to 32.0.2) ### Are you using the Nextcloud Server Encryption module? Encryption is Disabled ### What user-backends are you using? - [x] Default user-backend _(database)_ - [ ] LDAP/ Active Directory - [ ] SSO - SAML - [ ] Other ### Configuration report Only relevant entry from `config.php`: ```php 'loglevel' => 2, ``` ### List of activated Apps ```shell ``` ### Nextcloud Signing status ```shell ``` ### Nextcloud Logs ```json { "reqId": "***", "level": 0, "time": "***", "remoteAddr": "", "user": "--", "app": "no app in context", "method": "", "url": "--", "message": "dirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1", "userAgent": "--", "version": "30.0.6.2", "exception": { "Exception": "Exception", "Message": "dirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1", "Code": 0, "Trace": [ { "file": "/***/lib/private/DB/ConnectionAdapter.php", "line": 50, "function": "executeQuery", "class": "OC\\DB\\Connection", "type": "->" }, { "file": "/***/lib/private/DB/QueryBuilder/QueryBuilder.php", "line": 289, "function": "executeQuery", "class": "OC\\DB\\ConnectionAdapter", "type": "->" }, { "file": "/***/lib/private/BackgroundJob/JobList.php", "line": 127, "function": "executeQuery", "class": "OC\\DB\\QueryBuilder\\QueryBuilder", "type": "->" }, { "file": "/***/lib/private/BackgroundJob/JobList.php", "line": 47, "function": "has", "class": "OC\\BackgroundJob\\JobList", "type": "->" }, { "file": "/***/lib/private/Setup.php", "line": 415, "function": "add", "class": "OC\\BackgroundJob\\JobList", "type": "->" }, { "file": "/***/lib/private/Updater.php", "line": 227, "function": "installBackgroundJobs", "class": "OC\\Setup", "type": "::" }, { "file": "/***/lib/private/Updater.php", "line": 98, "function": "doUpgrade", "class": "OC\\Updater", "type": "->" }, { "file": "/***/core/Command/Upgrade.php", "line": 190, "function": "upgrade", "class": "OC\\Updater", "type": "->" }, { "file": "/***/3rdparty/symfony/console/Command/Command.php", "line": 326, "function": "execute", "class": "OC\\Core\\Command\\Upgrade", "type": "->" }, { "file": "/***/3rdparty/symfony/console/Application.php", "line": 1078, "function": "run", "class": "Symfony\\Component\\Console\\Command\\Command", "type": "->" }, { "file": "/***/3rdparty/symfony/console/Application.php", "line": 324, "function": "doRunCommand", "class": "Symfony\\Component\\Console\\Application", "type": "->" }, { "file": "/***/3rdparty/symfony/console/Application.php", "line": 175, "function": "doRun", "class": "Symfony\\Component\\Console\\Application", "type": "->" }, { "file": "/***/lib/private/Console/Application.php", "line": 183, "function": "run", "class": "Symfony\\Component\\Console\\Application", "type": "->" }, { "file": "/***/console.php", "line": 87, "function": "run", "class": "OC\\Console\\Application", "type": "->" }, { "file": "/***/occ", "line": 33, "args": [ "/***/console.php" ], "function": "require_once" } ], "File": "/***/lib/private/DB/Connection.php", "Line": 402, "message": "dirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1", "tables": [ "oc_jobs" ], "reads": [ "oc_jobs" ], "exception": {}, "CustomMessage": "dirty table reads: SELECT `id` FROM `*PREFIX*jobs` WHERE (`class` = :dcValue1) AND (`argument_hash` = :dcValue2) LIMIT 1" } } ``` ### Additional info _No response_

So I am not sure whether this is just an existing debug/database warning or something worth investigating further.

I am intentionally using the Beta channel, so I mainly want to confirm whether both of these are currently known/expected with AIO 14.0.0 Beta + Nextcloud 34.0.3.

If any additional logs or information would be useful, I can provide them.

Cheers.

szaimen · September 2, 2026, 4:09pm

Hi, regarding the first error, see Error message NextCloud Talk HBP after NextCloud update

vawaver · September 2, 2026, 4:50pm

@szaimen, glad for that answers the HPB part.

So I understand that the changed-users warning can simply be ignored for now until a new HPB/signaling release becomes available.

What about the second issue from my post?

dirty table reads:
SELECT * FROM `*PREFIX*jobs`
WHERE (`reserved_at` <= :dcValue1)
AND (`last_checked` <= :dcValue2)
ORDER BY `last_checked` ASC
LIMIT 1

Is this also a known/expected issue with NC34, or should I investigate/report this separately?

szaimen · September 2, 2026, 4:51pm

The other must be addressed in the server code and is thus for now expected.

mic2025 · September 30, 2026, 6:17pm

There is still no update available which fixes the warning “Achtung: Laufende Version: 2.1.1~docker; Der Server unterstützt nicht alle Funktionen dieser Talk-Version, fehlende Funktionen: changed-users” right? I got a lot of updates in the last weeks but nothing fixed it.

szaimen · September 30, 2026, 7:41pm

Indeed. The feature in question doesnt seem to be merged nor released yet. See Don't need all users in requests from Talk by fancycode · Pull Request #1175 · strukturag/nextcloud-spreed-signaling · GitHub

AIO 14.0.0 Beta – HPB warning and dirty table reads

Talk High-performance backend

dirty table reads in the log

`dirty table reads` in the log