Package: ejabberd Followup-For: Bug #931211 Hi,
while taking a look at this I run into an interesting discussion here: https://github.com/processone/ejabberd/issues/528 The scenario is different but the log message matches the one in this report. In that case the problem seemed to be related to name resolution in erlang, and not strictly an ejabberd issue. The fact that the issue here started with a buster upgrade might be due to a change in behavior in erlang internals, which might have broken ejabberd assumptions is some corner case. The log message posted by Marco points out to this line in erlang: https://sources.debian.org/src/erlang/1:21.2.6+dfsg-1/lib/kernel/src/inet_dns.erl/#L694 And the "empty" label mentioned in the comment could be the last entry in the log message: ... [<<"_xmpps-server">>,<<"_tcp">>,<<"jabber">>,<<"seeweb">>,<<"it">>,<<>>] ^^^^ In the discussion above, one possible cause is said to be extra trailing dots in FQDNs. Is it possible that the issue Marco is experiencing is caused by something like that? I didn't notice anything strange in posted config, but what about DNS records or entries in /etc/hosts? Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
