Bug#931211: s2s connections are broken after upgrading to buster

2020-01-04 Thread Antonio Ospite
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

Bug#931211: s2s connections are broken after upgrading to buster

2019-07-02 Thread Marco d'Itri
On Jul 02, Philipp Huebner wrote: > Can you verify that _srv-Lookups work on your server? > E.g. "dig -t srv _xmpp-server._tcp.debalance.de" Names resolution works fine. > And make sure that if your DNS responds with records you are able > to connect to IPv6 hosts. This too. > Also check

Bug#931211: s2s connections are broken after upgrading to buster

2019-07-01 Thread Philipp Huebner
I just upgraded my own ejabberd server from Stretch to Buster and everything's fine. I'll put your config on my test machine and see if it causes any problems there, in the meantime you could provide the crash.log from your server. Best wishes -- .''`. Philipp Huebner : :' : pgp fp: 6719

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-29 Thread Marco d'Itri
On Jun 29, Philipp Huebner wrote: > Could you try my no-change rebuild of ejabberd under buster? > https://apt.debalance.de/pool/main/e/ejabberd/ejabberd_18.12.1-2.1_i386.deb Thank you, still broken. -- ciao, Marco signature.asc Description: PGP signature

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-29 Thread Philipp Huebner
Other than your user block being indented one more space than necessary I don't see anything wrong. Am 29.06.19 um 18:59 schrieb Marco d'Itri: > acl: > admin: > user: >- "xxx": "jabber.linux.it" >- "xxx": "jabber.linux.it" Could you try my no-change rebuild of ejabberd

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-29 Thread Marco d'Itri
On Jun 29, Philipp Huebner wrote: > If you're willing to share your ejabberd configuration files I am happy > to take a look, otherwise I don't know how to help you. Thank you, I surely may have got something wrong in the conversion: --- loglevel: 4 log_rotate_count: 0 log_rotate_date: ""

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-29 Thread Philipp Huebner
Hi again, I tried to reproduce your problem by setting up two fresh Debian Buster installations, one i386 one amd64. s2s between them works like a charm, and the list of installed packages is identical to yours. For that reason I assume your problem is either in your ejabberd configuration or

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-28 Thread Marco d'Itri
On Jun 28, Philipp Huebner wrote: > I just noticed that after my latest ejabberd upload there have been > several updates of Erlang for buster, maybe we need binNMUs for ejabberd > and erlang-p1-*. Maybe a missing dependency? root@sarek:~# dpkg -l | egrep 'erlang|ejabberd' ii ejabberd

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-28 Thread Philipp Huebner
Hi, this is rather strange, could you please let me know what erlang packages and versions you have installed? Looks like there is a mismatch somewhere. I just noticed that after my latest ejabberd upload there have been several updates of Erlang for buster, maybe we need binNMUs for ejabberd

Bug#931211: s2s connections are broken after upgrading to buster

2019-06-28 Thread Marco d'Itri
Package: ejabberd Version: 18.12.1-2 Severity: important After upgrading to buster apparently all s2s connections are broken. I have no idea of what is wrong here. error.log: 2019-06-28 12:17:17.896 [error] <0.1995.0>@inet_dns:encode_labels:694 gen_server <0.1995.0> terminated with reason: no