Skip to content
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

[Bug]: Update to 29.0.8 failed due to index name "nid" collision with constraint #49052

Closed
4 of 8 tasks
VolkerKaminDSA opened this issue Nov 3, 2024 · 2 comments
Closed
4 of 8 tasks
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug

Comments

@VolkerKaminDSA
Copy link

⚠️ This issue respects the following points: ⚠️

Bug description

While updating to 29.0.8 (in a chain after doing a few overdue updates just before, but with a minute between each update), my system got stuck. The error message specifically asked me to report this here.

I have limited access to the system (web hoster), but I am a computer scientist and the support of my hoster is rather responsive and forthcoming.

I have the option to just go back to a backup, but I'd rather fix the issue.

Aktualisierung auf 29.0.8
InvalidArgumentException: Index name "nid" for table "WX19z_social_3_stream" collides with the constraint on table "WX19z_social_3_cache_actor".

Detaillierte Protokollmeldungen 
Update vorbereiten

Log-Level auf "debug" gesetzt

Wartungsmodus eingeschaltet

Reparaturschritt: Repair MySQL collation

Reparaturinformation: All tables already have the correct collation -> nothing to do

Reparaturschritt: Copy data from accounts table when migrating from ownCloud

Reparaturschritt: Drop account terms table when migrating from ownCloud

Das Datenbankschema wird aktualisiert

Datenbank aktualisiert

InvalidArgumentException: Index name "nid" for table "WX19z_social_3_stream" collides with the constraint on table "WX19z_social_3_cache_actor".

Das Update ist fehlgeschlagen. Bitte melden Sie dieses Problem an die [Nextcloud Community](https://github.com/nextcloud/server/issues).

Steps to reproduce

  1. Go to my domain, which presents the self-updater as expected.
  2. Execute self-update by clicking the button.
  3. Watch the error message come up.

Expected behavior

Finish the update as per usual.

Nextcloud Server version

28

Operating system

None

PHP engine version

PHP 8.1

Web server

None

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Upgraded to a MAJOR version (ex. 28 to 29)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@VolkerKaminDSA VolkerKaminDSA added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Nov 3, 2024
@VolkerKaminDSA VolkerKaminDSA changed the title [Bug]: [Bug]: Update to 29.0.8 failed due to index name "nid" collision with constraint Nov 3, 2024
@solracsf
Copy link
Member

solracsf commented Nov 3, 2024

This seem related to Social app, not Server. Like nextcloud/social#1871
Please report there.

@solracsf solracsf closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2024
@joshtrichards
Copy link
Member

#41253 (comment)

#41253 (comment)

Don't hesitate to pop into the help forum (https://help.nextcloud.com) if still stuck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug
Projects
None yet
Development

No branches or pull requests

3 participants