Closed jmechnich closed 4 months ago
I just realized that this might actually be an issue with https://github.com/nextcloud/logreader/...
Yeah, nextcloud/logreader@32f93c28276564df9defa67469685092cb87f87f broke stuff. Could someone move this issue to nextcloud/logreader?
Thanks in advance and sorry for the noise!
⚠️ This issue respects the following points: ⚠️
Bug description
After upgrading from NC 28.0.4 to NC 29, I noticed the following:
The contents of
nextcloud.log
is not identical to the output of./occ log:tail
or https://server.tld/settings/admin/logging. The browser output sorts the messages by timestamp, so the order is slightly different.More specifically, log messages from the last two hours are duplicated (the time frame is just an estimate but apparently it is not a constant number of entries).
Steps to reproduce
jq -r '. | {time,message} | join(" ")' < nextcloud.log | tail -8
./occ log:tail -r | jq -r '. | {time,message} | join(" ")' | tail -8
Expected behavior
Log messages in log file, printed by occ log:tail and in /settings/admin/logging are identical.
Installation method
Community Manual installation with Archive
Nextcloud Server version
29
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?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
The errors present in the logs are caused by a missing release update for group folders reported here.