"column User.locale does not exist" after Docker container update
Hi all, I am receiving this error at the point of login after updating and recreating the Twenty docker containers with the most recent version. System was previously working perfectly. Any assistance or guidance would be welcome.
16 Replies
That happened to me too, then I reinstalled on a fresh installation and got another error about user not logged in
Hello @Rorschach what version of twenty are you deploying exactly ?
In case it's the 0.42.2 please double check following steps
Env vars
- Removed:
FRONT_PORT, FRONT_PROTOCOL, FRONT_DOMAIN, PORT
- Added: FRONTEND_URL, NODE_PORT, MAX_NUMBER_OF_WORKSPACES_DELETED_PER_EXECUTION, MESSAGING_PROVIDER_MICROSOFT_ENABLED, CALENDAR_PROVIDER_MICROSOFT_ENABLED, IS_MICROSOFT_SYNC_ENABLEDI rolled back to 0.41.5 which does not have this issue. All recent updates after that have this issue.
Is there any documented process to go from 0.41 to 0.42 within Docker?
It looks to just be a new column that's been added, is there perhaps a command that can be run within the mariadb container that will create the required column?
Hello @Rorschach, should be fixed in v0.42.3
Let me know !
Same issue on 0.42.3
Rolled back to 0.41.5 again
Please use latest 0.42
I'm also not sure to understand what issue you're talking about
Please provide as much information as possible regarding your problem
It is the issue described in the opening post
"column User.locale does not exist" after Docker container update
This is just a statement
How have you acheived to this point
"Hi all, I am receiving this error at the point of login after updating and recreating the Twenty docker containers with the most recent version. System was previously working perfectly. Any assistance or guidance would be welcome."
I do have access to chat history, could you please bring more information your current outage
Receiving this error after what commands ? What achieved to be successfull beforehand, more logs etc
It's running on docker with your one step script. Versions worked up to and including v0.41.5. Moving past that version produces the error when trying to log in.
Upgrading is being done via standard docker delete-recreate containers
I see there are version-specific upgrade steps at this URL: https://twenty.com/developers/section/self-hosting/upgrade-guide
However there is no indication of where to run these commands
Please find related commands to run in order to migrate between 0.41 to 0.42 versions here
Indeed you need to migrate your self hosted application it order for it to run on the targeted version
In your twenty-server container
Should they be executed pre or post-upgrade?
Will they break backwards compatibility with previous versions?
Executing the commands via docker exec post-upgrade resolved the issue
It's probably worth documenting this process in a little more detail on the upgrade documentation
Nice well done ! Noted
Hey @Prastoin - I'm getting a similar error as OP after upgrading to LATEST. This is what I get when running
docker exec -it twenty-server-1 yarn database:migrate:prod
docker exec -it twenty-server-1 yarn command:prod upgrade-0.42
Any thoughts on how to resolve?
Hello @Andreas , col
createdByContext has been added in 0.41
Please double check all the commands in the upgrade migration guide ( migrate prod and upgrade-0-41 )
If the issue is persisting please forward your migrations logs
It might be failing your workspaces for some reason !
From what version have you migrated from to 0.42 ?