Container Crashing Randomly after 7.13.5 upgrade

[LeeThompson]

Description:

Since upgrading the container from 7.11.2 to 7.13.5, the container has suddenly exited (crashed) three times within a 72 hour period.

There are only 2 regular users and it's mainly used for two people to communicate, it's secondary use is notifications from various applications such as Home Assistant.

NOTE: Some information isn't complete, I'm still going through logs. Issue will be updated.

Steps to reproduce:

(Still trying to figure this part out.)

Expected behavior:

This is the most unstable RocketChat we've run.

Actual behavior:

Not applicable.

Server Setup Information:

• Version of Rocket.Chat Server: 7.13.5
• License Type: Starter
• Number of Users: 2
• Operating System: Debian (Synology)
• Deployment Method: docker
• Number of Running Instances: 1
• DB Replicaset Oplog: Yes
• NodeJS Version: (whatever the image ships with)
• MongoDB Version: 7.0.18

Client Setup Information

• Desktop App or Browser Version: Firefox 149.0
• Operating System: Windows 10 Enterprise

Additional context

Relevant logs:

(Gathering this, will update)

[Rohit544]

hello I want to contribute this issue could you please assign it to me ?

[LeeThompson]

Still going through logs, the most recent crash, however, was a JAVA heap out of memory so I've edited the container with a higher RAM limit (was 1024MB, now 1536MB) and I haven't had another crash, yet. It's still early though. Oddly, general memory use is still around the 400-600MB mark so might be a sign of memory usage spikes.

[reetp]

Check the resource requirements.

Docs say 4Gb+ (for Rocket/Mongo/et al) so you are way off and likely to hit issues. I'd use that as your baseline.

Seen far too many users over the years struggling on underpowered, under resourced VPS/VM.

https://docs.rocket.chat/v1/docs/system-requirements

Sounds like this can be closed.

[LeeThompson]

1536MB seems to be sufficient for the RocketChat container for my use case so just gone up a little. (Mongo is in it's own container)
I'm going to close this as it seems to be the cause in all of the container exits and it's been running fine since the tweak.