[ejabberd] Ejabberd messages delayed delivery

Mansab Uppal mansab.uppal at gmail.com
Fri Nov 15 00:25:14 MSK 2013


Do you recognize that IP? is that a user? Also, what do you have at around
line 157 in ejabberd.cfg. The one I am sharing is the default chunk of code:

{5280, ejabberd_http, [
%%{request_handlers,                        %% [                        %%
{["pub", "archive"], mod_http_fileserver}                        %%
]},                        captcha,
http_bind,                        http_poll,
%%register,                        web_admin                       ]} ]}.


On Fri, Nov 15, 2013 at 1:47 AM, Saurabh Kumar <saurabh.catch at gmail.com>wrote:

> I have http-bind running on 8080. If  a client connects using http-bind
> then there wont be any tcp connection on port 5222. If the httpbind client
> is making new tcp connection again and again, there must be something
> wrong.
>
> what could cause such a behaviour? Additionally, client is not
> authenticating again and again. It is just the new tcp connection.
> On Nov 15, 2013 1:31 AM, "Mansab Uppal" <mansab.uppal at gmail.com> wrote:
>
>> If you see closely, every time the tcp connection is being started over a
>> different port. However, that should not cause something erroneous. Just
>> check if the same IP connection is established over port 5222 (beam), that
>> will let you know if the connection is actually being established or it is
>> just trying and getting disconnected. No active connection could lead you
>> to look further in the Ejabberd's configuration and user rosters.
>>
>> To check the connection use:
>>
>> netstat -a | grep EST | grep | beam
>>
>> And look for the IP.
>>
>>
>> On Fri, Nov 15, 2013 at 12:57 AM, Saurabh Kumar <saurabh.catch at gmail.com>wrote:
>>
>>> I don't see any warnings and errors but the log keep saying  "Accepted
>>> connection" from the same IP addresses again and again. Is this normal?
>>> Clients are probably using http-bind to connect to the Ejabberd server.
>>>
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.285.0>:ejabberd_listener:281) : (#Port<0.24365277>) Accepted
>>> connection {{180,149,52,42},55538} -> {{10,152,178,50},8080}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.31663.157>:ejabberd_http:146) : started: {gen_tcp,#Port<0.24365277>}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.285.0>:ejabberd_listener:281) : (#Port<0.24365281>) Accepted
>>> connection {{180,149,52,42},37086} -> {{10,152,178,50},8080}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.31664.157>:ejabberd_http:146) : started: {gen_tcp,#Port<0.24365281>}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.285.0>:ejabberd_listener:281) : (#Port<0.24365289>) Accepted
>>> connection {{180,149,52,42},36295} -> {{10,152,178,50},8080}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.31665.157>:ejabberd_http:146) : started: {gen_tcp,#Port<0.24365289>}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.283.0>:ejabberd_listener:281) : (#Port<0.24365292>) Accepted
>>> connection {{106,219,18,35},35319} -> {{10,152,178,50},5222}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.285.0>:ejabberd_listener:281) : (#Port<0.24365296>) Accepted
>>> connection {{180,149,52,42},35494} -> {{10,152,178,50},8080}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.31668.157>:ejabberd_http:146) : started: {gen_tcp,#Port<0.24365296>}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.283.0>:ejabberd_listener:281) : (#Port<0.24365300>) Accepted
>>> connection {{169,204,229,146},43402} -> {{10,152,178,50},5222}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.285.0>:ejabberd_listener:281) : (#Port<0.24365302>) Accepted
>>> connection {{180,149,52,42},50210} -> {{10,152,178,50},8080}
>>>
>>> =INFO REPORT==== 2013-11-14 19:23:07 ===
>>> I(<0.31671.157>:ejabberd_http:146) : started: {gen_tcp,#Port<0.24365302>}
>>>
>>>
>>>
>>> On Fri, Nov 15, 2013 at 12:35 AM, Saurabh Kumar <saurabh.catch at gmail.com
>>> > wrote:
>>>
>>>> Although 'ejabberd.cfg' file was alright,  'ejabberdctl reopen-log'
>>>> worked for me. Thanks. I will post the logs, whenever I see a glitch.
>>>>
>>>> Saurabh
>>>>
>>>>
>>>> On Fri, Nov 15, 2013 at 12:27 AM, Mansab Uppal <mansab.uppal at gmail.com>wrote:
>>>>
>>>>> Well, I am not sure about the run time logging. However, you may check
>>>>> your 'ejabberd.cfg' file and check if the loglevel is properly defined.
>>>>>
>>>>> You can also try to reopen the log files after they were renamed by
>>>>> using 'ejabberdctl reopen-log'.
>>>>>
>>>>> Hope that helps.
>>>>>
>>>>>
>>>>> On Fri, Nov 15, 2013 at 12:05 AM, Saurabh Kumar <
>>>>> saurabh.catch at gmail.com> wrote:
>>>>>
>>>>>> Is there a way to switching ON the logs runtime (without restart)?
>>>>>> Logs were ON but somehow the logs file got deleted and the server has
>>>>>> stopped logging now.
>>>>>>
>>>>>> I tried this but does not seem to work.
>>>>>>
>>>>>>  % erl -sname node1 -remsh ejabberd at localhost
>>>>>>   Erlang (BEAM) emulator version 5.6.5 [source] [smp:2] [async-threads:0] [hipe] [kernel-poll:false]
>>>>>>
>>>>>>   Eshell V5.6.4  (abort with ^G)
>>>>>>   (ejabberd at localhost)1> ejabberd_loglevel:set(3).
>>>>>>   {module,ejabberd_logger}
>>>>>>   (ejabberd at localhost)2>
>>>>>>   BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
>>>>>>          (v)ersion (k)ill (D)b-tables (d)istribution
>>>>>>   %
>>>>>>
>>>>>> (hitting ^c^c to end the session)
>>>>>>
>>>>>>
>>>>>> On Thu, Nov 14, 2013 at 11:54 PM, Saurabh Kumar <
>>>>>> saurabh.catch at gmail.com> wrote:
>>>>>>
>>>>>>> Thanks for the reply. Will share shortly.
>>>>>>>
>>>>>>> Saurabh
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Nov 14, 2013 at 11:46 PM, Mansab Uppal <
>>>>>>> mansab.uppal at gmail.com> wrote:
>>>>>>>
>>>>>>>> You might need to check the 'ejabberd.logs' for the specific jabber
>>>>>>>> IDs and around with which you face the delay.
>>>>>>>>
>>>>>>>> P.S If possible share the logs here.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Nov 14, 2013 at 8:36 PM, Saurabh Kumar <
>>>>>>>> saurabh.catch at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I am using Ejabberd 2.1.13 with around 500 concurrent connections.
>>>>>>>>> Sometimes, chat messages start delivering late (~30s delay)  suddenly and
>>>>>>>>> this gets fixed on its own. Any clue on what could cause this? During the
>>>>>>>>> faulty behaviour, CPU and Memory consumption stays normal.
>>>>>>>>>
>>>>>>>>> Saurabh
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> ejabberd mailing list
>>>>>>>>> ejabberd at jabber.ru
>>>>>>>>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>> Mansab Uppal - mansab.upp.al
>>>>>>>> Director, GetTechGo - gettechgo.com <http://www.gettechgo.com/>
>>>>>>>> Manager, TeamJabber - teamjabber.com <http://www.teamjabber.com>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> ejabberd mailing list
>>>>>>>> ejabberd at jabber.ru
>>>>>>>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> ejabberd mailing list
>>>>>> ejabberd at jabber.ru
>>>>>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Mansab Uppal - mansab.upp.al
>>>>> Director, GetTechGo - gettechgo.com <http://www.gettechgo.com/>
>>>>> Manager, TeamJabber - teamjabber.com <http://www.teamjabber.com>
>>>>>
>>>>> _______________________________________________
>>>>> ejabberd mailing list
>>>>> ejabberd at jabber.ru
>>>>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> ejabberd mailing list
>>> ejabberd at jabber.ru
>>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>>
>>>
>>
>>
>> --
>> Regards,
>> Mansab Uppal - mansab.upp.al
>> Director, GetTechGo - gettechgo.com <http://www.gettechgo.com/>
>> Manager, TeamJabber - teamjabber.com <http://www.teamjabber.com>
>>
>> _______________________________________________
>> ejabberd mailing list
>> ejabberd at jabber.ru
>> http://lists.jabber.ru/mailman/listinfo/ejabberd
>>
>>
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd
>
>


-- 
Regards,
Mansab Uppal - mansab.upp.al
Director, GetTechGo - gettechgo.com <http://www.gettechgo.com/>
Manager, TeamJabber - teamjabber.com <http://www.teamjabber.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jabber.ru/pipermail/ejabberd/attachments/20131115/eb3624ab/attachment.html>


More information about the ejabberd mailing list