#1103879 ejabberd cluster node does not start after upgrade (bookworm -> trixie)

Package:
ejabberd
Source:
ejabberd
Description:
extensible realtime platform (XMPP server + MQTT broker + SIP service)
Submitter:
Date:
2025-04-23 22:03:01 UTC
Severity:
normal
#1103879#5
Date:
2025-04-22 11:37:53 UTC
From:
To:
On upgrading an ejabberd cluster node from bookworm to trixie a problem
with mam tables arises.

* ejabberd version: 24.12-3
  (Debian trixie, upgraded from bookworm 23.01-1 with apt dist-upgrade)
* Erlang version: Erlang 15.2.6

Error from the log [2]

I did report this upstream [0] and they have provided a fix [1] very
quickly. Now I'm not sure how I can test this fix as long as it's not
in the debian repo.



[0] upstream report: https://github.com/processone/ejabberd/issues/4374

[1] fix:
https://github.com/processone/ejabberd/commit/67cc0c528667a5bcdeab0cf63cf8aa0d42c6f0c7

[2]
2025-04-21 10:52:06.402141+02:00 [error]
<0.188.0>@ejabberd_mnesia:mnesia_op/2:431
 Failure on mnesia transform_table [archive_msg,
                                   #Fun<ejabberd_mnesia.8.102878464>,

[us,id,timestamp,peer,bare_peer,packet,
                                    nick,type,origin_id]]: {aborted,
                                                            {"Bad
transform function",

archive_msg,

#Fun<ejabberd_mnesia.8.102878464>,

'ejabberd@example.org',
                                                             {badfun,

#Fun<ejabberd_mnesia.8.102878464>}}}
2025-04-21 10:52:06.402902+02:00 [critical]
<0.1109.0>@gen_mod:start_module/4:186
 Failed to start module mod_mam: {error,db_failure}
2025-04-21 10:52:06.403065+02:00 [critical]
<0.1109.0>@gen_mod:maybe_halt_ejabberd/0:285
 ejabberd initialization was aborted because a module start failed.
#1103879#10
Date:
2025-04-23 14:44:07 UTC
From:
To:
Hi,

for what architecture do you need the supposedly fixed ejabberd
package?

Regards
#1103879#15
Date:
2025-04-23 17:52:52 UTC
From:
To:
Thx for the rocket-fast response :)

amd64

Markus
#1103879#20
Date:
2025-04-23 21:20:28 UTC
From:
To:
Hi,
you can now grab an ejabberd package with the proposed fix for
testing/unstable from this location:
https://apt.debalance.de/pool/main/e/ejabberd/ejabberd_24.12-4_amd64.deb


Please let me know if that solves your problem.

Best wishes
#1103879#25
Date:
2025-04-23 22:01:35 UTC
From:
To:
Thx! But I get the same error during sync of the mam tables.
'ejabberd@node1.example.com' in the log message below is the first node
in the cluster which is still on bookworm. I'm testing the upgrade on
node2.


2025-04-23 23:55:38.923094+02:00 [error] Failure on mnesia
transform_table [archive_msg,
                                   #Fun<ejabberd_mnesia.8.102878464>,

[us,id,timestamp,peer,bare_peer,packet,
                                    nick,type,origin_id]]: {aborted,
                                                            {"Bad
transform function",

archive_msg,

#Fun<ejabberd_mnesia.8.102878464>,

'ejabberd@node1.example.com',
                                                             {badfun,

#Fun<ejabberd_mnesia.8.102878464>}}}