uI was already running loglevel 4, and changing it to 5 gave no additional
info. There was nothing in the error.log or crash.log either, in fact those
files hadn't even been opened, as the timestamps were still of times
pre-upgrade.
However, your hint to look for firewall issues was a good one.
Looks like this was a problem with ejabberdctl using ipv6 by default. We
don't use ipv6 here, so had no rules loaded for ipv6, and the default
iptables policy was set to drop. Since Debian configures ipv6 addresses
automatically I guess it was trying to use ipv6 anyway and never fell
back to using ipv4.
Apologies for the error. But this failure mode should probably give
something more useful that just a timeout with no useful messages. Perhaps
it should emit a message to say that ejabberdctl couldn't contact the
daemon?
Thanks.
