1/30/2024 0 Comments Ejabberd mnesia tablesside effect, when joining cluster with big mnesia database, -no-timeout parameter must be passed to ejabberdctl call. When upgrading from previous versions, please notice: there is a suggested change in all SQL databases schemas, another suggested change specific for MySQL, an API change in srgcreate, and major changes in ejabberdctl help. Ive tried it again, and the mnesia table clustering works correctly. I obviously know what the 'username' field is (and I think I can guess what the 'iterationcount' would be), but I want to make sure I get the others in the right order. This new ejabberd 21.07 release includes many improvements and bugfixes in more than 130 commits. | created_at | timestamp | NO | | CURRENT_TIMESTAMP | | export2odbc server outputdir: Export Mnesia tables on server to files in outputdir. | iterationcount | int(11) | NO | | 0 | | Connect to remotely run ejabberd server at node ejabberdotherhost. | username | varchar(191) | NO | PRI | NULL | | | Field | Type | Null | Key | Default | Extra | To be able to correctly import these entries into the MySQL DB I need to figure out which field corresponds to which in the MySQL 'users' table: +-+-+-+-+-+-+ I succeeded in dumping the 'passwd' table and it is filled with entries like this one: Since my users' passwords are still stored in the Mnesia-database, I need to import them into the (new) MySQL DB on the new server. I would like to avoid using Mnesia as authentication DB from then on. I installed a shiny new server (including MySQL) and am planning to migrate to it ASAP. I have an (old) ejabberd instance that still uses 'internal' as authentication method.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |