Listing empty rooms >99

Hey,

I'm currently migrating from Openfire,
I wrote up a script to migrate MUC room data from openfire into ejabberd,
it currently writes to the 'muc_room' table in the appropriate format, this works well,
I'm able to import the rooms along with thier topic and moderator/password details.

Although, once the total number of rooms goes abovel 99 added, room discovery returns "Empty Rooms",
and I see the pasted errors in the logs, I'm not sure why its trying to connect to conference.localhost,
the muc is configured as conference.foo.com and is setup with the required SRV records.

Note: this issue only shows up when the number of rooms are greater than 99
I tried disabling s2s, by commenting out ejabberd_s2s_in but that didn't help,
I get the same messages in the log,

I came across,
http://stackoverflow.com/questions/32988750/ejabberd-s2s-out-remote-serv...

I also note the answer here, although I'm sure what he means there,
http://stackoverflow.com/questions/36619043/cannot-list-muc-rooms-from-e...

016-06-02 08:57:10.286 [debug] <0.663.0>@ejabberd_s2s:do_route:293 s2s manager
2016-06-02 08:57:10.286 [debug] <0.663.0>@ejabberd_s2s:find_connection:334 Finding connection for {<<"foo.com">>,<<"conference.localhost">>}
2016-06-02 08:57:10.286 [debug] <0.666.0>@ejabberd_s2s_out:init:139 started: {<<"foo.com">>,<<"conference.localhost">>,new}
2016-06-02 08:57:10.287 [info] <0.663.0>@ejabberd_s2s:new_connection:408 New s2s connection started <0.666.0>
2016-06-02 08:57:10.288 [debug] <0.663.0>@ejabberd_s2s:choose_pid:382 Using ejabberd_s2s_out <0.666.0>
2016-06-02 08:57:10.288 [debug] <0.663.0>@ejabberd_s2s:do_route:298 sending to process <0.666.0>
2016-06-02 08:57:10.288 [info] <0.666.0>@ejabberd_s2s_out:log_s2s_out:1253 Trying to open s2s connection: foo.com -> conference.localhost with TLS=false
2016-06-02 08:57:10.288 [debug] <0.666.0>@ejabberd_s2s_out:open_socket:214 open_socket: {<<"foo.com">>,<<"conference.localhost">>,true,false}
2016-06-02 08:57:10.317 [debug] <0.666.0>@ejabberd_s2s_out:get_addr_port:1095 srv lookup of 'conference.localhost' failed: nxdomain
2016-06-02 08:57:10.325 [debug] <0.666.0>@ejabberd_s2s_out:get_addrs:1188 inet lookup of 'conference.localhost' failed: nxdomain
2016-06-02 08:57:10.327 [debug] <0.666.0>@ejabberd_s2s_out:get_addrs:1188 inet6 lookup of 'conference.localhost' failed: nxdomain
2016-06-02 08:57:10.327 [info] <0.666.0>@ejabberd_s2s_out:open_socket:246 s2s connection: foo.com -> conference.localhost (remote server not found)

Thanks for any help,
Joel

https://support.process-one.n

https://support.process-one.net/browse/EJAB-343

Last comment in there seems to mention a change that could have caused this ?

Is there any way I could turn off non-listing of empty rooms ?

Right, when 100 or more rooms

Right, when 100 or more rooms exist, Service Discovery shows the empty ones in a node called "Empty Rooms".

I see some Jabber clients are not able to display correctly items in nodes; in Tkabber it works correctly; in Psi the node is shown with wrong name, in Gajim the Service Disco is not flexible, and doesn't allow to join empty rooms...

Regarding those debug log lines about conference.localhost, I don't know.

BTW, an alternative to manual editting the database, you can enable mod_muc_admin and call ejabberdctl commands.

Syndicate content