I'd like to completely remove the chat module from my Carbonio installation. Nobody is using it, it is disabled for all my users, and yet it causes the most trouble, often requiring manual intervention after updates.
Just now I found again that mongooseim is puking into the logs every 15s:
May 01 09:02:48 <my hostname> mongooseimctl[4510]: =ERROR REPORT==== 1-May-2026::09:02:48.750635 ===
May 01 09:02:48 <my hostname> mongooseimctl[4510]: reason: function_clause
May 01 09:02:48 <my hostname> mongooseimctl[4510]: stacktrace: <<"wpool_pool:g/2:334 mongoose_wpool_rdbms:get_rdbms_data_stats/2:64 safely:apply_and_log/4:58 mongoose_instrument_probe:call/3:20">>
May 01 09:02:48 <my hostname> mongooseimctl[4510]: class: error
May 01 09:02:48 <my hostname> mongooseimctl[4510]: what: probe_failed
May 01 09:02:48 <my hostname> mongooseimctl[4510]: event_name: wpool_global_rdbms_stats
May 01 09:02:48 <my hostname> mongooseimctl[4510]: labels: #{pool_tag => default}
May 01 09:02:48 <my hostname> mongooseimctl[4510]: probe_mod: mongoose_wpool_rdbms
May 01 09:02:48 <my hostname> mongooseimctl[4510]: stacktrace_args: <<"[size,undefined]">>
If possible, I would like to either remove all packages related to chat or at least make sure that anything that is only required for chat will never be started on boot.
Is that possible in a way that will survive updates?
Thanks, Christian
@zottel
The solution you are thinking of is yet to be defined officially. Therefore, I would request you to approach with caution.
The mongooseimctl[PID] lines come from carbonio-message-dispatcher.service. As you could see in the official docs, carbonio-message-dispatcher-ce package is responsible for the Chats module. So stopping and masking the service (carbonio-message-dispatcher.service) should stop the mongooseimctl log entries.
systemctl stop carbonio-message-dispatcher
systemctl mask carbonio-message-dispatcher
Try them and share your findings with us.
Also, don't remove any packages in a rush. That could break the infrastructure.