I was able to restore the 100% compliance test results after clearing one of the pubsub tables in PostgreSQL. However, this morning, I discovered that while my mobile and desktop clients appeared to be working perfectly the hosted web clients were having problems establishing OMEMO with my other clients. At least, this time I knew that it had something to do with pubsub databases. There's a few tables and I had only cleared one of them to pass the compliance test, but I guess there might have still been some entries in the other tables that were now missing associations causing more failures. I tried just clearing the pubsub related tables through phppgadmin, but it didn't seem to fix things. So, I decided to drop the pubsub tables completely and reload the database schema by importing the /opt/ejabberd-20.07/lib/ejabberd-20.07/priv/sql/pg.sql back into the database. Luckily, doing so will not overwrite any existing tables, but it did rebuild the missing pubsub tables. Anyway, that appears to have fixed that problem.

I was able to restore the 100% compliance test results after clearing one of the pubsub tables in PostgreSQL. However, this morning, I discovered that while my mobile and desktop clients appeared to be working perfectly the hosted web clients were having problems establishing OMEMO with my other clients. At least, this time I knew that it had something to do with pubsub databases. There's a few tables and I had only cleared one of them to pass the compliance test, but I guess there might have still been some entries in the other tables that were now missing associations causing more failures. I tried just clearing the pubsub related tables through phppgadmin, but it didn't seem to fix things. So, I decided to drop the pubsub tables completely and reload the database schema by importing the /opt/ejabberd-20.07/lib/ejabberd-20.07/priv/sql/pg.sql back into the database. Luckily, doing so will not overwrite any existing tables, but it did rebuild the missing pubsub tables. Anyway, that appears to have fixed that problem.

I was able to restore the 100% compliance test results after clearing one of the pubsub tables in PostgreSQL. However, this morning, I discovered that while my mobile and desktop clients appeared to be working perfectly the hosted web clients were having problems establishing OMEMO with my other clients. At least, this time I knew that it had something to do with pubsub databases. There's a few tables and I had only cleared one of them to pass the compliance test, but I guess there might have still been some entries in the other tables that were now missing associations causing more failures. I tried just clearing the pubsub related tables through phppgadmin, but it didn't seem to fix things. So, I decided to drop the pubsub tables completely and reload the database schema by importing the /opt/ejabberd-20.07/lib/ejabberd-20.07/priv/sql/pg.sql back into the database. Luckily, doing so will not overwrite any existing tables, but it did rebuild the missing pubsub tables. Anyway, that appears to have fixed that problem.

I migrated from Mnesia to PostgreSQL recently and while it appeared that the migration was successful (user accounts were preserved, etc.) the server was failing the OMEMO test on compliance.conversations.im. After speaking with Conversations and ejabberd support MUC, I was led to discovering the ejabberd server was reporting errors with the pubsub index. Unfortunately, I had to empty the pubsub tables to get things working again. That also means that any pubsub related entries (especially in Movim communities on this server) have been delete. I am hoping that there will not be any further errors related to the database migration.

I migrated from Mnesia to PostgreSQL recently and while it appeared that the migration was successful (user accounts were preserved, etc.) the server was failing the OMEMO test on compliance.conversations.im. After speaking with Conversations and ejabberd support MUC, I was led to discovering the ejabberd server was reporting errors with the pubsub index. Unfortunately, I had to empty the pubsub tables to get things working again. That also means that any pubsub related entries (especially in Movim communities on this server) have been delete. I am hoping that there will not be any further errors related to the database migration.

I migrated from Mnesia to PostgreSQL recently and while it appeared that the migration was successful (user accounts were preserved, etc.) the server was failing the OMEMO test on compliance.conversations.im. After speaking with Conversations and ejabberd support MUC, I was led to discovering the ejabberd server was reporting errors with the pubsub index. Unfortunately, I had to empty the pubsub tables to get things working again. That also means that any pubsub related entries (especially in Movim communities on this server) have been delete. I am hoping that there will not be any further errors related to the database migration.