Open Geexirooz opened 1 month ago
{"reqId":"1j1Y0A4xRxc9p6bJB262","level":3,"time":"2024-05-31T12:37:22+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::failure: InvalidArgumentException: Index name \"parent_index\" for table \"share\" collides with the constraint on table \"share_bak\".","userAgent":"--","version":"28.0.6.1","data":{"app":"updater"}}
InvalidArgumentException: Index name "parent_index" for table "share" collides with the constraint on table "share_bak".
Update failed
You appear to have some sort of manually created duplicate table called share_bak
. Does that sound familiar at all to you?
I suggest making sure you have a good database dump (backup) then dropping the share_bak
table.
If you need help doing that, please use the community help forum: https://help.nextcloud.com
Thanks for your reply. I certainly did not knowingly create that table. I have already resolved the issue with the risky fix you mentioned, so I hope no problems arise later.
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbtableprefix": "",
Are you sharing your db with other apps (or even other Nextcloud installations)?
EDIT: I just noticed the following:
Current version is 29.0.1.
Update to Nextcloud 29.0.1 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-29.0.1.zip
Open changelog ↗
{"reqId":"1j1Y0A4xRxc9p6bJB262","level":0,"time":"2024-05-31T12:36:49+00:00","remoteAddr":"","user":"--","app":"core","method":"","url":"--","message":"starting upgrade from 28.0.6.1 to 29.0.1.1","userAgent":"--","version":"28.0.6.1","data":{"app":"core"}}
This output doesn't make any sense. Was there some backstory here? Did you have to run the Updater more than once or anything like that?
Your Updater shouldn't (can't in theory) update from the same version to the same version.
Can you share your updater.log
file?
Installation method
None
What installation method are you using?
Also, now that I think about it, the constraint collision check I believe only fails on a new install. It should only be a warning on an upgrade.
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
⚠️ This issue respects the following points: ⚠️
Bug description
I upgraded the server from 28.0.5 to 28.0.6 successfully. And I tried to upgrade to 29.0.1 right after but it failed with the error attach to this post in the below. Please note that I tried the upgrade from the terminal using this command:
sudo -u www-data php --define apc.enable_cli=1 ./updater/updater.phar
OS => Ubuntu 22.04 (up to date) PHP => 8.1.2-1ubuntu2.17 Apache => 2.4.52 Database => Mysql
How can I get this sorted asap please?
Steps to reproduce
No specific steps to take, just upgrade from 28.0.5 to 28.0.6 and then to 29.0.1 and thing swill fail in the second step.
Expected behavior
I expected it to be upgraded as smoothly as before.
Installation method
None
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response