You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our staging server (13 users, ~2 active) crashed for no apparent reason shortly after a user sync script ran (the script runs every 5 minutes, ran fine before and after manual restart of RC, and changed/POSTed nothing in this run.) After manual restart it works fine.
(Crash behaviour is similar to #22062, also reported by myself, but the error message is different.)
Steps to reproduce:
(Unclear)
Server dies with the log entries posted below
We had to manually restart RC.
Expected behavior:
Run, RC, keep on running! 😇 (Or at least attempt to restart, which could be achieved by systemd's Restart option. Since the systemd unit is created by rocketchatctl, I guess I'll file an issue there, too.)
Actual behavior:
systemd service exited, see logs below.
Server Setup Information:
Version of Rocket.Chat Server: 3.17.0 (Commit Hash: d4ce52e, Commit Branch: HEAD)
Operating System: Debian GNU/Linux 9.13 (stretch)
Deployment Method: rocketchatctl
Number of Running Instances: 2 (one on this staging VM, one on a separate production VM)
DB Replicaset Oplog: the startup log says "Enabled"
NodeJS Version: v12.18.4 - x64
MongoDB Version: 4.0.19 (mmapv1)
Client Setup Information
Desktop App or Browser Version: n/a (no GUI client involved)
Operating System: n/a
Additional context
What's (maybe) special about our setup is that:
it's behind a corporate proxy (or more precisely, two different proxies, for HTTP and HTTPS) and not reachable from the outside world, which caused and causes a couple of problems (f.e. traefik can't request a LetsEncrypt certificate and creates an invalid "[0-9a-f.].traefik.default" cert)
Description:
Our staging server (13 users, ~2 active) crashed for no apparent reason shortly after a user sync script ran (the script runs every 5 minutes, ran fine before and after manual restart of RC, and changed/POSTed nothing in this run.) After manual restart it works fine.
(Crash behaviour is similar to #22062, also reported by myself, but the error message is different.)
Steps to reproduce:
Expected behavior:
Run, RC, keep on running! 😇 (Or at least attempt to restart, which could be achieved by systemd's
Restart
option. Since the systemd unit is created by rocketchatctl, I guess I'll file an issue there, too.)Actual behavior:
systemd service exited, see logs below.
Server Setup Information:
Client Setup Information
Additional context
What's (maybe) special about our setup is that:
traefik
can't request a LetsEncrypt certificate and creates an invalid "[0-9a-f.].traefik.default
" cert)Relevant logs:
The text was updated successfully, but these errors were encountered: