Various messages in the error log (every second) after upgrading MariaDB

NC: 30.0.1
PHP: 8.3.13
MariaDB: 10.11.6
OS: AlmaLinux 9.4

Hello everyone,

since the last Nextcloud update I was annoyed by the hint that I should please use a more recent MariaDB version, I upgraded from 10.5 to 10.11 today.
Of course, the Nextcloud instance was in maintenance mode during the upgrade.
Also, after the upgrade everything seemed to work fine…
But now I get messages in the error log every second, for example:

[dav] Fehlersuche: No calendar events found for status check
PUT /ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json
von x.x.x.x von admin um 04.11.2024, 21:27:15
[dav] Fehlersuche: Higher priority status detected, skipping calendar status change
GET /ocs/v2.php/apps/user_status/api/v1/user_status?format=json
von x.x.x.x von philipp um 04.11.2024, 21:27:14
[no app in context] Fehlersuche: Calling OCP\DB\QueryBuilder\IQueryBuilder::andX without parameters is deprecated and will throw soon.
PROPFIND /remote.php/dav/files/philipp/
von x.x.x.x von philipp um 04.11.2024, 21:28:14
[no app in context] Fehlersuche: OCA\LogReader\Controller\LogController::poll uses the @AuthorizedAdminSetting annotation and should use the #[OCP\AppFramework\Http\Attribute\AuthorizedAdminSetting] attribute instead
GET /index.php/apps/logreader/api/poll?lastReqId=…
von x.x.x.x von admin um 04.11.2024, 21:28:52

etc.

Could it be due to the upgrade of MariaDB?
Do I have to do anything else in Nextcloud?
I have already carried out an occ maintenance:repair - but it didn’t help :frowning:

Best regards
Philipp
alias picknicker :cowboy_hat_face:

It looks like debug logging is on. Set your loglevel back to 2 or, well, anything but 0. If you’re using the web-based logreader (looks like you are), maybe you toggled in on by accident there?

Refs:

https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/logging_configuration.html#log-level

Super - that was really it!
I set the log level to 2 and it was quiet…
Thank you very much, jtr :pray:

Now I just have to “empty” the log file - the file is now 2GB in size!
Can I “simply delete the log file” or do I have to pay attention to something?

Greets from the picknicker :upside_down_face:

You can rename the old one and archive it if you want. Or remove it. Up to you. I’d keep it around for a little bit, maybe compressed, personally since I never know if it might come in handy.

This is exactly how I did it (so i archived the log files and then deleted the originals).
I still had various errors in the logs due to the MariaDB upgrade…
Now the hook is green :innocent:

Many thanks again, jtr :pray:

It’s great to get help here so quickly and competently!
I love this community :smiling_face_with_three_hearts:

Greetings from picknicker :cowboy_hat_face:
Have a nice day :wink:

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.