Martin Filip
07-02-2008, 11:54 PM
Hi jadmins,
I've just upgraded my jabberd server to latest 2.2.0. Everything works
cool but one thing is concerning me.
My s2s is generating huge amounts of log messages about non-existant
jabber realms on remote servers.
For example - a friend of mine had his jabber server on domain
jabber.example.net. For some reason he had renamed his realm to just
example.net. On my server many people has still contacts pointing to the
old jids like example (AT) jabber (DOT) example.net instead of example (AT) example (DOT) net.
The problem is huge amount of connection tries which s2s generates and
with this comes a huge amount of events logged.
a little piece of my s2s.log:
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] outgoing
connection for 'jabber.example.net'
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] sending
dialback auth request for route 'smoula.net/jabber.example.net'
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] error:
Stream error (<stream:error xmlns:stream='http://etherx.jabber.org
/streams'><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>)
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] disconnect,
packets: 2
What I mean by huge amount - this all happens with total disrespect to
router/retry settings in s2s config and it is able to generate about 5
these tries per second. So really huge amount of text and bulk traffic.
Anyone experiencing behaviour like this?
Thank you for your replies.
--
Martin Filip <nexus (AT) smoula (DOT) net>
_______________________________________________
JAdmin mailing list
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=19
Info: http://mail.jabber.org/mailman/listinfo/jadmin
Unsubscribe: JAdmin-unsubscribe (AT) jabber (DOT) org
_______________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEABECAAYFAkhr+JkACgkQzvp9bBLJ9XPMdwCfWtbFqFrCul Tm2EB855PVqNVx
J0AAnRHovt4NFlqA8vTtLdQ3KNH14v69
=8tdm
-----END PGP SIGNATURE-----
I've just upgraded my jabberd server to latest 2.2.0. Everything works
cool but one thing is concerning me.
My s2s is generating huge amounts of log messages about non-existant
jabber realms on remote servers.
For example - a friend of mine had his jabber server on domain
jabber.example.net. For some reason he had renamed his realm to just
example.net. On my server many people has still contacts pointing to the
old jids like example (AT) jabber (DOT) example.net instead of example (AT) example (DOT) net.
The problem is huge amount of connection tries which s2s generates and
with this comes a huge amount of events logged.
a little piece of my s2s.log:
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] outgoing
connection for 'jabber.example.net'
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] sending
dialback auth request for route 'smoula.net/jabber.example.net'
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] error:
Stream error (<stream:error xmlns:stream='http://etherx.jabber.org
/streams'><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error>)
Wed Jul 2 23:28:00 2008 [notice] [18] [X.X.X.X, port=5269] disconnect,
packets: 2
What I mean by huge amount - this all happens with total disrespect to
router/retry settings in s2s config and it is able to generate about 5
these tries per second. So really huge amount of text and bulk traffic.
Anyone experiencing behaviour like this?
Thank you for your replies.
--
Martin Filip <nexus (AT) smoula (DOT) net>
_______________________________________________
JAdmin mailing list
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=19
Info: http://mail.jabber.org/mailman/listinfo/jadmin
Unsubscribe: JAdmin-unsubscribe (AT) jabber (DOT) org
_______________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEABECAAYFAkhr+JkACgkQzvp9bBLJ9XPMdwCfWtbFqFrCul Tm2EB855PVqNVx
J0AAnRHovt4NFlqA8vTtLdQ3KNH14v69
=8tdm
-----END PGP SIGNATURE-----