[ejabberd] No Connection Attempts to LDAP Server

Jiann-Ming Su su_js1 at yahoo.com
Sun Apr 15 09:55:44 MSK 2012

> From: Konstantin Khomoutov <flatworm at users.sourceforge.net>
>To: Jiann-Ming Su <su_js1 at yahoo.com>; ejabberd at jabber.ru 
>Sent: Saturday, April 14, 2012 6:53 PM
>Subject: Re: [ejabberd] No Connection Attempts to LDAP Server
>On Sat, Apr 14, 2012 at 02:02:59PM -0700, Jiann-Ming Su wrote:
>> Thanks for the quick response.  That got the ejabberd server up and
>> running.  However, starttls connections from the xmpp client was not
>> working.  It looks like 2.1.10 is suffering from the same problem
>> described here:  http://www.ejabberd.im/node/4094#comment-58186
>> Why was 2.1.10 packaged with libraries that it can't use??
>Judging from the comment at the link you pointed to, this is a typical
>problem for Linux-based OSes (and many other F/OSS operating systems):
>the lack of ABI compatibility based on an implicit assumption that
>the source code of all the components is available at any time and
>hence *the distribution as a whole* can be made consistent when its
>parts change their ABI.  The generic package provided by Process-One
>probably tries to do its best in terms of compatibility but it can't
>target all those myriads of Linux-based distros at once and therefore
>can't provide 100% compatibiliy with any of them.  Distributing its own
>pet build of openssl along that package on any system but Windows
>is insane (ask the security team of your OS about why it is that).
>There are several possible ways to solve this problem:
>1) You have the source code--build ejabberd yourself and it will use
>   the stock libraries of your OS.  Provided that they're not outdated
>   (ejabberd does have requirements on the minimal version of Erlang
>   runtime for instance) everything should work OK.
>2) Stop trying to swim against the stream and use ejabberd package
>   provided by your distro: its maintainer and testers made sure
>   the package builds and works OK with the rest of the OS it targets.
>   If your OS does not package ejabberd, you might as well consider
>   changing the OS.
>3) Buy support contract from Process-One or from someone else
>   to make sure the combination of ejabberd and OS you need to
>   be working is working.

If the statically linked libraries are going to be provided, why not provide the correct ones?  

The ejabberd distribution package came with openssl-0.9.7 when the ejabberd binary (or erlang)
was looking for 0.9.8.

More information about the ejabberd mailing list