Question

rocketchat does not work after reboot?

Posted February 23, 2021 865 views
NginxApacheDigitalOcean Droplets

I have just install a rocketchat app form marketplace on digitalocean. After reboot the droplet I get this site cant be reached error.

I check the service;

service rocketchat status
● rocketchat.service - The Rocket.Chat server
Loaded: loaded (/lib/systemd/system/rocketchat.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-02-23 00:13:26 UTC; 3min 21s ago
Main PID: 1362 (node)
Tasks: 10 (limit: 1151)
CGroup: /system.slice/rocketchat.service
└─1362 /usr/bin/node /opt/Rocket.Chat/main.js

And also it says degraded ??;

rocketchat-ubuntu-s-1vcpu-1gb-sfo3-01
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Tue 2021-02-23 00:07:36 UTC; 17min ago
CGroup: /
├─user.slice
│ └─user-0.slice
│ ├─session-1.scope
│ │ ├─1117 sshd: root@pts/0
│ │ ├─1249 -bash
│ │ ├─2409 systemctl status
│ │ └─2410 systemctl status
│ └─user@0.service
│ └─init.scope
│ ├─1127 /lib/systemd/systemd –user
│ └─1128 (sd-pam)
├─init.scope
│ └─1 /sbin/init
└─system.slice
├─systemd-networkd.service
│ └─676 /lib/systemd/systemd-networkd
├─systemd-udevd.service
│ └─759 /lib/systemd/systemd-udevd
├─cron.service
│ └─861 /usr/sbin/cron -f
├─system-serial\x2dgetty.slice
│ └─serial-getty@ttyS0.service
│ └─877 /sbin/agetty -o -p – \u –keep-baud 115200,38400,9600 ttyS0 vt220
├─nginx.service
│ ├─1627 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
│ └─1630 nginx: worker process
├─polkit.service
│ └─875 /usr/lib/policykit-1/polkitd –no-debug
├─networkd-dispatcher.service
│ └─859 /usr/bin/python3 /usr/bin/networkd-dispatcher –run-startup-triggers
├─accounts-daemon.service
│ └─841 /usr/lib/accountsservice/accounts-daemon
├─systemd-journald.service

Any idea would be appreciated, thanks..

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers

Hi @mehmetaliozer,

Have you tried restarting rocketchat? With the following command:

service rocketchat restart

If it fails again, I’ll recommend checking out the Logs of RocketChat. It should provide the exact error behind the degraded state.

Regards,
KFSys

Hello, @mehmetaliozer

Can you confirm if node is listening on port 3000? I’ve just spun up a droplet using the marketplace app and even after a reboot everything is working fine.

You can check if node is listening on the port using the netstat command:

  • netstat -plunta | grep 3000

The output must be:

netstat -plunta | grep 3000
tcp        0      0 0.0.0.0:3000            0.0.0.0:*               LISTEN      1043/node
tcp        0      0 :3000    :62373     ESTABLISHED 1043/node
tcp        0      0 :3000    :62370     ESTABLISHED 1043/node
tcp        0      0 :3000    :62372     ESTABLISHED 1043/node
tcp        0      0 :3000    :62376     ESTABLISHED 1043/node
tcp        0      0 :3000    :62375     ESTABLISHED 1043/node
tcp        0      0 :3000    :62371     ESTABLISHED 1043/node
tcp        0    128 :3000    :62374     ESTABLISHED 1043/node

Also, have you made any custom changes after the initial droplet deployment? I’ve completed the installation and then rebooted the droplet again and still, everything is working as expected.

Regards,
Alex