On a brand new installation, none of the outgoing s2s functions seem to work due to DNS resolution errors, tested with several different XMPP servers. Here's a gist of some of the errors:
debug Sending DNS query to 8.8.8.8
warn DNS socket for 8.8.8.8 disconnected: connection timeout
error Exhausted all 1 configured DNS servers, next lookup will try 8.8.8.8 again
debug DNS lookup failed to get a response for jabber.example.com
The server is running a plain vanilla 0.9.8 installation on Arch. The server has IPv4/IPv6 running dual stack, but AFAICT issue 352 is irrelevant in this case since I'm not running an IPv6-only setup. In any case I tried the 127.0.0.1 dnsmasq workaround but didn't help.
Also this doesn't seem to be a duplicate of issue 487, but I'll be happy to know if this is the case and when I can expect a release to test.
Zash
on
What version of LuaSocket are you using?
Are you using luaevent?
Awesome! I've put a warning in the Arch wiki referencing thi sbug, and looking forward to 0.10 being released.
Thanks for the great work on prosody and the quick respones :)
On a brand new installation, none of the outgoing s2s functions seem to work due to DNS resolution errors, tested with several different XMPP servers. Here's a gist of some of the errors: debug Sending DNS query to 8.8.8.8 warn DNS socket for 8.8.8.8 disconnected: connection timeout error Exhausted all 1 configured DNS servers, next lookup will try 8.8.8.8 again debug DNS lookup failed to get a response for jabber.example.com The server is running a plain vanilla 0.9.8 installation on Arch. The server has IPv4/IPv6 running dual stack, but AFAICT issue 352 is irrelevant in this case since I'm not running an IPv6-only setup. In any case I tried the 127.0.0.1 dnsmasq workaround but didn't help. Also this doesn't seem to be a duplicate of issue 487, but I'll be happy to know if this is the case and when I can expect a release to test.
What version of LuaSocket are you using? Are you using luaevent?
Arch uses LuaSocket from git commit https://github.com/diegonehab/luasocket/commit/4110e4125dace9df3a744067066e5dee62670561 Yes, I have luaevent enabled, version 0.4.3 installed
I see where you're going with this. When disabling luaevent, everything works great.
I noticed this earlier, https://github.com/diegonehab/luasocket/issues/147#issuecomment-137494758 A fix is in the 0.10 branch: https://hg.prosody.im/0.10/rev/86fcc3fa1a97 It might work with that applied, but beware breaking changes in git versions of both LuaSocket and LuaSec.
Awesome! I've put a warning in the Arch wiki referencing thi sbug, and looking forward to 0.10 being released. Thanks for the great work on prosody and the quick respones :)
Will reopen if we decide to backport to 0.9
ChangesLooks like Debian backported this patch: https://bugs.debian.org/863475