Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1260796

Bug#1085140: converting from mnesia to sqlite

From Johannes Schauer Marin Rodrigues <josch@debian.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#1085140: converting from mnesia to sqlite
Date 2025-09-10 08:30 +0200
Message-ID <Ltmv7-edyF-21@gated-at.bofh.it> (permalink)
References <Ltmls-edve-7@gated-at.bofh.it> <JxNrs-1M70-11@gated-at.bofh.it> <Ltmls-edve-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Quoting Johannes Schauer Marin Rodrigues (2025-09-10 08:10:16)
> As advised, I removed (backed up) /var/lib/ejabberd/archive_msg* and
> /var/lib/ejabberd/pubsub* but ejabberd still fails to start within 5 minutes
> (the default timeout) with the journalctl log from above.
> 
> I don't mind loosing a bit more data (only the user database is really
> important I think) and am looking for advice on how to get this service to
> start after my upgrade to Trixie. If this is a different bug (I'm filing it
> here because my archive_msg.DAT was large) then I'll open another issue. But at
> this point I would appreciate more advice from you.
> 
> I now manually increased the timeout for ejabberd to start from 5 minutes to 2
> hours and maybe this will fix itself, given a few more CPU cycles to spare?

Ah, it is the same issue. Though in my case, removing archive_msg.DAT was not
enough. Running "du -s /var/lib/ejabberd/* | sort -n" revealed that I had this:

1300288	/var/lib/ejabberd/upload

And it seems that the uploaded files are also part of the database?

Anyways, moving these out of the way now gives me a running server:

https://compliance.conversations.im/server/mister-muffin.de/

> > 2) Convert to SQL before upgrading (strongly recommended).
> >
> > I could help with either (e.g., in the ejabberd support channel), but 
> > maybe that's out of scope here?
> 
> Once everything runs I'd greatly appreciate advice on how to convert my
> installation to sqlite. I have a very small instance with only a handful of
> users and thus thought that using mnesia would be fine. Looking at the database
> sizes, maybe not the case. If you could point me to the guide on how to do the
> conversion, I'd greatly appreciate it. I was not successful finding such
> instruction in the web (with google and bing/duckduckgo).

I'd still appreciate some pointers for this so that I do not run into the same
issue the next time I upgrade.

Thank you so much for maintaining ejabberd in Debian! I have been using (and
upgrading) it for nearly a decade by now. :)

Thanks!

cheers, josch

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Bug#1085140: converting from mnesia to sqlite Johannes Schauer Marin Rodrigues <josch@debian.org> - 2025-09-10 08:20 +0200
  Bug#1085140: converting from mnesia to sqlite Johannes Schauer Marin Rodrigues <josch@debian.org> - 2025-09-10 08:30 +0200

csiph-web