I installed ejabberd-1.1.3_1 using the installer shown on the 180 second ejabberd installation presentation. My server is a Fedora 4. I'm able to register a client but they won't stay online. I followed the FAQ solution page posted by Zxinn that I pasted below (crypto server can't start). I copied the lib files to /usr/local/lib then uninstalled and reinstalled using the installer. It still isn't working(crypto not starting ) and I wonder if you have any suggestions (such as installing from source and using the Makefile).
Thanks in Advance
ESJHJ
You can try loading the file like the crypto_server does. In crypto-1.5 it's done something like this:
crypto_server:init/0 wrote:
erl_ddll:start(),
PrivDir = code:priv_dir(crypto),
LibDir1 = filename:join([PrivDir, "lib"]),
erl_ddll:load_driver(LibDir1, crypto_drv).
erl_ddll:load_driver() returns ok on success and {error,Reason} on fail. The crypto_server tries with a different path after the first fail, but has no error handling for an error during this second load and just tries to run with it regardless of the outcome.
Among the error messages printed you will get a line, "sh: exec: crypto_drv not found", or something of the like. I've seen different versions of this error message on different platforms. One reason for this, and the reason my crypto server would not start, is that the crypto_server could not load crypto_drv.so because it's not linked properly. The file should be located in your erlang lib, under crypto-/priv/lib/, or something similar.
If this file exists, it's quite possible that the path it tries to find ssl libs for dynamic loading is wrong. I had to rebuild my crypto_drv.so file from the priv/obj folder with my Makefile's SO_SSL_LIBDIR variable changed to correspond to the location of my libssl.so and libcrypto.so files. Another way to fix this could be to symlink or copy the corresponding libssl.so and libcrypto.so files to /usr/local/lib, which I think is the default path to look for them.
If you have this error and this solution fixes it, you may also have some trouble with your lib/ssl-/priv/bin/ssl_esock file's dynamic library loading. Rebuilding this file, or copying or symlinking the lib files to /usr/local/lib might solve this issue too.
/Zxinn
