On Saturday, April 5, 2025 1:39:44 AM Mountain Standard Time Holger Weiß wrote: > * Soren Stoutner <[email protected]> [2025-04-04 17:22]: > >Before attempting the update > >MnesiaCore.ejabberd@mail_1743_810526_689352 was 0.3 MB. After > >attempting the update, the file size had ballooned to 235 MB. > > > >However, before the update archive_msg.DAT was 285 MB, and > >ballooned to over 300 MB during the failed update. > > > >Do these file sizes seem large to you? It is perhaps a timeout > >trying to process the database because of the size? Is there some > >way to compact/purge the database? > > Ah, thanks. Yes, this clearly indicates that the Mnesia table used > for storing the server-side message archive is borked (there's a > max. size limit of 2 GiB), and it's most probably the reason > ejabberd fails to start up. > > So, for cases such as yours, I see no proper fix, and would instead > suggest one of the following two options: > > 1) Remove Mnesia's archive table (i.e., all messages stored > server-side) and maybe also the PubSub tables before upgrading. > The remaining tables will probably survive the upgrade, and fresh > archive/PubSub tables will be usable after the upgrade (until the > next breakage, at least).
I can confirm that removing the archive* and pubsub* files before upgrade allowed the upgrade to complete successfully. -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
