Ejabberd 25.10 fails to read database entries for muc_online_rooms - 25.08 works fine

[sunbladehub]

Environment

• ejabberd version: 25.10
• Erlang version:
• OS: Linux (Debian)
• Installed from: Docker

Errors from error.log/crash.log

No errors

Bug description

The list of existing MUCs can normally be obtained in the CLI via ejabberdctl muc_online_rooms group.server.com. On 25.10 the list returned is empty despite entries existing in the muc_room table of the MariaDB database. If Ejabberd is downgraded to 25.08, muc_online_rooms returns the correct non-empty list of entries from the database.

[badlop]

Quite strange. Looking at the source code changes in files src/mod_muc*.erl in the range 25.08..25.10 doesn't show any change that should affect this.

Using the 25.10 ejabberd container image, default ejabberd configuration and default room configuration, the API muc_online_rooms works correctly.

What changes have you applied compared to the default configuration? MariaDB instead of Mnesia, anything else in mod_muc configuration? And in room configuration?

[sunbladehub]

The mod_muc config has a few differences relative to the example config:

• Defined host
• Removed access_admin
• Added some default_room_options but those shouldn't be relevant

As a test I reverted back to the example mod_muc config. Same result.

I eventually discovered the problem is actually greater than I originally thought. I tried to test things out by creating and destroying MUCs via ejabberdctl. This always fails on 25.10 with the error {error,"Database error"}. If I downgrade to 25.08, I can create and destroy MUCs without error and list the existing MUCs.

[prefiks]

I think this is dup of 4492

[sunbladehub]

I confirmed the image linked in 4492 by @badlop fixes the issue. Thanks.