ejabberd - Comments for "read error"

Tried new version didn't solve crypto_table problem

ESJHJ — Thu, 21 Jun 2007 18:57:48 +0000

Just tried your new version without any luck. Downloaded 1.1.2 and worked fine. It was nice to see a ok when running crypto:start().
Fedora 4

New ejabberd 1.1.1 linux installer, needs test!

mfoss — Fri, 15 Jun 2007 13:09:06 +0000

There is a new version of the ejabberd 1.1.3 linux installer on the bug tracker: ejabberd_std-1.1.3-linux-x86-installer.bin.

Can all of you that had the crypto_table problem, please try it, and check if it works correctly or still has the
crypto_table problem?

If you try it, please add a comment here telling if it works or not.

Hi All, I had the same

Aaron@Univ Helsiniki — Thu, 14 Jun 2007 08:49:21 +0000

Hi All,

I had the same trouble - "Read Error" on Ejabberd.

After observing the log file of ejabberd, found that there is a conflict between erlang and my OS Ubuntu 7.04. Then after downgrading the OS to Ubuntu 6.06, and reinstalling the ejabberd server, everything works fine now. Guess the lastest version is not compatible to the erlang and ejabberd.

If other methods not working, this one could be a solution although it takes time and you might find downgrading the system to a elder version weird.

Aaron

Try to install ejabberd 1.1.2

mfoss — Tue, 12 Jun 2007 07:32:34 +0000

I have chatted with another person that had the same problem using

OpenSSL 0.9.7a
CentOS 4
Linux 2.6.9 i686
ejabberd 1.1.3 binary installer

He then uninstalled ejabberd 1.1.3, installed 1.1.2 and everything works fine now!

Until the problem is completely found and fixed, you can try to install 1.1.2.

read error

chhatrashal — Tue, 12 Jun 2007 03:04:33 +0000

i had installed using process-one installer..

tell me whether the script is to be written on command prompt as it is giving command not found error.. or have to write a bash script

thanks

The error indicates a

mfoss — Mon, 11 Jun 2007 15:57:05 +0000

The error indicates a problem loading some encryption modules. As you can see searching the forums, this error message seems more related to some Linux distributions, Suse, Redhat, Fedora... I think it isn't your fault.

Maybe you can connect to the server if you configure the Jabber client to not use SSL, STARTTLS or SASL encryption.

Did you install ejabberd using a Suse package, or using the Process-one installer?

Try this, do you get any error, or does it work correctly like me?

$ erl
Erlang (BEAM) emulator version 5.5.4 [source] [async-threads:0] [kernel-poll:false]

Eshell V5.5.4  (abort with ^G)
1> crypto:start().
ok
2> q().
ok

read error

chhatrashal — Mon, 11 Jun 2007 12:26:56 +0000

i tried from kopote still no connection but the account is created. plz guide

read error

chhatrashal — Mon, 11 Jun 2007 12:01:10 +0000

i put localhost as domain simply to test the installation.. and GAim was on the same machine...after checking the log the follwoing error was showing

=ERROR REPORT==== 2007-06-11 09:38:51 ===
** State machine <0.313.0> terminating 
** Last event in was {xmlstreamelement,
                         {xmlelement,"response",
                                     [{"xmlns",
                                       "urn:ietf:params:xml:ns:xmpp-sasl"}],
                                     [{xmlcdata,
                                          <<"dXNlcm5hbWU9ImNoaGF0cmFzaGFsIixyZWFsbT0ibG9jYWxob
3N0Iixub25jZT0iMzI0ODc4MDY2MSIsY25vbmNlPSIzZTdhNzg3ZTExODE1Mz
Q5MzFhZThiOWE2MyIsbmM9MDAwMDAwMDEscW9wPWF1dGgsZGlnZXN0LXVyaT0
ieG1wcC9sb2NhbGhvc3QiLHJlc3BvbnNlPTZmN2NkM2ZhNDVkMWFhYjQ2MDc1
OWQwMjUzYWJjNmQzLGNoYXJzZXQ9dXRmLTg=">>}]}}

** When State == wait_for_sasl_response
**      Data  == {state,#Port<0.324>,
                        <0.314.0>,
                        gen_tcp,
                        "248976759",
                        {sasl_state,"jabber",
                                    "localhost",
                                    [],
                                    #Fun,
                                    #Fun,
                                    cyrsasl_digest,
                                    {state,
                                        3,
                                        "3248780661",
                                        undefined,
                                        undefined,
                                        #Fun}},
                        c2s,
                        c2s_shaper,
                        false,
                        false,
                        false,
                        false,
                        [],
                        false,
                        undefined,
                        [],
                        "localhost",
                        [],
                        undefined,
                        {0,nil},
                        {0,nil},
                        {0,nil},
                        {0,nil},
                        undefined,
                        undefined,
                        undefined,
                        false,
                        none,
                        []}
** 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}]}

what is wrong???

If you put 'localhost' as

mfoss — Mon, 11 Jun 2007 11:50:14 +0000

If you put 'localhost' as domain on ejabberd.cfg, you can only use the Jabber server on that machine. Did you try GAIM on the same machine, or on a different one?

Are you completely sure GAIM created the account? Try to create more accounts with other clients (Gajim, Psi, Tkabber...) and check if all of them say that their accounts were correctly created.

Check ejabberd.log and sasl.log when you start ejabberd, and when you try to connect. Maybe there are error messages there.