I'm having troubles seting up a jabberd-2.0-0.s11 server on a CentOS 5 system. The problem seems to be in the configuration host ID. Following the instructions about using the same ID on sm.xml and c2s.xml is imposible for c2s to start and die after a router refused bind request (409) message. You can see the starting log sharing the same ID:
<id>192.168.1.1</id>: Feb 5 01:15:56 tormento jabberd/router[24474]: starting up Feb 5 01:15:56 tormento jabberd/router[24474]: process id is 24474, written to /var/lib/jabberd/pid/router.pid Feb 5 01:15:56 tormento jabberd/router[24474]: loaded user table (1 users) Feb 5 01:15:56 tormento jabberd/router[24474]: [127.0.0.1, port=5347] listening for incoming connections Feb 5 01:15:57 tormento jabberd/resolver[24498]: starting up Feb 5 01:15:57 tormento jabberd/resolver[24498]: process id is 24498, written to /var/lib/jabberd/pid/resolver.pid Feb 5 01:15:57 tormento jabberd/resolver[24498]: attempting connection to router at 127.0.0.1, port=5347 Feb 5 01:15:57 tormento jabberd/router[24474]: [127.0.0.1, port=39116] connect Feb 5 01:15:57 tormento jabberd/sm[24522]: starting up Feb 5 01:15:58 tormento jabberd/router[24474]: [127.0.0.1, port=39116] authenticated as jabberd Feb 5 01:15:58 tormento jabberd/resolver[24498]: connection to router established Feb 5 01:15:58 tormento jabberd/sm[24522]: id: 192.168.1.1 Feb 5 01:16:00 tormento jabberd/router[24474]: [resolver] online (bound to 127.0.0.1, port 39116) Feb 5 01:16:00 tormento jabberd/sm[24522]: process id is 24522, written to /var/lib/jabberd/pid/sm.pid Feb 5 01:16:00 tormento jabberd/c2s[24546]: starting up Feb 5 01:16:00 tormento jabberd/resolver[24498]: ready to resolve Feb 5 01:16:00 tormento jabberd/sm[24522]: initialised storage driver 'db' Feb 5 01:16:01 tormento jabberd/c2s[24546]: process id is 24546, written to /var/lib/jabberd/pid/c2s.pid Feb 5 01:16:01 tormento jabberd/sm[24522]: version: jabberd sm 2.0s11 Feb 5 01:16:01 tormento jabberd/c2s[24546]: initialised auth module 'db' Feb 5 01:16:02 tormento jabberd/s2s[24570]: starting up (interval=60, queue=60, keepalive=0, idle=86400) Feb 5 01:16:02 tormento jabberd/sm[24522]: attempting connection to router at 127.0.0.1, port=5347 Feb 5 01:16:02 tormento jabberd/c2s[24546]: [192.168.1.1] configured; realm=(null) Feb 5 01:16:03 tormento jabberd/s2s[24570]: process id is 24570, written to /var/lib/jabberd/pid/s2s.pid Feb 5 01:16:03 tormento jabberd/router[24474]: [127.0.0.1, port=39117] connect Feb 5 01:16:04 tormento jabberd/c2s[24546]: attempting connection to router at 127.0.0.1, port=5347 Feb 5 01:16:05 tormento jabberd/s2s[24570]: attempting connection to router at 127.0.0.1, port=5347 Feb 5 01:16:05 tormento jabberd/router[24474]: [127.0.0.1, port=39117] authenticated as jabberd Feb 5 01:16:05 tormento jabberd/sm[24522]: connection to router established Feb 5 01:16:05 tormento jabberd/router[24474]: [127.0.0.1, port=39118] connect Feb 5 01:16:06 tormento jabberd/router[24474]: [127.0.0.1, port=39119] connect Feb 5 01:16:06 tormento jabberd/router[24474]: [192.168.1.1] online (bound to 127.0.0.1, port 39117) Feb 5 01:16:06 tormento jabberd/sm[24522]: ready for sessions Feb 5 01:16:06 tormento jabberd/router[24474]: [127.0.0.1, port=39118] authenticated as jabberd Feb 5 01:16:06 tormento jabberd/c2s[24546]: connection to router established Feb 5 01:16:06 tormento jabberd/router[24474]: [127.0.0.1, port=39119] authenticated as jabberd Feb 5 01:16:06 tormento jabberd/s2s[24570]: connection to router established Feb 5 01:16:06 tormento jabberd/router[24474]: [127.0.0.1, port=39118] tried to bind '192.168.1.1', but it's already bound Feb 5 01:16:07 tormento jabberd/router[24474]: [s2s] set as default route Feb 5 01:16:07 tormento jabberd/c2s[24546]: router refused bind request (409) Feb 5 01:16:08 tormento jabberd/router[24474]: [s2s] online (bound to 127.0.0.1, port 39119) Feb 5 01:16:08 tormento jabberd/router[24474]: [127.0.0.1, port=39118] disconnect Feb 5 01:16:08 tormento jabberd/s2s[24570]: [0.0.0.0, port=5269] listening for connections Feb 5 01:16:09 tormento jabberd/s2s[24570]: ready for connections On the other and, and following other tips on the web, setting up different ID's al the system starts succesfully, but then, the server didn't answer for the desired domain. asking for server.net domain (which is set at sm.xml): [EMAIL PROTECTED] ~]$ telnet server.net 5222 Trying 192.168.1.1... Connected to server.net (192.168.1.1). Escape character is '^]'. <?xml version="1.0"?> <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client" to="server.net"> <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='server.net' id='zdsru037fijf18bs3aq8h1r04jvif0zedr58s9g7'><stream:error xmlns:stream='http://etherx.jabber.org/streams'><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>service requested for unknown domain</text></stream:error></stream:stream>Connection closed by foreign host. asking for localhost domain (which is set at c2s.xml): [EMAIL PROTECTED] ~]$ telnet server.net 5222 Trying 192.168.1.1... Connected to server.net (192.168.1.1). Escape character is '^]'. <?xml version="1.0"?> <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client" to="localhost"> <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='localhost' id='rznt8ylb9bjqdbrhvm0amzp0rv9k5pswpfpyeban'><stream:error xmlns:stream='http://etherx.jabber.org/streams'><host-gone xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>session manager for requested domain is not available</text></stream:error></stream:stream>Connection closed by foreign host. This behavior seems correct but I couldn't find any other configuration which lets the c2s subsystem to keep alive. Of course domain and nameserver configuration is correct on /etc/hosts, etc. I've investigated for many hours without success. Is it a bug? What I'm doing wrong? -- A. Ismael Olea González http://olea.org/diario/ http://aduaneros.olea.org, la ONG sin futuro. El mundo debe empezar a tener miedo a un planeta OLEA
signature.asc
Description: This is a digitally signed message part
smime.p7s
Description: S/MIME cryptographic signature
