ejabberd - Comments for "Install on RedHat - accounts get created, but login not possible"

This log might help (look

sander — Tue, 27 Jun 2006 15:20:50 +0000

This log might help (look for "PKIX1Explicit88.hrl").

--
sander

Well, please regard that

CCRDude — Sat, 11 Feb 2006 18:10:28 +0000

Well, please regard that first sentence as irony anyway ;)

I somehow didn't see the tarball, but only the binaries. Seems I overlooked the tarball, otherwise I would've prefered it of course (unless there may have been a RHEL4x86_64 rpm, which I would find quite unlikely ;) ).

Manual compiling led to a problem already described here in the forum (can't find include lib "ssl/pkix/PKIX1Explicit88.hrl"), with the mentioned requirement of openssl 0.9.7g. RedHat EL4 only offers openssl-0.9.7a-43.4.x86_64.

So I deed a ./configure --without-openssl --disable-tls, but that did not really help.

I guess I need to either upgrade to an inofficial newer openssl package (which then would fall out of RedHats autoupdating), or look for another Jabber server...

Quote:"runs out-of-the-box

teo — Sat, 11 Feb 2006 07:47:48 +0000

Quote:

"runs out-of-the-box under every Linux/x86 distribution"

Never trust advertisements.

Quote:

** Reason for termination =
** {badarg,[{ets,lookup,[crypto_server_table,port]},
{crypto,control,2},

Looks like erlang from the installer can't use your openssl library. I don't know how to fix that, though.

Anyway, I would never recommend to install binary package if it didn't come from your linux distribution. Windows users generally can't build ejabberd, so they have to use binary installer.