[SOLVED] Mattermost service automatically stops after some time


#1

Summary

Mattermost instance automatically stops, and I am unable to access mattermost anymore.
sudo systemctl status mattermost.service

Active: failed (Result: exit-code) since Wed 2018-01-10 10:34:52 UTC; 8min ago
this is the error when I check mattermost service status

then I run this command to restart it
sudo systemctl restart mattermost

Steps to reproduce

Mattermost Server version

Server OS Centos7

Version: 4.3.0
Build Number: 4.3.1
Build Date: Fri Oct 20 20:37:49 UTC 2017
Build Hash: c8a67ac3c95b11b6a3045905cd4f875f8ffd0fe8
Build Enterprise Ready: false
DB Version: 4.3.0


I don’t understand how does it happened but it is happening continously, and after around 15-20 minutes it automatically goes down,

here is the screenshot of the error

when I restart mattermost service, it gets fixed for some time

Expected behavior

it should works fine without getting stopped

Observed behavior

service stops after sometime, it stops working

here is the error
[centos@ip-172-31-34-175 ~]$ sudo systemctl status -l mattermost.service ● mattermost.service - Mattermost Loaded: loaded (/etc/systemd/system/mattermost.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2018-01-10 10:34:52 UTC; 8min ago Process: 13956 ExecStart=/opt/mattermost/bin/platform (code=exited, status=2) Main PID: 13956 (code=exited, status=2)

Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: /var/lib/jenkins/jobs/msr/jobs/d/jobs/team-release/workspace/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:729 +0x2fe
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).Execute(0x1879600, 0xc420000180, 0xf48d2f)
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: /var/lib/jenkins/jobs/msr/jobs/d/jobs/team-release/workspace/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:688 +0x2b
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: main.main()
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: /var/lib/jenkins/jobs/msr/jobs/d/jobs/team-release/workspace/src/github.com/mattermost/mattermost-server/cmd/platform/mattermost.go:32 +0x2d
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: goroutine 8 [syscall, 90692 minutes]:
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal platform[13956]: os/signal.signal_recv(0x706930)
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal systemd[1]: mattermost.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal systemd[1]: Unit mattermost.service entered failed state.
Jan 10 10:34:52 ip-172-31-34-175.us-east-2.compute.internal systemd[1]: mattermost.service failed.

#2

Hi @pankaj,

Thanks for your feedback,

We suggest upgrading to the latest version of Mattermost to see if the issue still reproduces for you.

You could also try checking your configuration according to this documentation and this doc may be helpful as well.


#3

Hi @lindy65,
Thanks for giving your time on this.
as you suggested me, I have upgraded my MM, its been 2 days and I am not seeing this issue anymore, I will surely report this issue if it arises again.
Thanks for the help.


#4

@pankaj,

Great news :slight_smile: Please do let us know if you see the issue again.