Niamh Having no further information, it looks to me that you might have a too old version of gsasl... checking for gsasl_check_version in -lgsasl... yes This line says it can find gsasl and its library. checking for GnuSASL version= 0.2.27... no This line says it fails the version check.
Tomasz and others, I'm using jabberd2 v2.2.17. For a while now I have experienced strange values in the status database table for some users, including myself. The most obvious problem is that the status field can show online even if the user is offline and last-login and last-logout are both
Christof, I had the same problem, luckily I ran on a test server. I could not even login with my client. There has been a change in sx/ssl.c line 899. The line now reads ctx = SSL_CTX_new(TLSv1_2_method()); This means that it will support TLS v1.2 only. Connections using SSLv3 or TLS v1.1
Hello, A typical XMPP server will open only one port, port 5222. All clients will connect to that port so in theory an almost unlimited number of connections are possible to that server. This is not particular to XMPP but is a basic TCP/IP client/server feature, exactly the same goes for
Guido, This looks like a problem with your system, not your jabber setup. What happens is simple, udns is trying to resolve the hostnames but this takes too long. From the jabberd2 source code I can see that the timeout is set to 5 seconds. The fact you didnt see it with jabberd 1.4 is most
+0100, Eric Koldeweij pisze: My suspicion is that there is a problem with a name server you are using. if you look at the file /etc/resolv.conf you will see one or more lines saying nameserver ip_addr. The resolver will ask each name server in turn to resolve the host name for it, I second
Guido, I forgot one thing: For the IPv6 thing you should also edit s2s.xml and comment out the line resolve-ipv6/ if it isn't commented out already. Sorry. Regards, Eric. On 28-Dec-13 15:59, Eric Koldeweij wrote: Guido, Does your server have IPv6 connectivity? If not try to edit
Tomasz (and maybe others), After an upgrade today from 2.2.17 to 2.3.2 a small number of users are unable to connect. The strange thing is that they seem to be thrown out AFTER they have authenticated correctly and the session has started. I have looked but I cannot see why it suddenly should