# Upgrade MM 5.3.1 to latest version fails

**URL:** <https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266>\
**Category:** Troubleshooting\
**Created:** [August 11, 2020, 11:32pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266 "2020-08-11T23:32:29Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 11, 2020, 11:32pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/1 "2020-08-11T23:32:29Z")

</div>

I’ve a couple of teams and data in it in MM and the latest Android client says, that my server version 5.3.1 may be to old. Ok, I agree 😉 – long time ago! I’ve tried to upgrade three times in the past and after each upgrade the service mattermost doesn’t start. But I was able to restore each time my MM version 5.3.1 correctly.

I’ve upgraded with this tutorial:  
[https://docs.mattermost.com/administration/upgrade.html?src=dl](https://docs.mattermost.com/administration/upgrade.html?src=dl)

My server:

- Ubuntu 16.04.7 LTS
- Apache 2.4.18
- PHP 7.2.33-1
- MariaDB 10.0.38
- https over own LetsEncrypt certificate

Another upgrade tutorial ([Redirect](https://docs.mattermost.com/administration/legacy-upgrade.html)) speaks about two version depending files, but I’ve neither the one not the other installed:

“RHEL6 and Ubuntu installations must verify the line limit nofile 50000 50000 is included in /etc/init/mattermost.conf file. See the installation guide for your operating system for more details.  
RHEL7 and Ubuntu installations must verify the line LimitNOFILE=49152 is included in the /etc/systemd/system/mattermost.service file. See the installation guide for your operating system for more details.”

I already have searched for this issue (so it’s probably possible) in this forum but nothing helpful found.

Any idea why my mattermost service doesn’t start after upgrade?

---

<div class="post-metadata">

**Author:** ![andrew.bimba](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/andrew.bimba/32/4064_2.png) [@andrew.bimba](https://forum.mattermost.com/u/andrew.bimba)\
**Post date:** [August 12, 2020, 4:41am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/2 "2020-08-12T04:41:49Z")

</div>

Hi @SuziQ,

For your version of _Ubuntu_, the depending file you are referring to is located at `/lib/systemd/system/mattermost.service`. Kindly check the file and verify `LimitNOFILE=49152`. If the file doesn’t exists you could follow the steps in [Setup Mattermost to use systemd](https://docs.mattermost.com/install/install-ubuntu-1604.html#installing-mattermost-server)

In case, the _mattermost_ service is properly configured and the service doesn’t start after the _upgrade_ could you execute this command `journalctl -u mattermost` and provide the output.

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 12, 2020, 9:36am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/3 "2020-08-12T09:36:14Z")

</div>

Hello Andrew,

thank you for your answer and writing the correct file name. Yeah, I have found this file and also the “LimitNOFILE=49152” statement is/was already present. Here’s the content of my /lib/systemd/system/mattermost.service:

> [Unit]  
> Description=Mattermost  
> After=network.target  
> After=mysql.service  
> Requires=mysql.service
> 
> [Service]  
> Type=simple  
> ExecStart=/opt/mattermost/bin/platform  
> Restart=always  
> RestartSec=10  
> WorkingDirectory=/opt/mattermost  
> User=mattermost  
> Group=mattermost  
> LimitNOFILE=49152
> 
> [Install]  
> WantedBy=multi-user.target

I assume that it’s neccessary to write you the ouput of “journalctl -u mattermost”, but I can do so not before evening/night, if nobody is working in MM. Till later …

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 12, 2020, 4:07pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/4 "2020-08-12T16:07:39Z")

</div>

Hello Andrew,

now I#ve done my upgrade try again and here’s the ouput of journalctl -u mattermost:

> # journalctl -u mattermost
> 
> – Logs begin at Mit 2020-08-12 16:05:53 CEST, end at Mit 2020-08-12 18:02:10 CEST. –  
> Aug 12 17:57:39 SERVER systemd[1]: Stopping Mattermost…  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.6628118,“caller”:“jobs/schedulers.go:136”,“msg”:"Stopping  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.684691,“caller”:“jobs/schedulers.go:71”,“msg”:"Schedulers  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.6865828,“caller”:“jobs/workers.go:170”,“msg”:"Stopped work  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.6868086,“caller”:“app/app.go:264”,“msg”:"Stopping Server…  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.693552,“caller”:“app/web\_hub.go:120”,“msg”:"stopping webso  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.7227626,“caller”:“app/plugin.go:156”,“msg”:"Shutting down  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“warn”,“ts”:1597247859.7291183,“caller”:“go-plugin/client.go:371”,“msg”:"error cl  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.735353,“caller”:“sqlstore/supplier.go:797”,“msg”:"Closing  
> Aug 12 17:57:39 SERVER platform[6833]: {“level”:“info”,“ts”:1597247859.7381942,“caller”:“app/app.go:285”,“msg”:“Server stopped”}  
> Aug 12 17:57:39 SERVER systemd[1]: Stopped Mattermost.  
> Aug 12 18:01:43 SERVER systemd[1]: Started Mattermost.  
> Aug 12 18:01:43 SERVER platform[9059]: ------------------------------------ ERROR -----------------------------------------------  
> Aug 12 18:01:43 SERVER platform[9059]: The platform binary has been deprecated, please switch to using the new mattermost binary.  
> Aug 12 18:01:43 SERVER platform[9059]: The platform binary will be removed in a future version.  
> Aug 12 18:01:43 SERVER platform[9059]: ------------------------------------------------------------------------------------------  
> Aug 12 18:01:43 SERVER platform[9059]:  
> Aug 12 18:01:43 SERVER platform[9059]: {“level”:“info”,“ts”:1597248103.3753557,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system t  
> Aug 12 18:01:43 SERVER platform[9059]: {“level”:“info”,“ts”:1597248103.3759367,“caller”:“app/server\_app\_adapters.go:58”,“msg”:"Se  
> Aug 12 18:01:43 SERVER platform[9059]: {“level”:“info”,“ts”:1597248103.3787365,“caller”:“sqlstore/supplier.go:227”,“msg”:"Pinging  
> Aug 12 18:01:43 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248103.8251693,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.0026808,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.003777,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attemptin  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.0080054,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.0087283,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.076553,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The datab  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.077548,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attemptin  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.0824,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The databas  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.0831192,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.3862062,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.3865883,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.389081,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The datab  
> Aug 12 18:01:44 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248104.3893828,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.0307164,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.0311134,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.0343084,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.034637,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attemptin  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1856031,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1860185,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1895509,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1898494,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1923711,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1926734,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.1941507,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.194418,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attemptin  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.2519264,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3261428,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3302298,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3307269,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3336015,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3340073,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3369105,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3373084,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3615177,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3620079,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3645556,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.3649511,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.450795,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The datab  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.4514832,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.4543526,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.4549468,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.5104742,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.5109668,“caller”:“sqlstore/upgrade.go:200”,“msg”:"Attempti  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“warn”,“ts”:1597248105.5138142,“caller”:“sqlstore/upgrade.go:195”,“msg”:"The data  
> Aug 12 18:01:45 SERVER platform[9059]: {“level”:“error”,“ts”:1597248105.8609264,“caller”:“sqlstore/supplier.go:915”,“msg”:"Failed  
> Aug 12 18:01:46 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=119/n/a  
> Aug 12 18:01:46 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 12 18:01:46 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 12 18:01:57 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 12 18:01:57 SERVER systemd[1]: Stopped Mattermost.  
> Aug 12 18:01:57 SERVER systemd[1]: Started Mattermost.  
> Aug 12 18:01:57 SERVER platform[9111]: ------------------------------------ ERROR -----------------------------------------------  
> Aug 12 18:01:57 SERVER platform[9111]: The platform binary has been deprecated, please switch to using the new mattermost binary.  
> Aug 12 18:01:57 SERVER platform[9111]: The platform binary will be removed in a future version.  
> Aug 12 18:01:57 SERVER platform[9111]: ------------------------------------------------------------------------------------------  
> Aug 12 18:01:57 SERVER platform[9111]:  
> Aug 12 18:01:57 SERVER platform[9111]: {“level”:“info”,“ts”:1597248117.3420393,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system t  
> Aug 12 18:01:57 SERVER platform[9111]: {“level”:“info”,“ts”:1597248117.3424163,“caller”:“app/server\_app\_adapters.go:58”,“msg”:"Se  
> Aug 12 18:01:57 SERVER platform[9111]: {“level”:“info”,“ts”:1597248117.3453321,“caller”:“sqlstore/supplier.go:227”,“msg”:"Pinging  
> Aug 12 18:01:57 SERVER platform[9111]: {“level”:“error”,“ts”:1597248117.397832,“caller”:“sqlstore/supplier.go:915”,“msg”:"Failed  
> Aug 12 18:01:58 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=119/n/a  
> Aug 12 18:01:58 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 12 18:01:58 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 12 18:02:08 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 12 18:02:08 SERVER systemd[1]: Stopped Mattermost.  
> Aug 12 18:02:08 SERVER systemd[1]: Started Mattermost.  
> Aug 12 18:02:08 SERVER platform[9166]: ------------------------------------ ERROR -----------------------------------------------  
> Aug 12 18:02:08 SERVER platform[9166]: The platform binary has been deprecated, please switch to using the new mattermost binary.  
> Aug 12 18:02:08 SERVER platform[9166]: The platform binary will be removed in a future version.  
> Aug 12 18:02:08 SERVER platform[9166]: ------------------------------------------------------------------------------------------  
> Aug 12 18:02:08 SERVER platform[9166]:  
> Aug 12 18:02:08 SERVER platform[9166]: {“level”:“info”,“ts”:1597248128.855694,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system tr  
> Aug 12 18:02:08 SERVER platform[9166]: {“level”:“info”,“ts”:1597248128.8559012,“caller”:“app/server\_app\_adapters.go:58”,“msg”:"Se  
> Aug 12 18:02:08 SERVER platform[9166]: {“level”:“info”,“ts”:1597248128.8618877,“caller”:“sqlstore/supplier.go:227”,“msg”:"Pinging  
> Aug 12 18:02:08 SERVER platform[9166]: {“level”:“error”,“ts”:1597248128.9169214,“caller”:“sqlstore/supplier.go:915”,“msg”:"Failed  
> Aug 12 18:02:09 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=119/n/a  
> Aug 12 18:02:09 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 12 18:02:09 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.

Thanks for your support in advance.  
Suzi

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 12, 2020, 5:19pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/5 "2020-08-12T17:19:52Z")

</div>

Aaarrrgghhh, but now, MM doesn’t start with my backup (DB and MM from my NAS) from yesterday, while all teams was working today with MM (next backup this night).

Here’s the last ouput from “journalctl -u mattermost”:

> # journalctl -u mattermost
> 
> – Logs begin at Mit 2020-08-12 19:18:06 CEST, end at Mit 2020-08-12 19:18:50 CEST. –  
> Aug 12 19:18:14 SERVER systemd[1]: Started Mattermost.  
> Aug 12 19:18:14 SERVER platform[3347]: ------------------------------------ ERROR -----------------------------------------------  
> Aug 12 19:18:14 SERVER platform[3347]: The platform binary has been deprecated, please switch to using the new mattermost binary.  
> Aug 12 19:18:14 SERVER platform[3347]: The platform binary will be removed in a future version.  
> Aug 12 19:18:14 SERVER platform[3347]: ------------------------------------------------------------------------------------------  
> Aug 12 19:18:14 SERVER platform[3347]:  
> Aug 12 19:18:17 SERVER platform[3347]: {“level”:“info”,“ts”:1597252697.0997727,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system t  
> Aug 12 19:18:17 SERVER platform[3347]: {“level”:“info”,“ts”:1597252697.1053228,“caller”:“app/app.go:195”,“msg”:"Server is initial  
> Aug 12 19:18:17 SERVER platform[3347]: {“level”:“info”,“ts”:1597252697.1331873,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pinging  
> Aug 12 19:18:17 SERVER platform[3347]: {“level”:“error”,“ts”:1597252697.182437,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Database  
> Aug 12 19:18:18 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 12 19:18:18 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 12 19:18:18 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 12 19:18:28 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 12 19:18:28 SERVER systemd[1]: Stopped Mattermost.  
> Aug 12 19:18:28 SERVER systemd[1]: Started Mattermost.  
> Aug 12 19:18:28 SERVER platform[4606]: ------------------------------------ ERROR -----------------------------------------------  
> Aug 12 19:18:28 SERVER platform[4606]: The platform binary has been deprecated, please switch to using the new mattermost binary.  
> Aug 12 19:18:28 SERVER platform[4606]: The platform binary will be removed in a future version.  
> Aug 12 19:18:28 SERVER platform[4606]: ------------------------------------------------------------------------------------------  
> Aug 12 19:18:28 SERVER platform[4606]:  
> Aug 12 19:18:29 SERVER platform[4606]: {“level”:“info”,“ts”:1597252709.0250037,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system t  
> Aug 12 19:18:29 SERVER platform[4606]: {“level”:“info”,“ts”:1597252709.0251403,“caller”:“app/app.go:195”,“msg”:"Server is initial  
> Aug 12 19:18:29 SERVER platform[4606]: {“level”:“info”,“ts”:1597252709.028808,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pinging  
> Aug 12 19:18:29 SERVER platform[4606]: {“level”:“error”,“ts”:1597252709.0976717,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Databas  
> Aug 12 19:18:30 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 12 19:18:30 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 12 19:18:30 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 12 19:18:40 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 12 19:18:40 SERVER systemd[1]: Stopped Mattermost.  
> Aug 12 19:18:40 SERVER systemd[1]: Started Mattermost.  
> Aug 12 19:18:40 SERVER platform[4958]: ------------------------------------ ERROR -----------------------------------------------  
> Aug 12 19:18:40 SERVER platform[4958]: The platform binary has been deprecated, please switch to using the new mattermost binary.  
> Aug 12 19:18:40 SERVER platform[4958]: The platform binary will be removed in a future version.  
> Aug 12 19:18:40 SERVER platform[4958]: ------------------------------------------------------------------------------------------  
> Aug 12 19:18:40 SERVER platform[4958]:  
> Aug 12 19:18:41 SERVER platform[4958]: {“level”:“info”,“ts”:1597252721.9271123,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system t  
> Aug 12 19:18:41 SERVER platform[4958]: {“level”:“info”,“ts”:1597252721.932932,“caller”:“app/app.go:195”,“msg”:"Server is initiali  
> Aug 12 19:18:41 SERVER platform[4958]: {“level”:“info”,“ts”:1597252721.956258,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pinging  
> Aug 12 19:18:42 SERVER platform[4958]: {“level”:“error”,“ts”:1597252722.1016095,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Databas  
> Aug 12 19:18:43 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 12 19:18:43 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 12 19:18:43 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.

---

<div class="post-metadata">

**Author:** ![andrew.bimba](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/andrew.bimba/32/4064_2.png) [@andrew.bimba](https://forum.mattermost.com/u/andrew.bimba)\
**Post date:** [August 12, 2020, 10:10pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/6 "2020-08-12T22:10:17Z")

</div>

Hi @SuziQ,

Could you update the `ExecStart` property of the `/lib/systemd/system/mattermost.service` file as shown below:  
`ExecStart=/opt/mattermost/bin/mattermost`

Note:

If you have installed MySQL on a dedicated server, then you need to

> - remove `After=postgresql.service` and `BindsTo=postgresql.service` or `After=mysql.service` and `BindsTo=mysql.service` lines in the `[Unit]` section, and
> - replace the `WantedBy=postgresql.service` or `WantedBy=mysql.service` line in the `[Install]` section with `WantedBy=multi-user.target`

or the Mattermost service will not start.

After the changes, do the following:

1. Make systemd load the new unit.

2. Check to make sure that the unit was loaded.

3. Start the service.

4. If _Mattermost_ starts successfully, set _Mattermost_ to start on machine start up.

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 13, 2020, 9:35am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/7 "2020-08-13T09:35:24Z")

</div>

Hello Andrew,

thank you for your suggestions. My MariaDB is on the same machine like MM. So I’ve also changed the [Install] line “WantedBy=multi-user.target” to “WantedBy=mysql.service” and hope that was correct. Here’s my current file /lib/systemd/system/mattermost.service:

> [Unit]  
> Description=Mattermost  
> After=network.target  
> After=mysql.service  
> Requires=mysql.service
> 
> [Service]  
> Type=simple  
> ExecStart=/opt/mattermost/bin/mattermost  
> Restart=always  
> RestartSec=10  
> WorkingDirectory=/opt/mattermost  
> User=mattermost  
> Group=mattermost  
> LimitNOFILE=49152
> 
> [Install]  
> WantedBy=mysql.service

`systemctl daemon-reload` runs okay, but `systemctl status mattermost.service` does not! Here the output:

> # systemctl status mattermost.service
> 
> ● mattermost.service - Mattermost  
> Loaded: loaded (/lib/systemd/system/mattermost.service; enabled; vendor preset: enabled)  
> Active: activating (auto-restart) (Result: exit-code) since Don 2020-08-13 11:29:13 CEST; 8s ago  
> Process: 16608 ExecStart=/opt/mattermost/bin/mattermost (code=exited, status=234/MAKE\_STARTER)  
> Main PID: 16608 (code=exited, status=234/MAKE\_STARTER)
> 
> Aug 13 11:29:13 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 13 11:29:13 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.

So `systemctl start mattermost.service` doesn’t start … ☹ ☹ ☹

---

<div class="post-metadata">

**Author:** ![andrew.bimba](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/andrew.bimba/32/4064_2.png) [@andrew.bimba](https://forum.mattermost.com/u/andrew.bimba)\
**Post date:** [August 14, 2020, 12:11am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/8 "2020-08-14T00:11:11Z")

</div>

Hi @SuziQ,

Can you switch to your last working backup and perform the upgrade again, using the steps provided below:

> cd /tmp  
> wget [https://releases.mattermost.com/5.25.2/mattermost-5.25.2-linux-amd64.tar.gz](https://releases.mattermost.com/5.25.2/mattermost-5.25.2-linux-amd64.tar.gz)  
> tar -xzf mattermost\*.gz  
> cp -R /opt/mattermost/config/\* /tmp/mattermost/config/  
> sudo su  
> mv /opt/mattermost/data /tmp/mattermost/data  
> rsync -au /opt/mattermost/plugins/ /tmp/mattermost/plugins  
> rsync -au /opt/mattermost/client/plugins/ /tmp/mattermost/client/plugins  
> systemctl stop mattermost  
> mv /opt/mattermost /opt/old.mattermost  
> mv /tmp/mattermost /opt/mattermost  
> chown -R mattermost:mattermost /opt/mattermost  
> (If you have setup TLS) sudo setcap cap\_net\_bind\_service=+ep ./bin/mattermost  
> systemctl start mattermost  
> **Confirm Mattermost is working**  
> rm /tmp/mattermost\*.gz  
> rm -rf /opt/old.mattermost/

If the issue persists, provide the output of `journalctl -u mattermost` and any errors in the `/opt/mattermost/logs/mattermost.log` file

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 14, 2020, 12:50pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/9 "2020-08-14T12:50:35Z")

</div>

Hello Andrew,

I’m already talking about my last working backup. Current data (MM+DB) are all from the day before yesterday. And now the MM service doesn’t start. I’d be happy if this old MM comes up.

That’s the output from journalctl -u mattermost after server restart:

> # journalctl -u mattermost
> 
> – Logs begin at Fre 2020-08-14 14:39:22 CEST, end at Fre 2020-08-14 14:42:42 CEST. –  
> Aug 14 14:39:45 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:39:49 SERVER mattermost[2991]: {“level”:“info”,“ts”:1597408789.6726403,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:39:49 SERVER mattermost[2991]: {“level”:“info”,“ts”:1597408789.6937063,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:39:49 SERVER mattermost[2991]: {“level”:“info”,“ts”:1597408789.9588451,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:39:50 SERVER mattermost[2991]: {“level”:“error”,“ts”:1597408790.3341799,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:39:51 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:39:51 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:39:51 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:40:01 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:40:01 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:40:01 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:40:04 SERVER mattermost[4516]: {“level”:“info”,“ts”:1597408804.544298,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:40:04 SERVER mattermost[4516]: {“level”:“info”,“ts”:1597408804.5444705,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:40:04 SERVER mattermost[4516]: {“level”:“info”,“ts”:1597408804.5665936,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:40:04 SERVER mattermost[4516]: {“level”:“error”,“ts”:1597408804.6717236,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:40:05 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:40:05 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:40:05 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:40:15 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:40:15 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:40:15 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:40:17 SERVER mattermost[4812]: {“level”:“info”,“ts”:1597408817.3393323,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:40:17 SERVER mattermost[4812]: {“level”:“info”,“ts”:1597408817.3399246,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:40:17 SERVER mattermost[4812]: {“level”:“info”,“ts”:1597408817.342036,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingin  
> Aug 14 14:40:17 SERVER mattermost[4812]: {“level”:“error”,“ts”:1597408817.428405,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Databa  
> Aug 14 14:40:18 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:40:18 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:40:18 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:40:28 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:40:28 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:40:28 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:40:29 SERVER mattermost[4944]: {“level”:“info”,“ts”:1597408829.6034358,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:40:29 SERVER mattermost[4944]: {“level”:“info”,“ts”:1597408829.6036122,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:40:29 SERVER mattermost[4944]: {“level”:“info”,“ts”:1597408829.6055126,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:40:29 SERVER mattermost[4944]: {“level”:“error”,“ts”:1597408829.7044616,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:40:30 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:40:30 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:40:30 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:40:40 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:40:40 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:40:40 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:40:41 SERVER mattermost[5365]: {“level”:“info”,“ts”:1597408841.7379692,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:40:41 SERVER mattermost[5365]: {“level”:“info”,“ts”:1597408841.740226,“caller”:“app/app.go:195”,“msg”:"Server is initia  
> Aug 14 14:40:41 SERVER mattermost[5365]: {“level”:“info”,“ts”:1597408841.7878056,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:40:41 SERVER mattermost[5365]: {“level”:“error”,“ts”:1597408841.9906845,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:40:42 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:40:42 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:40:42 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:40:53 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:40:53 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:40:53 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:40:54 SERVER mattermost[5438]: {“level”:“info”,“ts”:1597408854.4683843,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:40:54 SERVER mattermost[5438]: {“level”:“info”,“ts”:1597408854.533212,“caller”:“app/app.go:195”,“msg”:"Server is initia  
> Aug 14 14:40:54 SERVER mattermost[5438]: {“level”:“info”,“ts”:1597408854.6163955,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:40:54 SERVER mattermost[5438]: {“level”:“error”,“ts”:1597408854.9739115,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:40:56 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:40:56 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:40:56 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:41:06 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:41:06 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:41:06 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:41:06 SERVER mattermost[5549]: {“level”:“info”,“ts”:1597408866.6937475,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:41:06 SERVER mattermost[5549]: {“level”:“info”,“ts”:1597408866.6956265,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:41:06 SERVER mattermost[5549]: {“level”:“info”,“ts”:1597408866.70862,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pinging  
> Aug 14 14:41:06 SERVER mattermost[5549]: {“level”:“error”,“ts”:1597408866.751742,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Databa  
> Aug 14 14:41:07 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:41:07 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:41:07 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:41:17 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:41:17 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:41:18 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:41:18 SERVER mattermost[6556]: {“level”:“info”,“ts”:1597408878.6111135,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:41:18 SERVER mattermost[6556]: {“level”:“info”,“ts”:1597408878.6148312,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:41:18 SERVER mattermost[6556]: {“level”:“info”,“ts”:1597408878.6188948,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:41:18 SERVER mattermost[6556]: {“level”:“error”,“ts”:1597408878.6514099,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:41:19 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:41:19 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:41:19 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:41:29 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:41:29 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:41:29 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:41:30 SERVER mattermost[7021]: {“level”:“info”,“ts”:1597408890.417672,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:41:30 SERVER mattermost[7021]: {“level”:“info”,“ts”:1597408890.4198797,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:41:30 SERVER mattermost[7021]: {“level”:“info”,“ts”:1597408890.4311087,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:41:30 SERVER mattermost[7021]: {“level”:“error”,“ts”:1597408890.4878302,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:41:31 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:41:31 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:41:31 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:41:41 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:41:41 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:41:41 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:41:42 SERVER mattermost[7156]: {“level”:“info”,“ts”:1597408902.0489345,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:41:42 SERVER mattermost[7156]: {“level”:“info”,“ts”:1597408902.0499895,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:41:42 SERVER mattermost[7156]: {“level”:“info”,“ts”:1597408902.0685785,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:41:42 SERVER mattermost[7156]: {“level”:“error”,“ts”:1597408902.0857158,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:41:43 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:41:43 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:41:43 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:41:53 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:41:53 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:41:53 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:41:53 SERVER mattermost[7305]: {“level”:“info”,“ts”:1597408913.4748929,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:41:53 SERVER mattermost[7305]: {“level”:“info”,“ts”:1597408913.4751213,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:41:53 SERVER mattermost[7305]: {“level”:“info”,“ts”:1597408913.4771538,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:41:53 SERVER mattermost[7305]: {“level”:“error”,“ts”:1597408913.500497,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Databa  
> Aug 14 14:41:54 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:41:54 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:41:54 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:42:04 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:42:04 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:42:04 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:42:04 SERVER mattermost[7336]: {“level”:“info”,“ts”:1597408924.9746943,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:42:04 SERVER mattermost[7336]: {“level”:“info”,“ts”:1597408924.9749923,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:42:04 SERVER mattermost[7336]: {“level”:“info”,“ts”:1597408924.9772296,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:42:05 SERVER mattermost[7336]: {“level”:“error”,“ts”:1597408925.0048046,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:42:06 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:42:06 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:42:06 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:42:16 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:42:16 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:42:16 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:42:16 SERVER mattermost[7355]: {“level”:“info”,“ts”:1597408936.7439735,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:42:16 SERVER mattermost[7355]: {“level”:“info”,“ts”:1597408936.7446935,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:42:16 SERVER mattermost[7355]: {“level”:“info”,“ts”:1597408936.7466884,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:42:16 SERVER mattermost[7355]: {“level”:“error”,“ts”:1597408936.7858453,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:42:17 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:42:17 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:42:17 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:42:27 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:42:27 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:42:28 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:42:28 SERVER mattermost[7375]: {“level”:“info”,“ts”:1597408948.251719,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:42:28 SERVER mattermost[7375]: {“level”:“info”,“ts”:1597408948.2519524,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:42:28 SERVER mattermost[7375]: {“level”:“info”,“ts”:1597408948.254036,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingin  
> Aug 14 14:42:28 SERVER mattermost[7375]: {“level”:“error”,“ts”:1597408948.2745166,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:42:29 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:42:29 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:42:29 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.  
> Aug 14 14:42:39 SERVER systemd[1]: mattermost.service: Service hold-off time over, scheduling restart.  
> Aug 14 14:42:39 SERVER systemd[1]: Stopped Mattermost.  
> Aug 14 14:42:39 SERVER systemd[1]: Started Mattermost.  
> Aug 14 14:42:39 SERVER mattermost[7425]: {“level”:“info”,“ts”:1597408959.764309,“caller”:“utils/i18n.go:83”,“msg”:"Loaded system  
> Aug 14 14:42:39 SERVER mattermost[7425]: {“level”:“info”,“ts”:1597408959.7646663,“caller”:“app/app.go:195”,“msg”:"Server is initi  
> Aug 14 14:42:39 SERVER mattermost[7425]: {“level”:“info”,“ts”:1597408959.7677455,“caller”:“sqlstore/supplier.go:200”,“msg”:"Pingi  
> Aug 14 14:42:39 SERVER mattermost[7425]: {“level”:“error”,“ts”:1597408959.7885208,“caller”:“sqlstore/upgrade.go:102”,“msg”:"Datab  
> Aug 14 14:42:40 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=234/MAKE\_STARTER  
> Aug 14 14:42:40 SERVER systemd[1]: mattermost.service: Unit entered failed state.  
> Aug 14 14:42:40 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.

And that’s `tail -30 /opt/mattermost/logs/mattermost.log`:

> # tail -30 /opt/mattermost/logs/mattermost.log
> 
> {“level”:“info”,“ts”:1597409198.9529328,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409198.9775841,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409210.2409937,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409210.2415547,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409210.2437673,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409210.2696326,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409221.7348754,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409221.7353294,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409221.7371235,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409221.761478,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409233.2113864,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409233.2116344,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409233.2142634,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409233.236406,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409244.68401,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409244.6844773,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409244.686594,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409244.7139657,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409255.979219,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409255.9796798,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409255.9818783,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409256.0009825,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409267.4437156,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409267.444194,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409267.446112,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409267.4649324,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}  
> {“level”:“info”,“ts”:1597409278.6988301,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}  
> {“level”:“info”,“ts”:1597409278.6995258,“caller”:“app/app.go:195”,“msg”:“Server is initializing…”}  
> {“level”:“info”,“ts”:1597409278.7018223,“caller”:“sqlstore/supplier.go:200”,“msg”:“Pinging SQL master database”}  
> {“level”:“error”,“ts”:1597409278.7252653,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}

It would be more than great if MM comes up in old version. And than we are discuss the next step 😉  
Best regards.

---

<div class="post-metadata">

**Author:** ![andrew.bimba](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/andrew.bimba/32/4064_2.png) [@andrew.bimba](https://forum.mattermost.com/u/andrew.bimba)\
**Post date:** [August 15, 2020, 12:53am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/10 "2020-08-15T00:53:40Z")

</div>

@SuziQ

> {“level”:“error”,“ts”:1597409198.9775841,“caller”:“sqlstore/upgrade.go:102”,“msg”:“Database schema version 5.25.0 is no longer supported. This Mattermost server supports automatic upgrades from schema version 3.0.0 through schema version 5.3.0. Downgrades are not supported. Please manually upgrade to at least version 3.0.0 before continuing”}

The error indicates that you’re trying to _start_ your old instance _Version 5.3.1_ while you’re connected to a database that has already been upgrade to Version _5.25.0_.

Start the _old instance_ while it is connected to the _old_ backed up database.

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [August 15, 2020, 1:46pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/11 "2020-08-15T13:46:06Z")

</div>

Upppsss, I’m an idiot, I’ve restored the wrong \*.sql file. Many thanks, Andrew. Now MM already runs in old version 5.3.1 … 👏  
Next step is upgrading like written above – but not today 😉  
I need some distance now 😉

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [December 28, 2020, 2:44pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/12 "2020-12-28T14:44:49Z")

</div>

Hello Andrew,

now I have tried the update twice again now. Unfortunately, I still have had no success with it.

What I have done:

# get mm

cd /opt  
mkdir tmp  
cd tmp  
wget [https://releases.mattermost.com/5.30.1/mattermost-5.30.1-linux-amd64.tar.gz](https://releases.mattermost.com/5.30.1/mattermost-5.30.1-linux-amd64.tar.gz)  
tar -xzf mattermost\*.gz

# keep current mm config

rsync -a /opt/mattermost/config/ mattermost/config/ # rsync to keep write access!

# stop mm daemon

systemctl stop mattermost

# backup current mm state

cd … # now in /opt  
rsync -a mattermost/ mm.bak  
mysqldump -u root -p mattermost \> mm.sql

# keep current mm data

rsync -a mattermost/data tmp/mattermost/data  
rsync -au mattermost/plugins/ tmp/mattermost/plugins  
rsync -au mattermost/client/plugins/ tmp/mattermost/client/plugins

# replace old mm install

mv mattermost mattermost.OLD  
mv tmp/mattermost mattermost  
chown -R mattermost:mattermost mattermost

# if you have setup TLS

sudo setcap cap\_net\_bind\_service=+ep mattermost/bin/mattermost

# start/check mm daemon

systemctl start mattermost  
systemctl status mattermost

## The status result is:

root@SERVER:/opt# 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 Mon 2020-12-28 15:04:40 CET; 1s ago  
Process: 26378 ExecStart=/opt/mattermost/bin/mattermost (code=exited, status=119)  
Main PID: 26378 (code=exited, status=119)

## Dez 28 15:04:40 SERVER systemd[1]: mattermost.service: Main process exited, code=exited, status=119/n/a Dez 28 15:04:40 SERVER systemd[1]: mattermost.service: Unit entered failed state. Dez 28 15:04:40 SERVER systemd[1]: mattermost.service: Failed with result ‘exit-code’.

My server:

- Ubuntu Server 16.04.7 LTS
- Database: MariaDB (Ver 15.1 Distrib 10.0.38-MariaDB)
- Mattermost database schema: 5.3.0

Are you able to see what’s going wrong with my update?

---

<div class="post-metadata">

**Author:** ![XxLilBoPeepsxX](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/xxlilbopeepsxx/32/4993_2.png) [@XxLilBoPeepsxX](https://forum.mattermost.com/u/XxLilBoPeepsxX)\
**Post date:** [December 29, 2020, 1:26am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/13 "2020-12-29T01:26:11Z")

</div>

Hello! Could you provide the output of `journalctl -xe -t mattermost`?  
This will provide specifics of the issues related to mattermost, and only log entries that are classified as errors or

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [December 29, 2020, 12:54pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/14 "2020-12-29T12:54:41Z")

</div>

Hello!  
Currently my old MM version 5.3.1 is running again. Apparently there are no entries here.

root@SERVER:/opt# journalctl -xe -t mattermost  
– No entries –  
root@SERVER:/opt#

---

<div class="post-metadata">

**Author:** ![XxLilBoPeepsxX](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/xxlilbopeepsxx/32/4993_2.png) [@XxLilBoPeepsxX](https://forum.mattermost.com/u/XxLilBoPeepsxX)\
**Post date:** [January 1, 2021, 4:01pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/15 "2021-01-01T16:01:56Z")

</div>

Well, that is quite interesting given that it should be logged under the name of the service. Maybe it’s because your not on the same operating system as myself, which would be understandable.

I’m interested to hear, how were you able to get the instance running again?

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [January 1, 2021, 7:35pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/16 "2021-01-01T19:35:38Z")

</div>

Hello,

is there another log file I could check?

Well, I proceeded as follows (from non-functioning version 5.30.1):

# remove dead mm v5.30.1 installation

rm -r /opt/mattermost

# remove all database tables without database itself using phpMyAdmin

# restore mm database

mysql -u root -p mattermost \< /opt/mm.sql

# restore mm program folder (v5.3.1)

rsync -a /opt/mm.bak/ /opt/mattermost

# start mm daemon

systemctl start mattermost  
systemctl status mattermost

● mattermost.service - Mattermost  
Loaded: loaded (/lib/systemd/system/mattermost.service; enabled; vendor preset: enabled)  
Active: active (running) since Mon 2020-12-28 16:51:12 CET; 4 days ago  
Main PID: 32330 (mattermost)  
Tasks: 26 (limit: 65000)  
Memory: 43.2M  
CPU: 6min 130ms  
CGroup: /system.slice/mattermost.service  
├─32330 /opt/mattermost/bin/mattermost  
└─32341 plugins/jira/plugin.exe

# remove unused files

rm /opt/mm.bak  
rm /opt/mm.sql

In the meantime I’ve moved my mm data directory outside of the installation to /opt/mattermost.data.

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [January 1, 2021, 8:04pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/17 "2021-01-01T20:04:22Z")

</div>

![Bildschirmfoto vom 2021-01-01 21-03-10](https://us1.discourse-cdn.com/flex020/uploads/mattermost/original/2X/3/3e77f5667f6651bef9c9015fa9143d3a2e906b80.png)

I also like to completely reinstall version 5.30.1.  
The problem is I would like to keep the previous data 😉

---

<div class="post-metadata">

**Author:** ![XxLilBoPeepsxX](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/xxlilbopeepsxx/32/4993_2.png) [@XxLilBoPeepsxX](https://forum.mattermost.com/u/XxLilBoPeepsxX)\
**Post date:** [January 3, 2021, 3:25am UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/18 "2021-01-03T03:25:04Z")

</div>

@ahmaddanial it seems like this is something that is a reoccurring issue between at least the two people here, potentially this is a bigger issue? Would you be able to provide a bit of insight into what details we should take a look at further in-depth, by any chance?

---

<div class="post-metadata">

**Author:** ![SuziQ](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/suziq/32/6751_2.png) [@SuziQ](https://forum.mattermost.com/u/SuziQ)\
**Post date:** [January 12, 2021, 10:26pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/19 "2021-01-12T22:26:56Z")

</div>

HI, is there any chance for my upgrade?

---

<div class="post-metadata">

**Author:** ![ahmaddanial](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ahmaddanial/32/2938_2.png) [@ahmaddanial](https://forum.mattermost.com/u/ahmaddanial)\
**Post date:** [January 13, 2021, 3:07pm UTC](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/20 "2021-01-13T15:07:36Z")

</div>

Hello, @SuziQ

Upgrading from an older version is definitely a tricky issue. Nevertheless, I have assisted upgrades from older version based on steps that was shared by @andrew.bimba [earlier](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266/8):

```auto
cd /tmp
wget https://releases.mattermost.com/5.25.2/mattermost-5.25.2-linux-amd64.tar.gz
tar -xzf mattermost*.gz
cp -R /opt/mattermost/config/* /tmp/mattermost/config/
sudo su
mv /opt/mattermost/data /tmp/mattermost/data
rsync -au /opt/mattermost/plugins/ /tmp/mattermost/plugins
rsync -au /opt/mattermost/client/plugins/ /tmp/mattermost/client/plugins
systemctl stop mattermost
mv /opt/mattermost /opt/old.mattermost
mv /tmp/mattermost /opt/mattermost
chown -R mattermost:mattermost /opt/mattermost
(If you have setup TLS) sudo setcap cap_net_bind_service=+ep ./bin/mattermost
systemctl start mattermost
Confirm Mattermost is working
rm /tmp/mattermost*.gz
rm -rf /opt/old.mattermost/

```

Since we are facing issues with the `mattermost.service`, can you please let me know if you are able to remove the configured service and start the instance manually using this command:

```auto
sudo -u mattermost ./bin/mattermost

```

instead of using the service after you completed the upgrade?

As the error kept on pointing to the service, I want to isolate if we miss out anything on the upgrade steps itself.

On a side note, I can see that there is an additional `Requires=mysql.service` line in your `mattermost.service`. Is that intended instead of using `BindsTo=mysql.service`?

```auto
[Unit]
Description=Mattermost
After=network.target
After=mysql.service
Requires=mysql.service

[Service]
Type=simple
ExecStart=/opt/mattermost/bin/mattermost
Restart=always
RestartSec=10
WorkingDirectory=/opt/mattermost
User=mattermost
Group=mattermost
LimitNOFILE=49152

[Install]
WantedBy=mysql.service

```

With comparison to the one in the [documentation](https://docs.mattermost.com/install/install-ubuntu-1804.html#installing-ubuntu-server-18-04-lts) in step 10b:

```auto
[Unit]
Description=Mattermost
After=network.target
After=mysql.service
BindsTo=mysql.service

[Service]
Type=notify
ExecStart=/opt/mattermost/bin/mattermost
TimeoutStartSec=3600
Restart=always
RestartSec=10
WorkingDirectory=/opt/mattermost
User=mattermost
Group=mattermost
LimitNOFILE=49152

[Install]
WantedBy=mysql.service

```

The reason why I am checking on this is because of the difference between these directives tying back to the `mysql.service`:

- **`Requires=`** : This directive lists any units upon which this unit essentially depends. If the current unit is activated, the units listed here must successfully activate as well, else this unit will fail. These units are started in parallel with the current unit by default.
- **`BindsTo=`** : This directive is similar to `Requires=` , but also causes the current unit to stop when the associated unit terminates.

[Next page](https://forum.mattermost.com/t/upgrade-mm-5-3-1-to-latest-version-fails/10266.md?page=2)