Upgrade path from 7.8 to 10.3?

1

Hello,

In short, are there risks to upgrading directly from 7.8 to 10.3? If I need to follow an upgrade path instead of the direct upgrade, which versions do I need to upgrade to?

2

You’ll want to go to 8.1 (the next ESR), then 9.5, then 9.11

https://docs.mattermost.com/about/release-policy.html#legacy-releases

1 Like
3

Hello,

I am returning to this, and am encountering issues.

First, it seems 8.1 is no longer the next ESR, is that correct?

Second, are there legacy installation/upgrade instructions? Basic things like the systemctl commands do not work, e.g.,

sudo systemctl start mattermost
Failed to start mattermost.service: Unit mattermost.service not found.

And when using alternative commands to start the server, the log shows a bunch of “Plugins have been disabled” errors, when config.json very much has them enabled. Examples of errors:

{“timestamp”:“2025-02-21 18:26:34.043 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}
{“timestamp”:“2025-02-21 18:26:43.220 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}
{“timestamp”:“2025-02-21 18:26:43.253 Z”,“level”:“info”,“msg”:“Plugins have been disabled. Please check your logs for details.”,“caller”:“web/context.go:115”,“path”:“/api/v4/plugins/webapp”,“request_id”:“oiwm9i41tjf7bxuez7s43jqdnw”,“ip_addr”:“10.150.2.108”,“user_id”:“ty3shy56h3ghmxewyqq3h9rtbh”,“method”:“GET”,“err_where”:“GetActivePluginManifests”,“http_code”:501,“error”:“GetActivePluginManifests: Plugins have been disabled. Please check your logs for details.”}
{“timestamp”:“2025-02-21 18:26:43.266 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}
{“timestamp”:“2025-02-21 18:26:43.271 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}
{“timestamp”:“2025-02-21 18:26:43.576 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}
{“timestamp”:“2025-02-21 18:26:43.621 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}
{“timestamp”:“2025-02-21 18:27:33.118 Z”,“level”:“error”,“msg”:“ServePluginRequest: Plugins have been disabled. Please check your logs for details., Enable plugins to serve plugin requests”,“caller”:“app/plugin_requests.go:34”}

4

If you’re still on 7.8.x, yes, 8.1.13 is the next ESR. You can find every version of Mattermost at Version archive - Mattermost documentation

How did you install 7.8? How is Mattermost getting started now? SysVinit scripts?

If you do something like sudo service mattermost start you should be able to just replace the mattermost directory with the instructions at Upgrade Mattermost Server - Mattermost documentation and have that still work. And those instructions have you just move the old install directory to the side, so you can reverse the upgrade.

You can enable DEBUG logging Mattermost logging - Mattermost documentation and watch your system & audit logs as well… this might be caused by something like SELinux, if during your upgrade the proper context labeling isn’t applied. Are you using RHEL? Is SELinux in enforcing more? sudo getenforce would tell you. Install Mattermost on RHEL - Mattermost documentation talks about getting Mattermost and SELinux coooperating.

1 Like