RocketChat / RocketChat/Rocket.Chat

Failed to start Service for snap application rocketchat-server.rocketchat-server

Open
#14,582 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Service for snap application rocketchat-server does not auto start anymore.

Steps to reproduce:
  1. Turn on server.
Expected behavior:

Rocketchat must be actively running after turning on the server.

Actual behavior:

Rocketchat service status failure after turning on the server.

Server Setup Information:
  • Version of Rocket.Chat Server: 1.0.3
  • Operating System: Ubuntu 18.04.2 LTS
  • Deployment Method: Snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v8.11.3
  • MongoDB Version: 3.4.20
Additional context
Relevant logs:
 snap.rocketchat-server.rocketchat-server.service - Service for snap applicatio
   Loaded: loaded (/etc/systemd/system/snap.rocketchat-server.rocketchat-server.
   Active: failed (Result: exit-code) since Wed 2019-05-22 00:01:09 UTC; 10min a
  Process: 2138 ExecStart=/usr/bin/snap run rocketchat-server (code=exited, stat
 Main PID: 2138 (code=exited, status=1/FAILURE)

May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-se
May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-se
May 22 00:01:09 smctchat_server systemd[1]: Stopped Service for snap application
May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-se
May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-se
May 22 00:01:09 smctchat_server systemd[1]: Failed to start Service for snap app
lines 1-12/12 (END)...skipping...
● snap.rocketchat-server.rocketchat-server.service - Service for snap application rocketchat-server.rocketchat-server
   Loaded: loaded (/etc/systemd/system/snap.rocketchat-server.rocketchat-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-05-22 00:01:09 UTC; 10min ago
  Process: 2138 ExecStart=/usr/bin/snap run rocketchat-server (code=exited, status=1/FAILURE)
 Main PID: 2138 (code=exited, status=1/FAILURE)

May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-server.service: Service hold-off time over, scheduling restart.
May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-server.service: Scheduled restart job, restart counter is at 6.
May 22 00:01:09 smctchat_server systemd[1]: Stopped Service for snap application rocketchat-server.rocketchat-server.
May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-server.service: Start request repeated too quickly.
May 22 00:01:09 smctchat_server systemd[1]: snap.rocketchat-server.rocketchat-server.service: Failed with result 'exit-code'.
May 22 00:01:09 smctchat_server systemd[1]: Failed to start Service for snap application rocketchat-server.rocketchat-server.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the boot failure on Ubuntu 18.04.2 LTS with the Rocket.Chat snap, then inspect the reported systemd service status and failure logs. Compare the behavior with the listed NodeJS and MongoDB versions; done means the service starts successfully after a server reboot.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb, node.js, ubuntu
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.