-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix-bug-invalid-modification-date inside docker #4255
Comments
you can either install psql in the container (not best practice but for troubleshooting perfectly valid) or expose your DB port on the docker host and connect using your favorite tool. take a look at this SQL query (it's built on MariaDB mayby you need to adopt for Postgres). This collects invalid files and their versions with additional data from the database and could become starting point for further recovery steps. nextcloud-gmbh/mtime_fixer_tool_kit#23 (comment) related to mtime_fixer_tool_kit #4016 #4188 |
But exposing the postgres port doesn't mean that I can run the script from my laptop, as the script requires not just the db but also the nextcloud files, right? ./solvable_files.sh <mysql|pgsql> <list|fix> <noscan|scan> |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
Hello everyone, I'm trying to fix the mess that was caused by the modification date bug by using this official guide, but it doesn't work when NC is a docker container (it doesn't have psql installed).
Is there another guide to follow?
Thank you,
RF
The text was updated successfully, but these errors were encountered: