-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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]: After upgrade to NC v27.0.1, cannot sync to server. SQLSTATE[42S22]: Column not found: 1054 Unknown column 'valuetype' in 'field list' #39548
Comments
Hi @andrew-jolley - Thanks for reporting. That's a little weird though. The Given how it's being triggered for you and there haven't any other reports, I suspect something else is going on here (but anything is possible). Any chance you can provide the output of Also, what version of NC did you upgrade from? |
Hello. |
@andrew-jolley - The general approach would be to do it from the command line using mysql/mariadb client. Something like:
...executed from your NC (or DB) server. If you're using a UNIX socket to connect to your db modify it slightly to something like:
Example:
|
Yes, definitely missing. Haven't seen any other reports of this. This would have been something that somehow got skipped or failed when upgrading/installing NC v25.0.0. No idea why/how. Do you recall any weird things that happened when you upgraded to NC25? Or any chance your database was restored from an earlier backup at some point or something? Would possibly have broken some aspects of CalDav (Calendar, Tasks) too. Since you're already up to NC27, the cause is probably going to remain a mystery. I can help you repair it manually, but first let's check one more thing. Provide the output of the following from your server command-line:
Example (adjusted for my environment which isn't a DietPi but similar idea):
|
Well that's certainly interesting. It certainly thinks the appropriate migration ran successfully. How to manually fixThis should re-run that specific migration manually. It should be as safe as any typical NC upgrade run so handle it however you do so when upgrading. My standard suggestion: Backup your database first Warning: This will temporarily prevent users from connecting to Nextcloud during maintenance modePut Nextcloud into maintenance mode:
Trigger the manual migration that should update the table:
Probably not a bad idea to trigger this too:
Then turn off maintenance mode:
Connect to your db from the command line in the way as you did previously then execute the following again to see if the
Update us here with the status. |
@andrew-jolley - Glad you got it all sorted out! Please close this Issue out when you get a chance if you consider it "done". Thanks! |
Bug description
After upgrading to Nextcloud v27.0.1 on my Raspberry Pi 4, I get an "Internal Server Error" on my desktop client
I have reinstalled both the server, the client and the configuration on the desktop client.
Steps to reproduce
Expected behavior
Client to sync to server
Installation method
Other Community project
Nextcloud Server version
27
Operating system
Other
PHP engine version
PHP 8.2
Web server
Other
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?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
OS: DietPi v8.19.1
Webserver: llighttpd
Installed from DietPi software
The text was updated successfully, but these errors were encountered: