ejabberd - Comments for "troubles with mod_mam on 15.06 "

Each message has two parties,

mremond — Wed, 08 Jul 2015 07:49:53 +0000

Each message has two parties, so yes, seems normal.

With default: always, all

badlop — Tue, 07 Jul 2015 16:10:14 +0000

With default: always, all messages sent and received are stored automatically. I don't configure anything else in my client or in ejabberd.

When user1 sends a message to user2, then two entries are stored in the archive_msg table.

Please, say, is it normal,

Deniska — Tue, 07 Jul 2015 11:48:42 +0000

Please, say, is it normal, that i have two records in archieve table for every message with this module?

It looks like we had an issue

mprokop — Mon, 06 Jul 2015 17:36:40 +0000

It looks like we had an issue with our updates rolling out with our in house server. After a manual reinstall the errors have seem to vanished. I have it configured on my machine, will messages automatically start appearing in the archive table? Or will I have to configure on a per user basis?

With those options, and MySQL

badlop — Thu, 02 Jul 2015 16:49:14 +0000

With those options, and MySQL storage, my messages are stored in the "archive" table. Such errors don't appear.

In fact, looking at the source code of ejabberd and cache_tab, I don't understand how that error appears: timestamp() is not called anywhere I can see.

How did you install ejabberd 15.06? Binary installer... which one? Or source code, how did you get erlang?