My team was using mattermost 5.31.4 and we have been unable to upgrade past that point.
Now the server had to be moved from one vm to another and has not restarted for a very long time. It seems that some update perhaps to the linux kernel or some other service is also a problem as mattermost is borked. I am able to recover from a backup on the 13th but unable to start with current data.
With all of that said I have installed mm on windows server.( I know unsupported, but its working great.) I have done a full backup including files and dump from postgreSQL. I attempted to recover from backup but the dump file errors when attempting to import.
What is the best method to recover from my last image to the current windows mm install, also using PostgreSQL
Steps to reproduce
Following the upgrade process causes the error, have tried several versions but anything past 5.31.4 results in mm server failing to start.
Restarting the server causes mm to no longer function with check websocket port. mm service is running on the server.
I would expect it to upgrade without an issue.
I would expect it to run and connect.
Job for mattermost.service failed because the control process exited with error code. See “systemctl status mattermost.service” and “journalctl -xe” for details.
Unable to connect to mm service from external system after system reboot.