MongoDB Not stable - MongoNetworkError - Snap version 4.8.3 - ubuntu 20.04

Description

Can someone provide a little insight on this issue I’m struggling with since, well, very very long time now … Pleease

Since I moved to version 4.8.3 on 4.x/stable - I’m getting these strange mongodb error
It seems the system is suffering from intermittent disconnections on 127.0.0.1:27017

Below the Log from Rocketchat :

I20221107-14:46:01.092(1) Exception in setInterval callback: Error: connect ECONNREFUSED 127.0.0.1:27017     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)     at TCPConnectWrap.callbackTrampoline (internal/async_hooks.js:130:17) {   name: 'MongoNetworkError' } 
I20221107-14:47:04.088(1) Exception while invoking method 'UserPresence:away' MongoNetworkError: connection 28 to 127.0.0.1:27017 closed     at Connection.handleIssue (/snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connection.js:129:15)     at Socket.<anonymous> (/snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/cmap/connection.js:62:35)     at Socket.emit (events.js:400:28)     at Socket.emit (domain.js:475:12)     at TCP.<anonymous> (net.js:686:12)     at TCP.callbackTrampoline (internal/async_hooks.js:130:17)
I20221107-15:07:21.129(1) Exception in setInterval callback: Error: connect ECONNREFUSED 127.0.0.1:27017     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)     at TCPConnectWrap.callbackTrampoline (internal/async_hooks.js:130:17) {   name: 'MongoNetworkError' } 
I20221107-14:56:43.789(1) Exception from sub stream-notify-room id ug8APxAqXSGBge24Q Error: connect ECONNREFUSED 127.0.0.1:27017     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)     at TCPConnectWrap.callbackTrampoline (internal/async_hooks.js:130:17)  => awaited here:     at Function.Promise.await (/snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)     at server/modules/notifications/notifications.module.ts:187:19     at /snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40  => awaited here:     at Function.Promise.await (/snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)     at server/modules/streamer/streamer.module.ts:181:7     at /snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40  => awaited here:     at Function.Promise.await (/snap/rocketchat-server/1523/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)     at Subscription.<anonymous> (app/notifications/server/lib/Notifications.ts:18:19)     at packages/matb33:collection-hooks/server.js:33:71     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1257:12)     at Subscription._handler (packages/matb33:collection-hooks/server.js:33:26)     at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1885:12)     at packages/ddp-server/livedata_server.js:1107:9     at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1257:12)     at Subscription._runHandler (packages/ddp-server/livedata_server.js:1106:60)     at Session._startSubscription (packages/ddp-server/livedata_server.js:917:9)     at Session.sub (packages/ddp-server/livedata_server.js:673:12)     at packages/ddp-server/livedata_server.js:603:43 

So far everything is fine on the version 4.8.3
but when I move to 5.x the system become instable and the main issue is that after a short time the message are greyed out on the Chat interface and you have to constantly refresh the Server to Get everything updated …

Server Setup Information

  • Version of Rocket.Chat Server: 4.8.3

  • Operating System: Ubuntu 20.04 LTS

  • Deployment Method: snap

  • Number of Running Instances: 1

  • DB Replicaset Oplog: Enabled

  • NodeJS Version: 14.18.3 - x64

  • MongoDB Version: 4.2.17

  • Proxy: nginx

  • Firewalls involved: no

  • active users < 100

Any additional Information

I tried almost everything …
from Timeout on mongodb (Env Variables … ) to rlimits to iptables and firewall
Binding Options in Mongodb Config file
I also tried resetting network and changing network adapter

Current VM Spec :
Vmware 6.7 vm
16 vcpu
16 gb ram
network adapter : e1000e (also tried vmxnet3)