For Programmers: Free Programming Magazines  


Home > Archive > PERL Miscellaneous > February 2005 > Problem with jabberd-1.4.2, xdb_auth_cpile.smb and Jabber::Connection









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Problem with jabberd-1.4.2, xdb_auth_cpile.smb and Jabber::Connection
tylernt

2004-05-13, 7:32 pm

I'm afraid xdb_auth_cpile.pl isn't working with my Jabber server. It
worked ok in a small test environment but when I got more than, oh, 3
or 4 users logged on to the Jabber server, Jabber would get slower and
slower and eventually stop allowing logins and stop passing messages
after 1-5 minutes. It seemed to be related to someone trying to log in
with a bad username/password... the server seemed to die very quickly
after a failed login attempt was logged in record.log. Sometimes, the
xdb_auth_cpile.pl process would die, other times it would keep
running.

I noticed sometimes when I stopped the unresponsive jabberd, I would
get this:

Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.0/Jabber/Connection.pm line 416.

Use of uninitialized value in subroutine entry at
/usr/lib/perl5/site_perl/5.8.0/i386-linux/XML/Parser/Expat.pm line
614.

I started out with Jabber::Connection 0.03 but encountered problems
with jabberd segfaulting (the 'memory leak issue', presumably), so I
switched to 0.04, which caused the above problem.

I'm running jabberd-1.4.2 and using xdb_auth_cpile to authenticate
against a Win2k AD domain with smb. Jabberd worked fine prior to the
upgrade to xdb_auth_cpile.

Any ideas or suggestions?
maalox

2005-02-24, 11:18 am

quote:
Originally posted by tylernt
I'm afraid xdb_auth_cpile.pl isn't working with my Jabber server. It
worked ok in a small test environment but when I got more than, oh, 3
or 4 users logged on to the Jabber server, Jabber would get slower and
slower and eventually stop allowing logins and stop passing messages
after 1-5 minutes. It seemed to be related to someone trying to log in
with a bad username/password... the server seemed to die very quickly
after a failed login attempt was logged in record.log. Sometimes, the
xdb_auth_cpile.pl process would die, other times it would keep
running.

I noticed sometimes when I stopped the unresponsive jabberd, I would
get this:

Use of uninitialized value in concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.0/Jabber/Connection.pm line 416.

Use of uninitialized value in subroutine entry at
/usr/lib/perl5/site_perl/5.8.0/i386-linux/XML/Parser/Expat.pm line
614.

I started out with Jabber::Connection 0.03 but encountered problems
with jabberd segfaulting (the 'memory leak issue', presumably), so I
switched to 0.04, which caused the above problem.

I'm running jabberd-1.4.2 and using xdb_auth_cpile to authenticate
against a Win2k AD domain with smb. Jabberd worked fine prior to the
upgrade to xdb_auth_cpile.

Any ideas or suggestions?




Tylernt,
I am also trying to use xdb_auth_cpile and an seeing the same errors that you described. I a using jadderd-1.4.3 and jadc2s on Red Hat Enterprise Linux 3. I am using xdb_auth_cpile to authenticate against an iplanet ldap server. I am also using Jabber::Connection 0.04. I am seeing the exact same Perl errors that you are. Have you found a fix for this problem that you would be willing to share? I am scheduled to go production with my Jabber server in the near future so I really need to resolve this problem. Any help you could provide will be much appreciated. You can contact me directly via e-mail at grant@uark.edu.
Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com