MOD_MAM (Message Archive Management) doesnt work correctly

Debian 8 x64, Ejabberd 15.07, MySQL 5.6.25-3. Clean install.
Mysql base structure imported from this file:
https://github.com/processone/ejabberd/blob/master/sql/mysql.sql
with mysql -D ejabberd -h localhost -p -u ejabberd < ./mysql.sql (no errors appears).

# cat /opt/ejabberd-15.07/conf/ejabberd.yml
...
auth_method: internal
...
odbc_type: mysql
odbc_server: "localhost"
odbc_port: 3306
odbc_database: "ejabberd"
odbc_username: "ejabberd"
odbc_password: "PASSWORD"
...
mod_mam:
    default: always
    db_type: odbc
...

Clients:
- Alice
Gajim 0.16.3 on Debian 8 x64
Conversations 1.5.2 on Android 4.1.2
- Bob
Gajim 0.16.3 on Debian 8 x64

Messages correctly writes in database in archive table (I can see them through phpmyadmin, for example). No new errors in /opt/ejabberd-15.07/logs/error.log appears.
But clients (Gajim and Conversations) dont receive messages from database. Tried to clean all Gajim profile folders and create new profile - same result.
Same result if I choose to store messages in mnesia database.
Mod_mam_mnesia from contrib works, but I'd like to use official module.

What should I do to fix it? Where can be the problem?

We have fixed a few bugs in

We have fixed a few bugs in master already. If you have the option, you could try the development version or try with the upcoming ejabberd 15.09 when released.

Syndicate content