Dear EJABBERD team,
I have configured ejabberd in FC6, I have done Server configuration and working fine, If i register it is succesfull and If i login to the user account am getting READ ERROR.
I have seen FAQ, but none having the problem this type, Please guys can you help me out in this peculiar type of problem.
Thanks
Sathish..!!!!
So you probably have his
So you probably have his same problem, right? .
Check ejabberd.log and sasl.log, maybe you have similar error messages.
How did you install ejabberd, using the installer, or using a package available on your Fedora distribution?
Also, can you try the example crypto:start(). mentioned on a comment on the other forum post?
Please post your answers on this thread, not on the other one.
badlop, I installed via the
badlop,
I installed via the installer. I did the crypto:start() mentioned on that post and it worked properly, with the same responses as on that forum post.
Any other ideas?! Thanks
Devin
Hi All, I had the same
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.
Good luck
-----
Aaron
Read Error
Hi,
I have uninstalled the latest version ie., ejabberd 1.1.3
and installed the old version from the archives.. it is working fine.. on this version ejabberd-1.1.2
Sathish....
I'm getting the same error
I'm getting the same error on RHEL5.
Server seems to be running fine. I can login to admin web interface. Users can register. But when users try to connect pidgin responds "Read Error". If users try to connect via the SSL port (5223) which I have enabled pidgin resonds "SSL Handshake Failed." What gives!?! Everything is working but users cannot connect.
Please help if you can.
Thanks! -Devin
Try to install ejabberd 1.1.2
I have chatted with another person that had the same problem using
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.
badlop, Thanks for the info.
badlop,
Thanks for the info. I've uninstalled 1.1.3 and installed 1.1.2 (via x86 installer) and its working now. So, this appears to be a bug in 1.1.3. AFAIK 1.1.3 should be identical to 1.1.2 aside from the mod_roster_odbc security fix so somehow a bug has snuck in. Is there somewhere I can file a bug report ?
Devin
I think it's a
I think it's a bug/problem/topic on the ejabberd 1.1.3 Linux binary installer. The 1.1.3 ejabberd source code is correct, but maybe they updated something on the building environment, and resulted in a half-incompatible installer.
Anyway, I'll report the problem and the tricky solution. Once a new build is published I'll add a comment here so some of you can try it and report if it finally works or not.
New ejabberd 1.1.1 linux installer, needs test!
There is a new version of the ejabberd 1.1.3 linux installer on the : .
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.
Fixed in 1.1.4?
Can anyone verify whether or not this bug has been fixed in the new 1.1.4 release?
Thanks.
Devin
Yes, new binary installers should work
Can anyone verify whether or not this bug has been fixed in the new 1.1.4 release?
If I remember correctly, the problem in this thread was not related to ejabberd source code: it was related to Process-one's binary installer for Linux, right?
The binary installer for the new 1.1.4 should not have the problem. If you try it and still suffer the same problem, please comment it here.
Re:
Can anyone verify whether or not this bug has been fixed in the new 1.1.4 release?
If I remember correctly, the problem in this thread was not related to ejabberd source code: it was related to Process-one's binary installer for Linux, right?
The binary installer for the new 1.1.4 should not have the problem. If you try it and still suffer the same problem, please comment it here.
The 1.1.4 installer is working for me.