Hello,
"runs out-of-the-box under every Linux/x86 distribution" is what I have read about the ejabberd-linux-....-.bin. So I did that - installed it through that .bin file, and started it with /opt/ejabberd-1.0.0/bin/start . Text browser opened. Can open the admin interface from another machine inside the browser as well.
Next thing - I used Trillian to create a new account user@domain (anonymized for the forum - of course I use a valid internal subdomain that's pingable from all clients). No problem - account appears in admin interface. But whenever I try to connect, I get:
[18:55] *** Creating connection "user@domain/Trillian" [18:57] *** Connection to server lost. [18:57] *** Disconnected from server. [18:57] *** Reconnecting to domain, attempt 0... [18:57] *** Creating connection "user@domain/Trillian" [18:57] *** Connect: Unable to contact domain to get a connection at all
So I took a Linux box, fired up gaim, created an account user2@domain. Account was successfully created (so there IS a connection to the server). But when I try to use that account, I get "Fehler beim Lesen" ("Error while reading").
One of my ideas was ACLs... but while I find {access,register,[{allow,all}]}, I found none about connecting.
The ejabberd log file tells me:
** Reason for termination =
** {badarg,[{ets,lookup,[crypto_server_table,port]},
{crypto,control,2},
{cyrsasl_digest,response,6},
{cyrsasl_digest,mech_step,2},
{cyrsasl,server_step,2},
{ejabberd_c2s,wait_for_sasl_response,2},
{gen_fsm,handle_msg,7},
{proc_lib,init_p,5}]}I put in a ssl.pem file, I changed the config settings to point there as well (even though those lines are commented out in the config file), to no avail.
Any hints on how I could proceed to get this running would be greatly appreciated.
Quote:"runs out-of-the-box
"runs out-of-the-box under every Linux/x86 distribution"
Never trust advertisements.
** 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.
Well, please regard that
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...
This log might help (look
might help (look for "PKIX1Explicit88.hrl").
--
sander