Closed ch3sn3k closed 1 month ago
Hey @ch3sn3k are you able to run migration with our pgloader docker image? It's a build that we tested thoroughly so it should work out of the box. https://hub.docker.com/r/mattermost/mattermost-pgloader/
Hello @isacikgoz, Thank you for the fast reaction. Unfortunately, the result is the same:
docker pull mattermost/mattermost-pgloader
docker run -it --rm -v $(pwd):/home/migration --network="host" mattermost/mattermost-pgloader:latest pgloader migration.load > migration.log
See migration.log
No worries @ch3sn3k
Now reading the logs again, I see
In context SQLITE-OPTIONS:
While parsing SQLITE-OPTIONS.
wondering if there is anything odd for the database DSN values? Can you please check that? It looks like pgloader
is trying to run on sqlite
driver?
@isacikgoz
Ok, the problem seems to be in the MariaDB
DSN and the wrong authentication method. After I have changed mariadb
to use
cat /etc/mysql/mariadb.conf.d/default-auth-override.cnf
# This file is automatically generated by MySQL Maintainer Scripts
[mysqld]
default-authentication-plugin = mysql_native_password
and updated the auth method for the mmuser as is written in your documentation https://docs.mattermost.com/deploy/postgres-migration.html#unsupported-authentication-for-mysql
the pgloader
worked. I have used the docker container as you have recommended.
Once again, thank you for your help since the problem seems to be with authentication to the mysql
database. I have also used special characters in the root
user password like &
and @
, and these also mess up with pqloader
Now I am running on the postgress, so thank you for your assistance
Glad that it worked out! Thanks for sharing your experience 💪
The command
It seems that
multiple readers per thread
is not known for thepgloader
Note: I want to do the migration on the same VM as a Mattermost server is running
Can you advice what to try next?