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
Hi,
please set the log level to debug (5) as described at
https://docs.ejabberd.im/admin/guide/troubleshooting/#log-files
and try again. It is very unusual that you seem not to get any error
messages.
Also check out error.log and crash.log.
Do you do any kind of firewalling on the system in
I am not using AppArmor, but I reconfirmed that by no results being found
from "dmesg | grep -i apparmor".
I killed all the epmd processes (there were two) and as far as I know
ejabberd is my only erlang process. Restarting after killing the epmd
processes results in two new epmd processes,
Hi,
since the security patch in Erlang should not have any impact for
ejabberd and because I don't have this problem on my Stretch ejabberd
servers I doubt it is a generic issue and thus I will lower the severity.
Please make sure that epmd and all other erlang processes are stopped
before
Package: ejabberd
Version: 16.09-4
Severity: grave
Justification: renders package unusable
Just updated my system to the latest security updates for erlang packages,
and after doing so, ejabberd refuses to start. Continually gives a
"timeout" from systemd:
Dec 14 02:02:53 myhost systemd[1]:
5 matches
Mail list logo
