ejabberd - Comments for "mnesia backup failed"

Difficult to know: many changes between 1.1.4 and 2.0.5

mfoss — Sun, 19 Apr 2009 18:02:54 +0000

virt wrote:

And after upgrade don't work AgileMessenger client.

Client connected and after some seconds disconected

=INFO REPORT==== 2009-04-08 10:09:36 ===
I(<0.273.0>:ejabberd_listener:116) : (#Port<0.6732>) Accepted connection {{y,y,y,y},48672} -> {{x,x,x,x},5222}
=INFO REPORT==== 2009-04-08 10:09:40 ===
I(<0.3121.0>:ejabberd_c2s:449) : ({socket_state,gen_tcp,#Port<0.6732>,<0.3120.0>}) Accepted legacy authentication for virt@rtr.domain.ru/AgileMessenger
=INFO REPORT==== 2009-04-08 10:09:47 ===
I(<0.3121.0>:ejabberd_c2s:1306) : ({socket_state,gen_tcp,#Port<0.6732>,<0.3120.0>}) Close session for virt@rtr.domain.ru/AgileMessenger

Another client are working ok.

I try connect with AgileMessenger to public ejabberd server (jabber.ru version 2.1.0-alpha) and all ok.
But with my ejabberd server version 2.05 this client is not work.
Only with this client, another (miranda, tkabber, Im+, IChabber) worked fine.

You say it worked with 1.1.4, but doesn't work with 2.0.5. There are may changes in ejabberd between 1.1.4 and 2.0.5, so it's difficult to get an idea of what could be the problem.

You could experiment with intermediate ejabberd versions (1.1.4, 2.0.0, 2.0.1...). Maybe you can find what exact ejabberd version starts to not work with AgileMess. Your first experiment should be with ejabberd 1.1.4, to ensure this version works correctly. You can install those ejabberds in another machine, because it is only for testing Agile client.

What about this question? And

virt — Fri, 17 Apr 2009 10:09:53 +0000

What about this question?

And after upgrade don't work AgileMessenger client.

Client connected and after some seconds disconected

=INFO REPORT==== 2009-04-08 10:09:36 ===
I(<0.273.0>:ejabberd_listener:116) : (#Port<0.6732>) Accepted connection {{y,y,y,y},48672} -> {{x,x,x,x},5222}
=INFO REPORT==== 2009-04-08 10:09:40 ===
I(<0.3121.0>:ejabberd_c2s:449) : ({socket_state,gen_tcp,#Port<0.6732>,<0.3120.0>}) Accepted legacy authentication for virt@rtr.domain.ru/AgileMessenger
=INFO REPORT==== 2009-04-08 10:09:47 ===
I(<0.3121.0>:ejabberd_c2s:1306) : ({socket_state,gen_tcp,#Port<0.6732>,<0.3120.0>}) Close session for virt@rtr.domain.ru/AgileMessenger

Another client are working ok.

Set no admins

mfoss — Mon, 13 Apr 2009 11:37:47 +0000

virt wrote:

In config file I uncomment string
{watchdog_admins, ["virt@rtr.company.ru"]}.

But then I comment out this line again the debug messages continue to received
How I can off watchdog_admins ?

Put this:

{watchdog_admins, []}.

Thank you. Full path

virt — Mon, 13 Apr 2009 10:41:50 +0000

Thank you.
Full path /tmp/ejabberd.back is works.

And another question.
In config file I uncomment string
{watchdog_admins, ["virt@rtr.company.ru"]}.

I began to receive reports like this

rtr.company, 10.04.2009 15:43:41:
(ejabberd@rtr) The process <0.2757.0> is consuming too much memory: [{old_heap_block_size,832040},{heap_block_size,196418},{mbuf_size,0},{stack_size,17886},{old_heap_size,609055},{heap_size,56886}].
Process type: c2s
Command to kill this process: kill ejabberd@rtr <0.2757.0>

But then I comment out this line again the debug messages continue to received
How I can off watchdog_admins ?

Put full path where ejabberd can write, like /tmp/ejabberd.back

mfoss — Fri, 10 Apr 2009 21:46:35 +0000

That error message is probably caused because ejabberd can't create the file (it doesn't have write permissions). In the Web Admin, instead of storing to 1.backup or ejabberd.backup, put a full path, like: /home/virt/ejabberd.backup, or /tmp/ejabberd.backup or something like that.