close to good news (was RE: [JDEV] AIM Transport Release)

Jay Chalfant jchalfan at outbackinc.com
Thu Nov 16 19:51:56 CST 2000


Since I couldn't build the latest aim-transport but did have the new
libetherx-1.2, I decided to try to build the previous aim-transport
(11/9/00) that initially complained about pool_label(). Well, that works. I
now can run both jabberd (1.2) and a relatively current aim-transport. The
only missing item is configuration which is the focus of this post..

I changed the default jabber.xml as follows:

- update the hostname to 'roo' (the local hostname)
- uncomment the aim transport agent and change the jid to 'aim.roo'

I then start jabberd (./jabberd/jabberd -D) and aimtrans
(/usr/local/bin/aimtrans -n aim.roo -D). When I start aimtrans, I see a
flurry of activity in the jabberd trace and it all looks good. I then
connect to jabberd with the latest WinJab and it all looks good. I then try
to register the aim transport from the WinJab client and it doesn't look
good. It appears that even though aimtrans has connected to jabberd, jabberd
doesn't know how to find/route packets to aimtrans when the time comes. This
is the relevant part of the log:

~~~~~~~~~~~~~~~
Thu Nov 16 17:23:10 2000  users.c:82 checking users for host roo
Thu Nov 16 17:23:10 2000  usercount 1	total users
Thu Nov 16 17:23:15 2000  users.c:82 checking users for host roo
Thu Nov 16 17:23:15 2000  usercount 1	total users
Thu Nov 16 17:23:15 2000  io_select.c:339 io_main checking sockets
Thu Nov 16 17:23:15 2000  deliver.c:472 DELIVER 4:roo <route
to='a at roo/8196528' from='12 at c2s/80EF318'><iq type='get' id='wjAgent_1_1'
to='aim.roo'><query xmlns='jabber:iq:register'/></iq></route>
Thu Nov 16 17:23:15 2000  deliver.c:344 delivering to instance 'sessions'
Thu Nov 16 17:23:15 2000  deliver.c:84 (8081E28)incoming packet <route
to='a at roo/8196528' from='12 at c2s/80EF318'><iq type='get' id='wjAgent_1_1'
to='aim.roo'><query xmlns='jabber:iq:register'/></iq></route>
Thu Nov 16 17:23:15 2000  users.c:147 js_user(a at roo/8196528,80F1FC0)
Thu Nov 16 17:23:15 2000  mtq 80F28E0 entering from pth
Thu Nov 16 17:23:15 2000  mtq 80F28E0 queue call 8198FD8
Thu Nov 16 17:23:15 2000  sessions.c:289 THREAD:SESSION:FROM received a
packet!
Thu Nov 16 17:23:15 2000  modules.c:124 mapi_call 1
Thu Nov 16 17:23:15 2000  modules.c:147 MAPI 81967F8
Thu Nov 16 17:23:15 2000  modules.c:147 MAPI 8196808
Thu Nov 16 17:23:15 2000  modules.c:147 MAPI 8196828
Thu Nov 16 17:23:15 2000  modules.c:147 MAPI 8196838
Thu Nov 16 17:23:15 2000  modules.c:163 mapi_call returning unhandled
Thu Nov 16 17:23:15 2000  deliver.c:262
deliver(to[aim.roo],from[a at roo/Work],type[4],packet[<iq type='get'
id='wjAgent_1_1' to='aim.roo' from='a at roo/Work'><query
xmlns='jabber:iq:register'/></iq>])
Thu Nov 16 17:23:15 2000  deliver.c:472 DELIVER 1:aim.roo <iq type='get'
id='wjAgent_1_1' to='aim.roo' from='a at roo/Work'><query
xmlns='jabber:iq:register'/></iq>
Thu Nov 16 17:23:15 2000  deliver.c:344 delivering to instance 'dnsrv'
Thu Nov 16 17:23:15 2000  mtq 80F28E0 leaving to pth
Thu Nov 16 17:23:15 2000  dnsrv.c:330 dnsrv: Recv'd a lookup request:
aim.roo
Thu Nov 16 17:23:15 2000  dnsrv.c:360 dnsrv: Creating lookup request queue
for aim.roo
Thu Nov 16 17:23:15 2000  dnsrv.c:370 dnsrv: Transmitting lookup request for
aim.roo to coprocess
Thu Nov 16 17:23:15 2000  dnsrv.c:106 dnsrv: Recv'd lookup request for
aim.roo
Thu Nov 16 17:23:15 2000  srv_resolv.c:101 srv: SRV resolution of
_jabber._tcp.aim.roo
Thu Nov 16 17:23:15 2000  srv_resolv.c:88 srv: Standard resolution of
aim.roo
Thu Nov 16 17:23:15 2000  srv_resolv.c:92 srv: Unable to resolve: aim.roo
Thu Nov 16 17:23:15 2000  dnsrv.c:255 dnsrv: Unable to resolve ip for
aim.roo

