--- Comment #9 from Carl-Johan Schenström <cjs(a)bluebox.pp.se> ---
I just upgraded from FC20 (ejabberd-2.1.13-7.fc20.x86_64) to FC22
(ejabberd-14.07-6.fc22.x86_64), which broke ejabberd in the following ways:
1. The configuration file wasn't converted, only saved as
/etc/ejabberd/ejabberd.cfg.rpmsave. Possibly connected to #2, since
"ejabberdctl convert_to_yaml" is used for converting.
2. .erlang.cookie mismatch. Solved this one by copying
/var/lib/ejabberd/.erlang.cookie to my home directory. Converted configuration
file as in #1.
3. All users gone. Copied /var/lib/ejabberd/spool to the same directory on
another FC20 host, mucked about with hostnames, dumped the data with
"ejabberdctl dump", copied it back to the FC22 host, loaded it with
"ejabberdctl load" and restarted the service. Using "ejabberdctl
"ejabberdctl restore" didn't work, since the database schema is different.
You are receiving this mail because:
You are on the CC list for the bug.