Closed pabloeisenhut closed 11 months ago
Can you please add the missing information to this bug report. Just posting the notification isn't helpful.
The reason none
means that the update was aborted due to the previous failures. You should have gotten an error message in the first three notifications.
If you don't have these any more, you can reset the attempts with this command:
./occ config:app:set passwords passwords/db/attempts --value=0;
[passwords] Fatal: Exception: Breached password database update failed at <
at 2023-07-29T10:21:54+00:00
I have filled in all the information to the best of my knowledge. @marius-wieschollek is there any way to fix the problem?
The exception you found in the logs is just the one that shows up once the maximum attempts have been reached. I have improved the wording in the exception and notifications in relation to this. You can try the command i wrote in my earlier comment to reset the attempts and see if that resolves the issue or at least brings back the original error messages. Or you can check this article in the wiki: https://git.mdns.eu/nextcloud/passwords/-/wikis/Administrators/Notifications/Breached-Passwords-Update-Failure-Notification
Thanks, it actually seems to have been due to the opcache.memory_consumption setting.
⚠️ This issue respects the following points: ⚠️
Server Information
Client Information
Client independent
Bug description
For some time now, the following message appears at regular intervals.
Could not update breached passwords database![1](https://github.com/marius-wieschollek/passwords/assets/137991389/af0a4433-306c-406d-96e0-c594b31592c3)
Steps to reproduce
After a migration of the cloud, this problem appeared for the first time. Unfortunately, I can not explain how this problem came about.
Expected behavior
No error message and the database breached passwords database updated.
Nextcloud Logs
[passwords] Fatal: Exception: Breached password database update failed at <>
at 2023-07-29T10:21:54+00:00
Browser Logs
No response