Thu Nov 16 17:23:15 2000  log.c:105 <log type='warn' from='-internal'>Packet
Delivery Failed, invalid packet, dropping &lt;route type=&apos;error&apos;
iperror=&apos;&apos;&gt;&lt;iq type=&apos;get&apos;
id=&apos;wjAgent_1_1&apos; to=&apos;aim.roo&apos;
from=&apos;a at roo/Work&apos;&gt;&lt;query
xmlns=&apos;jabber:iq:register&apos;/&gt;&lt;/iq&gt;&lt;error
code=&apos;502&apos;&gt;Unable to resolve
hostname.&lt;/error&gt;&lt;/route&gt;</log>
Thu Nov 16 17:23:15 2000  deliver.c:472 DELIVER 3:-internal <log type='warn'
from='-internal'>Packet Delivery Failed, invalid packet, dropping &lt;route
type=&apos;error&apos; iperror=&apos;&apos;&gt;&lt;iq type=&apos;get&apos;
id=&apos;wjAgent_1_1&apos; to=&apos;aim.roo&apos;
from=&apos;a at roo/Work&apos;&gt;&lt;query
xmlns=&apos;jabber:iq:register&apos;/&gt;&lt;/iq&gt;&lt;error
code=&apos;502&apos;&gt;Unable to resolve
hostname.&lt;/error&gt;&lt;/route&gt;</log>
Thu Nov 16 17:23:15 2000  deliver.c:344 delivering to instance 'logger'
20001117T01:23:15: [warn] (-internal): Packet Delivery Failed, invalid
packet, dropping <route type='error' iperror=''><iq type='get'
id='wjAgent_1_1' to='aim.roo' from='a at roo/Work'><query
xmlns='jabber:iq:register'/></iq><error code='502'>Unable to resolve
hostname.</error></route>
Thu Nov 16 17:23:20 2000  users.c:82 checking users for host roo
Thu Nov 16 17:23:20 2000  usercount 1	total users
Thu Nov 16 17:23:25 2000  users.c:82 checking users for host roo
Thu Nov 16 17:23:25 2000  usercount 1	total users
~~~~~~~~~~~~~~~

As a wild guess, I did try to add aim.roo to /etc/hosts (!?) but that just
produced a different stream of error messages. I'm looking for any
aim-transport/jabberd config tips of any sort! The comment in the jabber.xml
file that these aren't real agents and that you will be told what to enter
when you install a real agent leave me with the feeling that I am probably a
long way off.

Thanks in advance to any who find the time to respond.

-J

----------------------
Jay Chalfant
OutBack Resource Group
www.outbackinc.com









> -----Original Message-----
> From: Jay Chalfant [mailto:jchalfan at outbackinc.com]
> Sent: Thursday, November 16, 2000 4:37 PM
> To: 'jdev at jabber.org'
> Subject: RE: [JDEV] AIM Transport Release
> 
> 
> Temas,
> 
> Thanks much for the quick turnaround. However, it looks like 
> there are some
> #defines missing:
> 
> sessions.c: In function `at_parse_authresp':
> sessions.c:174: `AIM_CB_SPECIAL_CONNCOMPLETE' undeclared 
> (first use in this
> function)
> sessions.c:174: (Each undeclared identifier is reported only once
> sessions.c:174: for each function it appears in.)
> sessions.c: In function `at_session_create':
> sessions.c:459: `AIM_SESS_FLAGS_NONBLOCKCONNECT' undeclared 
> (first use in
> this function)
> sessions.c:459: too many arguments to function `aim_session_init'
> sessions.c:509: `AIM_CB_SPECIAL_FLAPVER' undeclared (first use in this
> function)
> sessions.c:511: `AIM_CB_SPECIAL_CONNCOMPLETE' undeclared 
> (first use in this
> function)
> sessions.c: In function `_aim_select':
> sessions.c:853: `AIM_CONN_STATUS_INPROGRESS' undeclared 
> (first use in this
> function)
> make[1]: *** [sessions.o] Error 1
> make: *** [all-recursive] Error 1
> 
> Any chance I could get these tonight?
> 
> thanks,
> 
> -J
> 
> ----------------------
> Jay Chalfant
> OutBack Resource Group
> www.outbackinc.com
> 
> 
> > -----Original Message-----
> > From: Thomas Muldowney [mailto:temas at box5.net]
> > Sent: Thursday, November 16, 2000 1:11 PM
> > To: Jabber Development
> > Subject: [JDEV] AIM Transport Release
> > 
> > 
> > I just put AIM Transport version 0.8 on download.jabber.org.  
> > Have fun!
> > 
> > --temas
> > 
> > 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 




More information about the JDev mailing list