Automatic snap package update leads to unreachable instance

[scoopex]

Description:

Trigger a update of the snap package.

It seems that nodejs server runs in a timeout because the mongodb server is not not seems to be ready fast enough. The rocketchat server does probably not wait long enough to be connected to mongodb. Probably there is a trivial fix in just increasing connection pool timeout values or re-trying forever to get a mongodb connection.

Steps to reproduce:

1. Stop rocketchat nodejs server and mongodb server
2. Start rocketchat nodejs server
3. Wait 10 minutes
4. Start Mongodb server
5. Nodejs does not automatically connect to mongodb after mongodb is available

Expected behavior:

Rocketchat should retry forever (ideally with a exponential backoff, limited by 5 minute cycles) to get a mongodb connection.

Server Setup Information:

• Version of Rocket.Chat Server: 2.1.1
• Operating System: Ubuntu 18.04
• Deployment Method: snap
• Number of Running Instances: 1

[scoopex]

Happens again this night after update to 2.3.1.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[scoopex]

Probably still broken. I stopped using rocketchat.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.