Mattermost, Inc.

MM randomly restart

Summary

My MM instance have some troubles last week.
At debug log I found information, that MM server restarts, but there is no command for restart

Logs

{“level”:“debug”,“ts”:1534321143.0788054,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1534321143.259252,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/channels/members/me/view”}
{“level”:“debug”,“ts”:1534321143.5753138,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1534321144.0559208,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1534321144.4222775,“caller”:“wsapi/websocket_handler.go:26”,“msg”:“websocket: user_typing”}
{“level”:“debug”,“ts”:1534321144.8254626,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1534321146.1583776,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“debug”,“ts”:1534321146.8181524,“caller”:“web/handlers.go:50”,“msg”:“POST - /api/v4/users/status/ids”}
{“level”:“info”,“ts”:1534321149.2448986,“caller”:“jobs/schedulers.go:126”,“msg”:“Stopping schedulers.”}
{“level”:“debug”,“ts”:1534321149.2449918,“caller”:“jobs/schedulers.go:85”,“msg”:“Schedulers received stop signal.”}
{“level”:“info”,“ts”:1534321149.2450175,“caller”:“jobs/schedulers.go:69”,“msg”:“Schedulers stopped.”}
{“level”:“debug”,“ts”:1534321149.2450523,“caller”:“jobs/jobs_watcher.go:63”,“msg”:“Watcher Stopping”}
{“level”:“debug”,“ts”:1534321149.245076,“caller”:“jobs/jobs_watcher.go:54”,“msg”:“Watcher: Received stop signal”}
{“level”:“debug”,“ts”:1534321149.2451417,“caller”:“jobs/jobs_watcher.go:47”,“msg”:“Watcher Finished”}
{“level”:“debug”,“ts”:1534321149.2451632,“caller”:“migrations/worker.go:64”,“msg”:“Worker stopping”,“worker”:“Migrations”}
{“level”:“debug”,“ts”:1534321149.245186,“caller”:“migrations/worker.go:54”,“msg”:“Worker received stop signal”,“worker”:“Migrations”}
{“level”:“debug”,“ts”:1534321149.245208,“caller”:“migrations/worker.go:47”,“msg”:“Worker finished”,“worker”:“Migrations”}
{“level”:“info”,“ts”:1534321149.2452328,“caller”:“jobs/workers.go:170”,“msg”:“Stopped workers”}
{“level”:“info”,“ts”:1534321149.245263,“caller”:“app/app.go:257”,“msg”:“Stopping Server…”}
{“level”:“info”,“ts”:1534321149.24538,“caller”:“app/web_hub.go:120”,“msg”:“stopping websocket hub connections”}

Hi @alexmorbo, thank you for reaching out!

  1. What Mattermost server version are you using?
  2. What OS and version are you using?
  3. Do you any automation setup such as puppet or chef? Maybe a cron job is shutting down Mattermost?

Hi @amy.blais

  1. Last one 5.1.0
  2. Ubuntu 16.04.4 LTS
  3. no automation

I checked crontab from root and mattermost user, everything clear

@alexmorbo Thank you, I’ll ask our devs about this now.

Hi @alexmorbo,

Feedback from one of our community members!

Are you using the systemd services files from the docs? If yes, you should check your database server’s logs as well (the Mattermost service and the database service defined there depend on each other - e.g. if one restarts so does the other).

Also, did you do any updates to Mattermost recently? If not, then something else may have changed. E.g. there was a postgresql security update in the last 2-20 days.

Hi @amy.blais
I check my mysql server logs.
There is no restarts at 15 days

Hi @alexmorbo,

Is there a reason you decided to post that part of your log? If not, can you help post a log containing all messages between two forced restarts?