Maybe there are other modules enabled in your server that also create : We noticed that with creation of room, the memory kept on increasing (even though the rooms were completely empty). Regarding the clients connections, a just registered account with no roster is around 16kB from what I saw. Maybe the number of room occupants? subscribers? their activity? It could be checked what factors in a room usage increase that memory consumption. That's an almost empty, just created room. All the actual online room information is kept in the state of the corresponding erlang process.Īnd how much memory does it require each muc room erlang process? I did a quick test with Erlang 24.3, ejabberd 22.05, amd64, and an almost empty, just created room process is 5 kB. None: admin normal: all s2s_shaper: fast modules: Max_user_sessions: 10 max_user_offline_messages: ejabberd_ctl who: all what: '* ' ' admin access ': Port: 1883 ip: ':: ' module: mod_mqtt backlog: 1000 s2s_use_starttls: optional acl: Port: 3478 transport: udp module: ejabberd_stun use_turn: true # The server's public IPv4 address: # turn_ip: 203.0.113.3 bosh: mod_bosh /websockets: ejabberd_http_ws /admin: ejabberd_web_admin # /.well-known/acme-challenge: ejabberd_acme Port: 5280 ip: ':: ' module: ejabberd_http request_handlers: Port: 5281 ip: ':: ' module: ejabberd_http request_handlers: websockets: ejabberd_http_ws /bosh: mod_bosh /admin: ejabberd_web_admin Port: 8443 ip: ':: ' module: ejabberd_http tls: true request_handlers: Port: 5222 ip: ':: ' module: ejabberd_c2s max_stanza_size: 262144 shaper: c2s_shaper access: c2s starttls_required: true etc/ssl/ejabberd/some_company.pem #certfiles: # - /etc/ssl/ejabberd/some_company.pem # - /etc/letsencrypt/live/domain.tld/privkey.pem oom_watermark: 50 listen: dev-pigeon.some_ loglevel: debug # If you already have certificates, list them here certfiles: # trameters used in this configuration file are explained at # The configuration file is written in YAML.

Ejabberd web admin default password