Thanks. That didn't work.

DrSpud — Thu, 20 Jul 2017 14:03:27 +0000

Thanks. That didn't work. Still getting the same error. So I tried a few things:

- Downgraded from erlang 19.3 to 19.2 and rebuilt the ejabberd software. No difference
- Looked very carefully at what was installed and discovered a number of supporting modules installed along with ejabberd in /usr/local/lib/. rm -rf the various directories in that tree.
- Downgraded to 17.04 by building and installing against erlang 19.2

Voila, it works.

I suspect that there was an intermixing of erlang-compiled modules, and ejabberd was getting confused by this. Another thing I had noticed as well is there were version-specific ejabberd-17.xx directories alongside an ejabberd directory. I'm wondering if the ejabberd application may have picked up mismatched versions of ejabberd support libs/binaries and that's what created the problem in the first place? In any case, back in business with the original database.

In short, I think it's best to remove any and all support binaries installed by ejabberd before upgrading as a precaution.

Between 17.06 and 17.07 there

zinid — Thu, 20 Jul 2017 06:59:14 +0000

Between 17.06 and 17.07 there is a single patch of a single file changing a single line. So this is not version upgrade related.
I see you have problem initializing cache table, try to disable cache globally: set use_cache: false. Does it work?

ejabberd - Comments for "Ejabberd upgrade to 17.07 caused failure"

Thanks. That didn't work.

Between 17.06 and 17.07 there