I upgraded ejabberd from 1.1.4 to 2.0.4. I have installed mod_statsdx from svn-872.
Now, this error shows up in the ejabberd log.
=ERROR REPORT==== 2009-05-07 08:28:02 === E(<0.2340.0>:mod_statsdx:255) : get_statistic error for N: 'ejabberd@server.mydomain.edu', A: [{recv, presence, out, 60000}, "courses.my.domain.edu"] {badarg,[{ets,update_counter, ['mod_statsdx_courses.my.domain.edu', {recv,"courses.my.domain.edu",presence,out}, {2,1,0,0}]}, {mod_statsdx,get_stat,2}, {mod_statsdx,get_statistic,2}, {mod_stats2file,fwttl,4}, {mod_stats2file,write_stats,5}, {lists,foreach,2}, {mod_stats2file,write_statsfiles,5}, {mod_stats2file,loop,5}]}
Try mod_stasdx/branches/ejabberd-2.0.x
I upgraded ejabberd from 1.1.4 to 2.0.4. I have installed mod_statsdx from svn-872.
Now, this error shows up in the ejabberd log.
You have ejabberd 2.0.4. You didn't specify, but it seems you are using mod_statsdx from mod_statsdx/trunk.
Can you try using instead from mod_stasdx/branches/ejabberd-2.0.x ? Check ejabberd.log and sasl.log when you start the server and when a client connects.
If that doesn't help, please comment here exactly what options did you add to ejabberd.cfg, and what are the first error messages that you see in ejabberd.log or sasl.log
Same error with mod_stasdx/branches/ejabberd-2.0.x
Thanks badlop. I wasn't using mod_stasdx/branches/ejabberd-2.0.x. I recompiled from that directory. Same errors show up in the logs.
First error:
Not sure if this is related, but these errors show up when I compile mod_statsdx
From ejabberd.cfg:
Fixed in SVN. Update and try.
Not sure if this is related, but these errors show up when I compile mod_statsdx
Not related. I also see them; don't worry about them at all. And those are warning messages, not error messages.
I wasn't using mod_stasdx/branches/ejabberd-2.0.x. I recompiled from that directory. Same errors show up in the logs.
I tried with your configuration, and I found the problem in the code. Update mod_statsdx from svn, and now it should work.
Mostly fixed
Great! Updating to r962 mostly fixed it.
Still seeing the error for 'totalmucrooms'.
Do you have mod_muc disabled?
I get that error message if I delete a Mnesia table. In your case, maybe you have mod_muc disabled in ejabberd.cfg?
If that's your case, you have three solutions:
My test:
Re: Do you have mod_muc disabled?
Ah, I still have mod_muc enabled on only 1 or the 2 nodes (the 1.1.4 way). I see now that the errors only show up on the node that doesn't have mod_muc enabled.
Now that ejabberd 2.x supports mod_muc clustering, I will figure out how to configure it on both nodes.
Thanks again for your help and your patience, badlop.