T
Twenty2mo ago
El Odve

ERROR [ExceptionsHandler] column Workspace.trashRetentionDays does not exist after upgrade to 1.8

Self-hosted using docker here. I'm trying to upgrade from 1.7.7 to 1.8.1, but this breaks twenty completely (going straight to 1.8.2 has the same issue). Can't log in with password, can't log in with Microsoft account. Seems like something goes wrong in the database update, as the headline error seems to be the breakeage point. Any quick fix for this, or should I just restore my 1.7.7 containers?
11 Replies
Prastoin
Prastoin2mo ago
Hey @El Odve seems like you're missing a migration Could you please share your workpsace version database ? core.workspace.version cc @abdulrahmancodes ( AddWorkspaceTrashRetention1760356369619 )
El Odve
El OdveOP2mo ago
Yeah, I'm missing more than one migration - the workspace version is still 1.6.7
Prastoin
Prastoin2mo ago
That's the root cause here, two options: - Restore a 1.6 backup and proceed to 1.7 upgrade ( seems to fail for you or you skipped this version ) - Restore a 1.7 backup downgrade the 1.6 latest version and re-attempt an 1.7 upgrade If failing in 1.7 upgrade please share twenty-server logs
El Odve
El OdveOP2mo ago
I upgraded from 1.6.7 to 1.7.7 yesterday and that seemed fine, but apparently the migration didn't quite go through... The recommended approach is to do incremental upgrades, i.e. 1.6.7-1.7.1, 1.7.3 --> 1.7.7 and then 1.8.1? 1.6.7->1.7.7 might break something? I can't try to run the migrations manually on the current database container?
Prastoin
Prastoin2mo ago
No need to upgrade within the same minor version 1.7.1 -> 1.7.3 I recommend consuming the patch less docker hub mirror e.g 1.7 Your current twenty instance is pretty much corrupted
El Odve
El OdveOP2mo ago
Yeah, that's what I did yesterday - 1.6.7->1.7
Prastoin
Prastoin2mo ago
Yes but it failed, and we will investigate why
El Odve
El OdveOP2mo ago
Ok, I'll restore 1.6.7 and try to migrate to 1.7 again Which logs do you need if this fails again? Narrator: It did. Still at 1.6.7 even after upgrade to 1.7.7 If I try to run migrations manually I get this: yarn database:migrate:prod query: SELECT * FROM current_schema() query: CREATE EXTENSION IF NOT EXISTS "uuid-ossp" query: SELECT version(); query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'core' AND "table_name" = '_typeorm_migrations' query: SELECT * FROM "core"."_typeorm_migrations" "_typeorm_migrations" ORDER BY "id" DESC No migrations are pending
Prastoin
Prastoin2mo ago
Again that s not an issue You don t have to run anything yourself Please upgrade to 1.7 and share twenty server logs
El Odve
El OdveOP2mo ago
I did the upgrade already, which logs do you want from the twenty server? Database version is stuck at 1.6.7 even after the new upgrade.
Prastoin
Prastoin2mo ago
Please proceed to one of both And share all twenty-server logs just after changing your TAG version

Did you find this page helpful?