ejabberd - Comments for "shared roster error? {badmatch, {error,"

More news: I probably found

mfoss — Sat, 14 May 2011 07:51:36 +0000

More news: I probably found the problem, being an incorrect configuration, check: http://www.ejabberd.im/node/4674#comment-57328

Re:

mfoss — Thu, 12 May 2011 19:24:34 +0000

habicious wrote:

I looked in the sql database in all of the tables starting with 'pubsub', they are all empty.

What exactly is stored in pubsub?

Some clients use Pubsub to store some information. If your users didn't complain about Pubsub not working, then you can disable mod_pubsub in ejabberd.cfg

more info regarding

habicious — Mon, 09 May 2011 14:26:14 +0000

Thank you very much for taking the time to respond to my post. I looked in the sql database in all of the tables starting with 'pubsub', they are all empty. Could this be related to the problem? Maybe information isn't being put in there correctly?

There is information in the ejabberd db under other tables such as 'rostergroups' and 'rosterusers', so I know that ejabberd is talking to the database and putting information in there. What exactly is stored in pubsub?

Thank you!

I think that error happens

mfoss — Thu, 05 May 2011 16:13:02 +0000

I think that error happens when the user disconnects from the server, and ejabberd is reading something in the pubsub tables about that user. That is unrelated to what you may configure in Shared Rosters.

If this error happens only with that jlookabaugh account, you could try to remove from the pubsub SQL tables any reference to him.

If the error happens for many different accounts, and you don't care about information that clients may have stored in pubsub, you can delete the content in all the pubsub SQL tables.

In other case, the best you can do is to wait, maybe other people can give more ideas about where the problem is.