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, but ejabberd still times out,
and the server doesn't answer.
The related processes that are running:
3700069 ? Ss 0:00 /bin/sh -c /usr/sbin/ejabberdctl start &&
/usr/sbin/ejabberdctl started
3700070 ? S 0:00 /bin/bash /usr/sbin/ejabberdctl start
3699902 ? Ss 0:00 /usr/bin/epmd -systemd
3700502 ? S 0:00 /usr/bin/epmd -names
Here is all that is in the ejabberd.log from a start attempt:
2017-12-14 18:03:49.040 [info] <0.31.0> Application lager started on node
ejabberd@kinison
2017-12-14 18:03:49.188 [info] <0.31.0> Application crypto started on node
ejabberd@kinison
2017-12-14 18:03:49.256 [info] <0.31.0> Application sasl started on node
ejabberd@kinison
2017-12-14 18:03:49.314 [info] <0.31.0> Application asn1 started on node
ejabberd@kinison
2017-12-14 18:03:49.315 [info] <0.31.0> Application public_key started on node
ejabberd@kinison
2017-12-14 18:03:49.357 [info] <0.31.0> Application ssl started on node
ejabberd@kinison
2017-12-14 18:03:49.436 [info] <0.31.0> Application fast_yaml started on node
ejabberd@kinison
2017-12-14 18:03:49.539 [info] <0.31.0> Application fast_tls started on node
ejabberd@kinison
2017-12-14 18:03:49.614 [info] <0.31.0> Application fast_xml started on node
ejabberd@kinison
2017-12-14 18:03:49.650 [info] <0.31.0> Application stringprep started on node
ejabberd@kinison
2017-12-14 18:03:49.669 [info] <0.31.0> Application cache_tab started on node
ejabberd@kinison
2017-12-14 18:03:50.469 [info] <0.31.0> Application mnesia started on node
ejabberd@kinison
There is nothing indicating any info about failure in the ejabberd.log.
On Thu, 14 Dec 2017, Philipp Huebner wrote:
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 trying to start ejabberd again. If necessary, kill them manually.
Please also check whether AppArmor is enabled (dmesg | grep -i
apparmor). Have you tried rebooting the server yet?
Without access to your ejabberd logs + dmesg I cannot really help you.
Regards,
--
.''`. Philipp Huebner <debala...@debian.org>
: :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F
`. `'`
`-
