Sudo mv -iv mattermost mattermost-$backupvers-$ts #sudo find mattermost/ mattermost/client/ -mindepth 1 -maxdepth 1 \! \( -type d \( -path mattermost/client -o -path mattermost/client/plugins -o -path mattermost/config -o -path mattermost/logs -o -path mattermost/plugins -o -path mattermost/data \) -prune \) | sort | sudo xargs echo rm -r #sudo cp -ra mattermost/ mattermost-$backupvers-$(date +'%F-%H-%M')/
#Mattermost docs install#
# Existing install directory - " -db-instance-identifier "mattermost" -region "ap-southeast-2" # You should gather the following information before starting the upgrade:
#Mattermost docs upgrade#
I have created a script based on the standard upgrade instructions ( Upgrading Mattermost Server - Mattermost 5.31 documentation) with a couple of optimisations and automated backups etc: #!/bin/bash
My initial reaction was “the script must have failed copying the config file back” (which makes no sense as my login still worked, without the correct config file there would not have been database access for logging in users) Though it did not always reset the config immediately upon start. Yes what you are describing matches my experience from earlier today. I can’t attach a file here but will add another post with both config versions if it would be helpful. I thought I got it to work before but then after a while the config reset again (“Please configure your site URL on the System Console” popped up, files / embedded images in posts stopped working). The config obviously works for startup (login works). I have tried merging our live config (from 5.29.1) with the blank config (created by 5.31) to make sure we have valid json. It obviously works to some degree (I can log in - it wouldn’t know my user if it didn’t have access to the database) but then the config file gets wiped. When mattermost 5.31 starts up the config file gets wiped. Config.json was still good before the upgrade)
#Mattermost docs update#
I decided to update to run the planned update (5.29.1 to 5.31.0) as an attempt to fix the issue. After a reboot of the VPS the MM server did not start up. (unrelated to the issue but added for completeness: Our mattermost server crashed / stopped responding over the weekend. Mattermost 5.31 should just start and update the config.json with any new settings it expects to find in there. The main mattermost config file gets reset to default values after upgrade to 5.31 Steps to reproduceĬheck config file: all settings have reverted to default (including DB, site URL, data storage location, etc) Expected behavior
0 kommentar(er)
