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
Automated tagging breaks occ:scan - PostreSQL #75
Comments
I've tested it again with a fresh install of NC. In the PostgreSQL log I can find this:
Can I provide any more information? |
i just spend a few minutes on a virtual server to replicate your issue. Bug replicate with 10.8 and 11.3. Bug not replicate with mariaDB 10.3 |
@stratege1401 thanks for verifying this. Seems to be a problem with PostgreSQL then. |
https://github.com/nextcloud/server/pull/16822/files should fix the issue. |
I think you meant this one: https://github.com/nextcloud/server/pull/16822/files And yes, it seems to work, |
I have the same issue now, also using PostgreSQL and Nextcloud 25.0.5. I have the same issue with the automated tagging breaking occ:scan |
this is the PostgreSQL logfile, similar to above. 2023-03-29 23:57:10.794 CEST [845034] nextclouduser@nextcloud_db FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »oc_systemtag_object_mapping_pkey« |
This is closed almost 3.5 yrs ago. Please open a new issue. |
Just updated to NC 16.0.1 and wanted to do a rescan of all files.
Steps to reproduce
occ files:scan --all
(or just the affected folder)Expected behaviour
files:scan should finish without problems.
Actual behaviour
I get an error:
When I delete the automated tagging rule, the scan works without problems.
Server configuration
Operating system: Ubuntu server 18.04
Web server: nginx
Database: PostgreSQL 10
PHP version: 7.2
Nextcloud version: 16.0.1
Are you using encryption: no
Logs
Nextcloud log (data/owncloud.log)
No logs in nextcloud.log
The text was updated successfully, but these errors were encountered: