I’m on the newest version (Nextcloud 30) in an docker setup.
I updated it a few days ago.
Now I checked my admin area and recognized a lot of strange errors.
Maybe somebody can help me to find out where they come from and how to set them off:
I don’t see any in the screenshot above, but that doesn’t matter, as it could be as simple as another application or the core checking to see if Circles is present. The debug log, as the name suggests, is mainly for developers to debug issues, and it’s very chatty. The messages in there are usually not actual problems, but mostly just hints for developers, like all the ‘deprecated’ messages that might become a problem at some point in the future, and then turn into actual errors when the corresponding feature has actually been removed.
Long story short, set the log level to 2 and as long as you don’t have any actual problems with your Nextcloud and then actively want to help debug the issue, there is almost never a reason to go to 0 or 1.
hm ok.
So it can not be that there are still apps active in my installation which are e.g. outdated? Circles e.g. supports Nextcloud until version 29.
So it can not be an old installation running under the hood and producing the log messages?
Here the concrete message (my first post should have a screenshot. Strange that you can’t see it):
[no app in context] Fehlersuche: OCA\Circles\Notification\Notifier::prepare() threw \InvalidArgumentException which is deprecated. Throw \OCP\Notification\UnknownNotificationException when the notification is not known to your notifier and otherwise handle all \InvalidArgumentException yourself.
GET /ocs/v2.php/apps/notifications/api/v2/notifications?format=json
von 172.18.0.3 von Tockra um 25.09.2024, 16:55:05
Have you perhaps installed Teams, the successor, or rather the renamed version of Circles? If so, that’s it, because internally it’s still named Circles.