Open SystemKeeper opened 5 months ago
Thanks for the report @SystemKeeper. This is a info level log message and it comes from https://github.com/nextcloud/server/blob/e5a6698ec0125d0183b3e71d27e4d22dae0431bc/lib/private/Notification/Manager.php#L357
Not sure either where this could come from, also given that mentioning in a document works and results in notifications in my tests.
I also could not trigger a debugger breakpoint when sending a notification for a mention. @SystemKeeper Can you maybe share the related entry that was created in your oc_notifications table?
I was thinking about this morning. Could it be that - during an update - the app was temporarily disabled while at the same some one tried to fetch the notifications?
I'll try to verify that with the access logs
SELECT * FROM oc_notifications WHERE app = 'text' AND user = '<user>';
+-----------------+------+--------------+------------+-------------+-----------+-----------+-------------------------------------------------------------+---------+--------------------+------+------+---------+
| notification_id | app | user | timestamp | object_type | object_id | subject | subject_parameters | message | message_parameters | link | icon | actions |
+-----------------+------+--------------+------------+-------------+-----------+-----------+-------------------------------------------------------------+---------+--------------------+------+------+---------+
| 73712 | text | <user> | 1696933982 | file | 859331 | mentioned | {"sourceUser":"marcel.mueller","targetUser":"<user>"} | | [] | | | [] |
+-----------------+------+--------------+------------+-------------+-----------+-----------+-------------------------------------------------------------+---------+--------------------+------+------+---------+
That is the only notification of the user in question. It happenes multiple times during the day:
grep mentioned nextcloud.log.3 | wc -l
19
So seems not related to the update. But I don't see anything weird in this entry? I also checked that 859331
is in oc_filecache
.
Is <user>
the actual user id or did you replace this?
Is
<user>
the actual user id or did you replace this?
I replaced it. It has the same format as "marcel.mueller", and also does not contain any special characters.
1696933982
Is from last october. So is a very old notification.
Describe the bug Not really sure if it is a bug, but I noticed this in the log of an instance. From the error I would assume it happens when someone was mentioned in a text document. But when I manually try it, it works. So not sure what triggers the exception.
Screenshots If applicable, add screenshots to help explain your problem.
Server details:
Logs
#### Nextcloud log (data/nextcloud.log) ``` { "reqId": "3CSQVHfB4Gmn2EyGSI46", "level": 1, "time": "2024-06-10T09:00:26+02:00", "remoteAddr": "172.31.2.42", "user": "