-
Notifications
You must be signed in to change notification settings - Fork 453
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
Can not upgrade/enable Talk/Spreed after upgrading NextCloud to v29 #13123
Comments
Seems like you manually corrupted the database at some point by either restoring an incomplete backup or manually removing some rows in e.g. oc_migrations table. |
The message is that a migration file we created back in February is trying to create a database table that is already in your database. The easiest way to end up in this situation is:
But okay, Can you run the following command:
That might be necessary to go forward, or manually changing PHP files. |
Thank you for your response, Nick. The nextcloud.log file is over 20GB, so I archived it and created a new one then attempted the Enable function to generate some log data. That 390K file is attached. We have never had any success running 'occ' or '.occ' or './occ' even if we change permissions to allow it to be executable. By default 'occ' is just a shell PHP script in a text file. |
Exactly the same problem for me: Error message after trying to activate: Database error when running migration 19000Date20240227084313 for app spreed The table with name nextcloud_156971c6.oc_talk_proxy_messages already exists.’ After removing the app and downloading and activating it again: the same message. Very, very strange: the date in the error message is exactly the same as for Stupidscript - so it can't be due to the local upgrade. We certainly didn't update at the same time in February 2024. Tables with Spreed in the name do not exist in the DB. I am tempted to delete all tables oc_talk... tables. However, this would lead to the loss of all thrads etc. Is there another way? Greetings, SmartKlabund |
Please try the command that was suggested by nickvergessen and post the output here. |
nickvergessen: Can you run the following command occ migrations:status spreed Output: Command "migrations:status" is not defined. Did you mean one of these? |
The status command is only available when you set |
Ok - Thank you, now is set. Result: In MigrationService.php line 495: Migration step 'OCA\Talk\Migration\Version19000Date20240227084313' is unknown migrations:status |
Can you check if you have multiple copies of the |
@Stupidscript Unluckily the logs don't explain how you came to the situation:
My suggestion for now would be to drop the table directly in the database and then retry the enabling. |
I checked: Only one directory "spreed". |
Then enabling succeeded. Unable to upgrade to v19.09 with unknown error, but that's a NextCloud issue, as no app can be upgraded at this point. Thanks for the help. |
That really sounds like a broader issue on your side then. |
How to use GitHub
Steps to reproduce
An error occurred during the request. Unable to proceed.
Database error when running migration 19000Date20240227084313 for app spreed The table with name "nextcloud.oc_talk_proxy_messages" already exists.
Expected behaviour
When I click 'Enable' or 'Upgrade' or 'Remove' I expect that action to occur successfully and completely
Actual behaviour
Does not 'Enable' or 'Upgrade' or 'Remove'
Talk app
**Talk app version: 19.0.8 (attempted to upgrade to v19.0.9 as prompted but no longer seeing that upgrade option, just 19.0.8)
Custom Signaling server configured: unknown
Custom TURN server configured: unknown
Custom STUN server configured: unknown
Browser
Microphone available: n/a
Camera available: n/a
Operating system: Ubuntu
Browser name: Chrome
Browser version: 127.0.6533.120 (Official Build) (64-bit)
Browser log
Server configuration
Operating system: Ubuntu
Web server: Apache
Database: Maria
PHP version: 8.3
Nextcloud Version: 29.0.5.1
List of activated apps:
Nextcloud configuration:
Server log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: