ejabberd - Comments for "Server drops random messages from muc with error 503."

I am also getting this 503

Nikhil — Wed, 18 Nov 2015 08:58:50 +0000

I am also getting this 503 service unavailable response sometime while sending messages to chat room ,all these messages are dropped by the time .
Currently i am using ejabberd 15.09 , Asmack library as my android client and Xmpp Framework as ios client .

below is the config i am having currently:

Virtual host : ejabberd.xyz.com
Muc service host : conference.ejabberd.xyz.com

mod_muc config is:
[{db_type, odbc}, {access, muc},
{access_create, muc_create},
{access_persistent, muc_create},
{access_admin, muc_admin},
{max_users, 300},
{max_users_admin_threshold, 10},
{max_user_conferences, 20},
{history_size, 1000},
{default_room_options,
[{persistent, true}, {mam, true}]}]

Error log:

2015-11-07 18:06:27.070 [debug] <0.4634.4>@ejabberd_c2s:send_text:1901 Send XML on stream = <<"2">>

packet {xmlel,<<"message">>,[{<<"type">>,<<"error">>},{<<"from">>,<<"testmuc@conference.xyz.com">>},{<<"id">>,<<"1af4f538-e6b9-42cc-bdea-0e7eba558461-4C1">>},{<<"xml:lang">>,<<"en">>}],[{xmlel,<<"body">>,[],[{xmlcdata,<<"6">>}]},{xmlel,<<"error">>,[{<<"code">>,<<"503">>},{<<"type">>,<<"cancel">>}],[{xmlel,<<"service-unavailable">>,[{<<"xmlns">>,<<"urn:ietf:params:xml:ns:xmpp-stanzas">>}],[]}]}]}
2015-11-07 18:06:28.410 [debug] <0.4634.4>@ejabberd_c2s:send_text:1901 Send XML on stream = <<"6">>

is it necessary to change muc service host and muc service host should be different from virtual host ?

I was also getting the 503

diane — Fri, 24 Jul 2009 06:17:09 +0000

I was also getting the 503 message dropping when I was trying ejabberd 2.0.3 (from ubuntu).

I'd also set up my ejabberd.cfg file to specify my host and a sub-domain conference.host in the hosts list, e.g. {hosts, ["host", "conference.host"]}.

The 503's went away when I removed the conference.host from the list of virtual hosts, and just left the servers main hostname. e.g. {hosts, ["host"]}. Additional the conference rooms started showing up in the service discovery browser.

503 means

mfoss — Tue, 01 Jul 2008 17:13:42 +0000

503 means 'service-unavailable'... strange.

You can try increasing the limits imposed by those options in the C2S listener: {shaper, c2s_shaper}, {max_stanza_size, 65536},

There are another limits configurable in mod_muc, described in the ejabberd Guide. But since you don't have those options defined, the mod_muc limits are not applied.

I joined a 'test' room in your MUC with two of my accounts (from jabber.org). Both participants could send messages. I tried sending many messages fast, and also with big messages. No error reported, and all messages where shown to both room participants.