Ejabberd mnesia tables2/2/2024 ![]() ![]() Ok, there's a feature incompatibility: you are asking ejabberd the details about the registered accounts, but ejabberd doesn't know what accounts exist. "Access-Control-Allow-Headers": "Content-Type"Īccess_max_user_messages: max_user_offline_messagesĭb_type: sql # This is what I want to get rid of # This runs behind reverse HTTP proxy with Let's Encrypt, which is neighbour container on the same host, so this is safeĮxtauth_program: "/etc/ejabberd/auth_mysql.py" The configuration on the new machine just references the same MySQL database for mod_roster and mod_vcard. Mnesia database migration was done as follows: # on the old machineĮjabberdctl backup mnesia_change_nodename on the new machine (starting with empty database) I don't have that machine at my discretion anymore. The database was migrated from old Ejabberd of around version 2.1, that was running on Gentoo and last updated in 2015. Ejabberd 21.01-2 installed with apt from standard Debian repo. Software: Debian 11.2 LXC container running on Proxmox VE 6.4-1 host. It just exports zero content, while there is data in the database and it is fetched when I connect with e.g. Is there a way to convert their data externally and load into ejabberd? I mean, there is a ejabberdctl dump_table, but again no reverse command.Īlso, export_piefxis doesn't seem to help. After some exploration I found that only two modules have some data in the SQL database: mod_roster and mod_vcard. How can I revert that change?Ĭan export_piefxis help me somehow? What it does? Somebody in the past did that thing, exported a database into SQL (specifically, MySQL). There are around 10-15 active users and no more than 30 of total users, and the size of the export from SQL database is around 200 kB. In my case there is really no need to have an external database. Some setups may need that because Mnesia is limited to 2GiB and blah blah blah. There is pretty supported action to move from Mnesia to SQL, a special command ejabberdctl export2sql (in older versions it used to be called export2odbc).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |