[JDEV] Server without involving jabber.org?
Keith Barrett
kbarrett at redhat.com
Wed Jan 24 11:45:21 CST 2001
OK
Here is the most "prominate" jabber.org connection message:
20010123T23:54:53: [notice] (update.jabber.org): bouncing a packet
to jsm at update.jabber.org/1.4pre2 from brak.devel.redhat.com:
Server Connect Timeout
20010124T00:02:43: [alert] (s2s): We were told by update.jabber.org
that our sending name XXX is invalid, either we tried using that
name improperly or dns does not resolve to us
I ge this even though I have commented out the whole s2s/dialback
section, and "mod_version". It appears the s2s ran anyway.
With debugging enabled, I see even more attempts to involve
jabber.org in my private setup. Since I'm new at this, I don't
yet understand the details or the seriousness of these. Here are
examples; just scan for "jabber.org" (note: the "XXX" is just
where my host/ip address appeared, the real log does not say "XXX")
Wed Jan 24 12:30:40 2001 deliver.c:452 DELIVER 1:update.jabber.org
<presence from='XXX' to='jsm at update.jabber.org/1.4pre2'/>
Wed Jan 24 12:30:40 2001 dnsrv.c:355 dnsrv: Recv'd a lookup request:
update.jabber.org
Wed Jan 24 12:30:40 2001 dnsrv.c:385 dnsrv: Creating lookup request
queue for update.jabber.org
Wed Jan 24 12:30:40 2001 dnsrv.c:395 dnsrv: Transmitting lookup request
for update.jabber.org to coprocess
Wed Jan 24 12:30:40 2001 dnsrv.c:154 DNSRV CHILD: eating read buffer
Wed Jan 24 12:30:40 2001 dnsrv.c:106 dnsrv: Recv'd lookup request for
update.jabber.org
Wed Jan 24 12:30:40 2001 srv_resolv.c:101 srv: SRV resolution of
_jabber._tcp.update.jabber.org
Wed Jan 24 12:30:40 2001 srv_resolv.c:88 srv: Standard resolution
of update.jabber.org
Wed Jan 24 12:30:40 2001 dnsrv.c:117 Resolved update.jabber.org((null)):
208.245.212.100 resend to:s2s
Wed Jan 24 12:30:40 2001 dnsrv.c:150 DNSRV CHILD: Reading from buffer
Wed Jan 24 12:30:40 2001 deliver.c:452 DELIVER 4:s2s <route to='s2s'
ip='208.245.212.100'><presence from='XXX'
to='jsm at update.jabber.org/1.4pre2'/></route>
Wed Jan 24 12:30:40 2001 deliver.c:641 delivering to instance 's2s'
Wed Jan 24 12:30:40 2001 dialback_out.c:181 dbout packet[208.245.212.100]:
<presence from='XXX' to='jsm at update.jabber.org/1.4pre2'/>
Wed Jan 24 12:30:40 2001 dialback_out.c:201 outgoing packet with key
update.jabber.org/XXX and located existing 0
Wed Jan 24 12:30:40 2001 dialback_out.c:88 Attempting to connect to
update.jabber.org/XXX at 208.245.212.100
Wed Jan 24 12:30:40 2001 mio.c:508 calling the connect handler for
mio object 80E7A18
Wed Jan 24 12:30:40 2001 dialback_out.c:303 dbout read: fd 10 flag 0
key update.jabber.org/XXX
Wed Jan 24 12:30:40 2001 dialback_out.c:308 NEW outgoing server socket\
connected at 10
Wed Jan 24 12:30:40 2001 mio.c:907 mio_write called on x: 0 buffer:
Wed Jan 24 12:30:40 2001 mio.c:630 socket 10 has restore karma -100 -=> 5
Wed Jan 24 12:30:40 2001 mio.c:288 write_dump writing data: <?xml
version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams'
id='3A6F1140' xmlns='jabber:server' to='update.jabber.org'
xmlns:db='jabber:server:dialback'>
Wed Jan 24 12:30:40 2001 mio.c:704 MIO read from socket 10:
<?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams'
id='ef70d07953c6251ae0db9dc4cc83679b2b2cb792' xmlns='jabber:server'
from='update.jabber.org' xmlns:db='jabber:server:dialback'>
Wed Jan 24 12:30:40 2001 dialback_out.c:303 dbout read: fd 10 flag 2 key
update.jabber.org/XXX
Wed Jan 24 12:30:40 2001 dialback_out.c:318 Incoming root <stream:stream
xmlns:stream='http://etherx.jabber.org/streams'
id='ef70d07953c6251ae0db9dc4cc83679b2b
.
.
.
Wed Jan 24 12:30:44 2001 dialback_out.c:303 dbout read: fd 10 flag 4
key update.jabber.org/XXX
Wed Jan 24 12:30:44 2001 deliver.c:570 delivery failed (Server Connect
Failed)
Wed Jan 24 12:30:44 2001 log.c:105 <log type='notice'
from='update.jabber.org'>bouncing a packet to
jsm at update.jabber.org/1.4pre2 from XXX: Server Connect Failed</log>
My goal is simple. To set up a server where one or more local clients can
talk to each other without any internet involvement.
--
Keith Barrett
Red Hat Inc.
More information about the JDev
mailing list