Hi. I migrated first to the highest version 5, then to version 6. So far it was ok. The next step was to migrate to 6.7 and this is where the problem began. I cannot start the service. I read similar cases on the forum and I couldn’t solve my problem. Please help.
root@Matermost:~# systemctl start mattermost.service
Job for mattermost.service failed because the control process exited with error code.
See “systemctl status mattermost.service” and “journalctl -xe” for details.
ESCOD
– The job identifier is 300674.
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.750 Z”,“level”:“info”,“msg”:“Server is initializing…”,“caller”:“app/server.go:262”,“go_version”:“go1.18.1”}
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.757 Z”,“level”:“info”,“msg”:“Pinging SQL”,“caller”:“sqlstore/store.go:226”,“database”:“master”}
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.761 Z”,“level”:“warn”,“msg”:“Table collation mismatch”,“caller”:“sqlstore/store.go:1181”,“table_name”:“incomingwebhooks”,“expect
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.762 Z”,“level”:“warn”,“msg”:“Table collation mismatch”,“caller”:“sqlstore/store.go:1181”,“table_name”:“preferences”,“expected”:”
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.763 Z”,“level”:“warn”,“msg”:“Table collation mismatch”,“caller”:“sqlstore/store.go:1181”,“table_name”:“users”,“expected”:"utf8mb
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.765 Z”,“level”:“warn”,“msg”:“Table collation mismatch”,“caller”:“sqlstore/store.go:1181”,“table_name”:“channels”,“expected”:"utf
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.766 Z”,“level”:“warn”,“msg”:“Table collation mismatch”,“caller”:“sqlstore/store.go:1181”,“table_name”:“publicchannels”,"expected
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.767 Z”,“level”:“info”,“msg”:“Pinging SQL”,“caller”:“sqlstore/store.go:226”,“database”:“master”}
Feb 16 08:00:40 Matermost mattermost[49828]: {“timestamp”:“2023-02-16 08:00:40.804 Z”,“level”:“fatal”,“msg”:“Failed to apply database migrations.”,“caller”:“sqlstore/store.go:163”,“error”:"driver: mysql, mes
Feb 16 08:00:40 Matermost systemd[1]: mattermost.service: Main process exited, code=exited, status=1/FAILURE
– Subject: Unit process exited
– Defined-By: systemd
– Support: Debian -- User Support
– An ExecStart= process belonging to unit mattermost.service has exited.
– The process’ exit code is ‘exited’ and its exit status is 1.
Feb 16 08:00:40 Matermost systemd[1]: mattermost.service: Failed with result ‘exit-code’.
– Subject: Unit failed
– Defined-By: systemd
– Support: Debian -- User Support
– The unit mattermost.service has entered the ‘failed’ state with result ‘exit-code’.
Feb 16 08:00:40 Matermost systemd[1]: Failed to start Mattermost.
– Subject: A start job for unit mattermost.service has failed
– Defined-By: systemd
– Support: Debian -- User Support
– A start job for unit mattermost.service has finished with a failure.
– The job identifier is 300674 and the job result is failed.