oops (was: RE: [JDEV] AIM Transport Release)
Jay Chalfant
jchalfan at outbackinc.com
Fri Nov 17 14:13:28 CST 2000
Dennis, Temas..
Thanks for these tips, I think I am closer now than I was before. I have
followed the aimtrans README and Dennis' comments and this is where I am at:
o For some reason, adns will not read from /etc/hosts on my system.
/etc/host.conf indicates "order hosts bind" but the adns test tool,
adnshost, will not resolve from /etc/hosts. Therefore, I added a new A
record for 'aimtrans' to our DNS and gave it (a) the IP of the jabberd
server and then (b) 127.0.01. In either case, the result was the same and in
both cases I provide the correct IP in the jabber.xml service element (see
below).
o In jabber.xml, I added 'aimtrans.internal.outbackinc.com' to both the
services and agents jid's as below. Initially, I tried only the service
element, but this resulted in no listing of the AIM Transport to the WinJab
client. Adding the agent element corrected this.
<service id='aimtrans.internal.outbackinc.com'>
<accept>
<ip>127.0.0.1</ip>
<port>7009</port>
<secret>test</secret>
</accept>
</service>
<agent jid="aimtrans.internal.outbackinc.com">
<name>AIM Transport</name>
<description>This is the AIM Transport</description>
<transport>AIM/AOL ScreenName</transport>
<service>aim</service>
<register/>
</agent>
o With these settings, I start jabberd and aimtrans as follows:
[root at roo jabber-1.2]# ./jabberd/jabberd -D
[root at roo adns-1.0]# /usr/local/bin/aimtrans -D -n
aimtrans.internal.outbackinc.com -e aimtrans.internal.outbackinc.com -p 7009
-s test
It appears that aimtrans connects to jabberd without issue. When I try to
register for the AIM Transport from the WinJab client, I get an error (from
WinJab debux XML):
SENT: <iq type="get" id="wjAgent_1_1"
to="aimtrans.internal.outbackinc.com"><query
xmlns="jabber:iq:register"></query></iq>
RECV: <iq type='error' id='wjAgent_1_1' to='a at roo/Work'
from='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/><error code='502'>External Server
Error</error></iq>
This is better than before when I never received a response from the Jabber
Server. However, it still looks like jabberd is still having trouble finding
the service because it 'bounces' the message. Here is the relevant sections
from the jabberd and aimtrans debug output:
jabberd:
========
[root at roo jabber-1.2]# ./jabberd/jabberd -D
..
Fri Nov 17 03:21:32 2000 io_select.c:339 io_main checking sockets
Fri Nov 17 03:21:32 2000 deliver.c:472 DELIVER 4:roo <route
to='a at roo/81A7B20' from='13 at c2s/8100910'><iq type='get' id='wjAgent_1_1'
to='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/></iq></route>
Fri Nov 17 03:21:32 2000 deliver.c:344 delivering to instance 'sessions'
Fri Nov 17 03:21:32 2000 deliver.c:84 (8092D10)incoming packet <route
to='a at roo/81A7B20' from='13 at c2s/8100910'><iq type='get' id='wjAgent_1_1'
to='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/></iq></route>
Fri Nov 17 03:21:32 2000 users.c:147 js_user(a at roo/81A7B20,81035B8)
Fri Nov 17 03:21:32 2000 mtq 8103ED8 entering from pth
Fri Nov 17 03:21:32 2000 mtq 8103ED8 queue call 81BBA70
Fri Nov 17 03:21:32 2000 sessions.c:289 THREAD:SESSION:FROM received a
packet!
Fri Nov 17 03:21:32 2000 modules.c:124 mapi_call 1
Fri Nov 17 03:21:32 2000 modules.c:147 MAPI 81A7DF0
Fri Nov 17 03:21:32 2000 modules.c:147 MAPI 81A7E00
Fri Nov 17 03:21:32 2000 modules.c:147 MAPI 81A7E20
Fri Nov 17 03:21:32 2000 modules.c:147 MAPI 81A7E30
Fri Nov 17 03:21:32 2000 modules.c:163 mapi_call returning unhandled
Fri Nov 17 03:21:32 2000 deliver.c:262
deliver(to[aimtrans.internal.outbackinc.com],from[a at roo/Work],type[4],packet
[<iq type='get' id='wjAgent_1_1' to='aimtrans.internal.outbackinc.com'
from='a at roo/Work'><query xmlns='jabber:iq:register'/></iq>])
Fri Nov 17 03:21:32 2000 deliver.c:472 DELIVER
1:aimtrans.internal.outbackinc.com <iq type='get' id='wjAgent_1_1'
to='aimtrans.internal.outbackinc.com' from='a at roo/Work'><query
xmlns='jabber:iq:register'/></iq>
Fri Nov 17 03:21:32 2000 deliver.c:344 delivering to instance
'aimtrans.internal.outbackinc.com'
Fri Nov 17 03:21:32 2000 mtq 8103ED8 leaving to pth
Fri Nov 17 03:21:35 2000 users.c:82 checking users for host roo
Fri Nov 17 03:21:35 2000 usercount 1 total users
Fri Nov 17 03:21:40 2000 users.c:82 checking users for host roo
Fri Nov 17 03:21:40 2000 usercount 1 total users
Fri Nov 17 03:21:42 2000 log.c:105 <log type='warn'
from='-internal'>base_accept Bouncing packet intended for
aimtrans.internal.outbackinc.com</log>
Fri Nov 17 03:21:42 2000 deliver.c:472 DELIVER 3:-internal <log type='warn'
from='-internal'>base_accept Bouncing packet intended for
aimtrans.internal.outbackinc.com</log>
Fri Nov 17 03:21:42 2000 deliver.c:344 delivering to instance 'logger'
20001117T11:21:42: [warn] (-internal): base_accept Bouncing packet intended
for aimtrans.internal.outbackinc.com
Fri Nov 17 03:21:42 2000 deliver.c:278 delivery failed (External Server
Error)
Fri Nov 17 03:21:42 2000 log.c:105 <log type='notice'
from='aimtrans.internal.outbackinc.com'>bouncing a packet to
aimtrans.internal.outbackinc.com from a at roo/Work: External Server
Error</log>
Fri Nov 17 03:21:42 2000 deliver.c:472 DELIVER
3:aimtrans.internal.outbackinc.com <log type='notice'
from='aimtrans.internal.outbackinc.com'>bouncing a packet to
aimtrans.internal.outbackinc.com from a at roo/Work: External Server
Error</log>
Fri Nov 17 03:21:42 2000 deliver.c:344 delivering to instance 'logger'
20001117T11:21:42: [notice] (aimtrans.internal.outbackinc.com): bouncing a
packet to aimtrans.internal.outbackinc.com from a at roo/Work: External Server
Error
Fri Nov 17 03:21:42 2000 deliver.c:472 DELIVER 1:roo <iq type='error'
id='wjAgent_1_1' to='a at roo/Work'
from='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/><error code='502'>External Server
Error</error></iq>
Fri Nov 17 03:21:42 2000 deliver.c:344 delivering to instance 'sessions'
Fri Nov 17 03:21:42 2000 deliver.c:84 (8092D10)incoming packet <iq
type='error' id='wjAgent_1_1' to='a at roo/Work'
from='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/><error code='502'>External Server
Error</error></iq>
Fri Nov 17 03:21:42 2000 users.c:147 js_user(a at roo/Work,81035B8)
Fri Nov 17 03:21:42 2000 deliver.c:44 delivering locally to a at roo/Work
Fri Nov 17 03:21:42 2000 modules.c:124 mapi_call 3
Fri Nov 17 03:21:42 2000 modules.c:163 mapi_call returning unhandled
Fri Nov 17 03:21:42 2000 mtq 8103ED8 entering from pth
Fri Nov 17 03:21:42 2000 mtq 8103ED8 queue call 81BCCB8
Fri Nov 17 03:21:42 2000 sessions.c:337 THREAD:SESSION:TO received data
from aimtrans.internal.outbackinc.com!
Fri Nov 17 03:21:42 2000 modules.c:124 mapi_call 0
Fri Nov 17 03:21:42 2000 modules.c:147 MAPI 81A7E10
Fri Nov 17 03:21:42 2000 modules.c:163 mapi_call returning unhandled
Fri Nov 17 03:21:42 2000 deliver.c:472 DELIVER 4:c2s <route
from='a at roo/81A7B20' to='13 at c2s/8100910'><iq type='error' id='wjAgent_1_1'
to='a at roo/Work' from='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/><error code='502'>External Server
Error</error></iq></route>
Fri Nov 17 03:21:42 2000 deliver.c:344 delivering to instance 'c2s'
Fri Nov 17 03:21:42 2000 client.c:124 Found the sock for this user
Fri Nov 17 03:21:42 2000 mtq 8103ED8 leaving to pth
Fri Nov 17 03:21:42 2000 io_select.c:339 io_main checking sockets
Fri Nov 17 03:21:42 2000 io_select.c:105 WRITE 13 len 177 of <iq
type='error' id='wjAgent_1_1' to='a at roo/Work'
from='aimtrans.internal.outbackinc.com'><query
xmlns='jabber:iq:register'/><error code='502'>External Server
Error</error></iq>
aimtrans:
=========
[root at roo adns-1.0]# /usr/local/bin/aimtrans -D -n
aimtrans.internal.outbackinc.com -e aimtrans.internal.outbackinc.com -p 7009
-s test
Fri Nov 17 03:20:34 2000 debug/log.c:79 log_init
Fri Nov 17 03:20:34 2000 debug/main.c:59 Loading Transport
Fri Nov 17 03:20:34 2000 debug/ehandler.c:44
ehandler_new(aimtrans.internal.outbackinc.com,jabber:server)
Fri Nov 17 03:20:34 2000 debug/ehlist.c:26
list_add(aimtrans.internal.outbackinc.com)
Fri Nov 17 03:20:34 2000 debug/etherxs.c:124 attempting socket connect to
aimtrans.internal.outbackinc.com for transport
aimtrans.internal.outbackinc.com
Fri Nov 17 03:20:34 2000 debug/xmlstream.c:26 xmlstream_connect
Fri Nov 17 03:20:34 2000 debug/tstream.c:63 tstream_new
Fri Nov 17 03:20:34 2000 debug/xmlstream.c:101 head: <?xml
version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' id='3A151482'
xmlns='jabber:server' to='aimtrans.internal.outbackinc.com'
from='aimtrans.internal.outbackinc.com'
xmlns:etherx='http://etherx.jabber.org/'
etherx:secret='11ff64a0a85d10d2c7d7531279387d26976e7e43'>
Fri Nov 17 03:20:34 2000 debug/tstream.c:133 tstream_write_buffer
Fri Nov 17 03:20:34 2000 debug/ehandler.c:72 spun off connection attempt
Fri Nov 17 03:20:34 2000 debug/external.c:23 [AIM] Loaded transport with
aimtrans.internal.outbackinc.com as host alias
Fri Nov 17 03:20:34 2000 debug/main.c:75 Main loop waiting
Fri Nov 17 03:20:34 2000 debug/unknown.c:11 THREAD:UNKNOWN starting
Fri Nov 17 03:20:34 2000 debug/tstream.c:212 tstream_main: startup
Fri Nov 17 03:20:34 2000 debug/xmlstream.c:222 xmlstream_main: startup
Fri Nov 17 03:20:34 2000 debug/tstream.c:335 tstream_connect:
ADNS[aimtrans.internal.outbackinc.com:5269]
Fri Nov 17 03:20:34 2000 debug/tstream.c:357 tstream_connect: ADNS A lookup
loop
Fri Nov 17 03:20:34 2000 debug/tstream.c:365 tstream_connect: ADNS found
some responses, attempting to connect
Fri Nov 17 03:20:34 2000 debug/tstream.c:492 tstream_socket 5269 127.0.0.1
Fri Nov 17 03:20:34 2000 debug/tstream.c:374 tstream_connectd:
ADNS[127.0.0.1]
Fri Nov 17 03:20:34 2000 debug/tstream.c:263 tstream write event 0
Fri Nov 17 03:20:34 2000 debug/tstream.c:285 tstream_write 296 blocks
Fri Nov 17 03:20:34 2000 debug/tstream.c:285 tstream_write 0 blocks
Fri Nov 17 03:20:34 2000 debug/tstream.c:247 tstream read event
Fri Nov 17 03:20:34 2000 debug/xmlstream.c:222 xmlstream_main: startup
Fri Nov 17 03:20:34 2000 debug/etherxs.c:61 got root tag from etherx!
Fri Nov 17 03:20:34 2000 debug/tstream.c:188 tstream_oob_flush
Fri Nov 17 03:22:07 2000 error/aimtrans Received KILL, shutting down
[root at roo adns-1.0]#
We are going to be running an important demo this weekend and are still
hoping to be able to run that demo on 1.2 and the latest aimtrans so we have
the 'presence' and other fixes. If anyone can provide somre more pointers,
it would really be appreciated.
And again, thanks to all who have helped thus far and thanks in advance to
all who reply to this post.
-J
----------------------
Jay Chalfant
OutBack Resource Group
www.outbackinc.com
> -----Original Message-----
> From: Dennis Noordsij [mailto:dennis.noordsij at wiral.com]
> Sent: Friday, November 17, 2000 1:28 AM
> To: jdev at jabber.org; Jay Chalfant
> Subject: Re: oops (was: RE: [JDEV] AIM Transport Release)
>
>
> On Friday 17 November 2000 04:41, Jay Chalfant wrote:
> > OOPS!! This is _my_ mistake.. in my excitement over the new
> packages I
> > forgot to build libfaim which is where these defines are
> found. Now that I
> > am back on track, aimtrans-0.8 builds flawlessly. However,
> even with 0.8 I
> > still have the configuration issues reported in the post
> earlier ("close to
> > good news"). That is, jabberd cannot dns resolve the aim
> transport. Still
> > looking for help on that one.
>
> Jay, make sure the domain aim.roo actually somehow exists.
> That is, points to
> an IP number.
>
> How I do it is like this, my agents point to irc.mydomain,
> icq.mydomain, etc.
> "Mydomain" points to my actual network address, say for
> example 192.168.10.1.
> I set up my /etc/hosts to contain:
>
> 127.0.0.1 localhost irc.mydomain icq.mydomain
>
> And in jabber.xml I tell it (in the service JID's) to listen
> on 127.0.0.1
>
> If you told jabber to listen for the AIM transport on
> 127.0.0.1, I recommend
> adding aim.roo to your /etc/hosts file. Noone else needs the
> domain name like
> that, only jabber, so its fine to leave it on that machine
> only (ie the rest
> of the world needs no clue as to where or what aim.roo is, just roo).
>
> Works for me :-)
>
> Dennis
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
More information about the JDev
mailing list