-
Notifications
You must be signed in to change notification settings - Fork 241
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
Error: Database error when running migration 4004Date20230414163505 for app calendar #5304
Comments
Duplicate: #5191 The new release 4.4.1 should fix this issue again.. Correct? |
Yes |
Unfortunately not. Had the same error than @solracsf. And after that I'm getting:
NC 26 |
The calendar release does not fix upgrade errors with files version or files trashbin. What we fixed is the missing class error. |
This comment was marked as outdated.
This comment was marked as outdated.
maybe also worth to take a look into this related issue? 2727 |
This comment was marked as duplicate.
This comment was marked as duplicate.
same here. From 4.3.5 to 4.4.1 on latest nextcloud 25 series. |
@flozz @sksksksk Solution mentioned in above link to issue https://github.com/nextcloud/all-in-one/issues/2727 |
Same here. Only that after clicking on that "proceed update" button, I got another error, telling me to refresh the website. After doing so, the server is now completely crashed Error 503. Great. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
#5191 (comment) as a counter example |
What PHP version do you all use and what are your opcache settings? I could imagine that the old (and faulty) autoloader was still active because opcache didn't clear early enough. |
The 4.4.1 release does contain an autoloader mapping for
in vendor/composer/autoload_classmap.php. |
@ChristophWurst
|
I was able to trigger it myself with an upgrade from 4.3.0 to 4.4.1 The issue is that #5295 fixes the autoloader but the autoloader fix for an upgrade only takes affect for future upgrades. So 4.4.2 or 4.5.0 will be fine only :s |
4.4.0 and 4.4.1 removed from https://apps.nextcloud.com/apps/calendar/. Tomorrow I'll
|
The plan to get instances unstuck is as follows
Progress is tracked in #5304 (comment). |
I just updated 4.3.4 to 4.3.5 without any issue :) |
https://github.com/nextcloud-releases/calendar/releases/tag/v4.4.2 tagged. Release will be built in a few minutes. I did a prerelease earlier to test the update in a production-like environment with the real app store:
I hope this gives everyone a smooth upgrade. |
A verbose summary of what went wrong: https://help.nextcloud.com/t/post-mortem-analysis-composer-authoritative-classloader/163969 Thanks for the reports and system infos, everyone. |
4.3.5 updated to 4.4.2 flawlessly 👌 |
This is done. The reverted feature will revive with v4.5. |
Steps to reproduce
occ app:update --all
occ upgrade
fixes the instanceExpected behavior
Migration is fine
Actual behaviour
Error.
Calendar app version
4.4.1
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
Apache
Database engine version
MariaDB
PHP engine version
PHP 8.1
Nextcloud version
25.0.7
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
No response
Nextcloud configuration
No response
Web server error log
No response
Log file
Browser log
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: