Upgrade MM 5.3.1 to latest version fails

Troubleshooting
44

After starting mattermost.service there’s shown an error, but the service ist already running for some seconds as you can see at first ps -ef command.

systemctl start mattermost

Job for mattermost.service failed because the control process exited with error code. See “systemctl status mattermost.service” and “journalctl -xe” for details.

systemctl status mattermost

● mattermost.service - Mattermost
Loaded: loaded (/lib/systemd/system/mattermost.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fre 2021-02-05 13:10:24 CET; 2s ago
Process: 27369 ExecStart=/opt/mattermost/bin/mattermost (code=exited, status=119)
Main PID: 27369 (code=exited, status=119)

Feb 05 13:10:24 SERVER systemd[1]: Failed to start Mattermost.
Feb 05 13:10:24 SERVER systemd[1]: mattermost.service: Unit entered failed state.
Feb 05 13:10:24 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.
root@SERVER:/opt#
root@SERVER:/opt#
root@SERVER:/opt#
root@SERVER:/opt# systemctl status mattermost
● mattermost.service - Mattermost
Loaded: loaded (/lib/systemd/system/mattermost.service; enabled; vendor preset: enabled)
Active: activating (start) since Fre 2021-02-05 13:10:45 CET; 937ms ago
Main PID: 27407 (mattermost)
Tasks: 11 (limit: 65000)
Memory: 27.7M
CPU: 353ms
CGroup: /system.slice/mattermost.service
└─27407 /opt/mattermost/bin/mattermost

Feb 05 13:10:45 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.
Feb 05 13:10:45 SERVER systemd[1]: Stopped Mattermost.
Feb 05 13:10:45 SERVER systemd[1]: Starting Mattermost…
Feb 05 13:10:45 SERVER mattermost[27407]: {“level”:“info”,“ts”:1612527045.976185,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system
Feb 05 13:10:45 SERVER mattermost[27407]: {“level”:“info”,“ts”:1612527045.9765236,“caller”:“app/server_app_adapters.go:58”,“msg”:
Feb 05 13:10:45 SERVER mattermost[27407]: {“level”:“info”,“ts”:1612527045.9883635,“caller”:“sqlstore/supplier.go:215”,“msg”:"Ping
Feb 05 13:10:46 SERVER mattermost[27407]: {“level”:“error”,“ts”:1612527046.0502627,“caller”:“sqlstore/supplier.go:807”,“msg”:"Fai
root@SERVER:/opt#
root@SERVER:/opt#
root@SERVER:/opt#
root@SERVER:/opt# ps -ef | grep -i mattermost
matterm+ 27425 1 31 13:10 ? 00:00:00 /opt/mattermost/bin/mattermost
root 27439 21018 0 13:10 pts/0 00:00:00 grep --color=auto -i mattermost
root@SERVER:/opt#
root@SERVER:/opt#
root@SERVER:/opt# ps -ef | grep -i mattermost
root 27459 21018 0 13:11 pts/0 00:00:00 grep --color=auto -i mattermost

Ok, return to v5.3.1 … :frowning:

rm -r mattermost
mv old.mattermost mattermost
mysql> drop database mattermost;
mysql> create database mattermost;
mysql -u root -p mattermost < mm.sql
systemctl start mattermost
systemctl status mattermost
● mattermost.service - Mattermost
Loaded: loaded (/lib/systemd/system/mattermost.service; enabled; vendor preset: enabled)
Active: active (running) since Fre 2021-02-05 13:39:48 CET; 17min ago
Main PID: 30413 (mattermost)
Tasks: 23 (limit: 65000)
Memory: 78.7M
CPU: 2.676s
CGroup: /system.slice/mattermost.service
├─30413 /opt/mattermost/bin/mattermost
└─30481 plugins/jira/plugin.exe

Voila! 5.3.1 is up and running … :slight_smile: