Assuming you haven't done

meroveus — Sat, 04 Oct 2008 23:40:15 +0000

Assuming you haven't done something foolish like having another version of erlang along with the one supplies in the binary, it is likely that selinux is preventing access to the lib.

Look in your /var/log/audit/audit.log file and if you see an entry like:
type=AVC msg=audit(1223133076.770:102): avc: denied { execmod } for pid=3878 comm="beam.smp" path="/opt/ejabberd-2.0.2_2/lib/crypto-1.5.2/priv/linux-x86/lib/crypto_drv.so" dev=dm-0 ino=26738869 scontext=user_u:system_r:unconfined_t:s0 tcontext=user_u:object_r:usr_t:s0 tclass=file
then you've found the culprit.

The easy solutions to this violation are:
a) run selinux in permissive mode
b) set the boolean variable allow_execmem by doing: setsebool -P allow_execmod=1

Erlang is included in binary installer.

mfoss — Tue, 30 Sep 2008 17:21:22 +0000

Quote:

I install ejabberd-2.0.2_2 on Red Hat Enterprise Linux Server release 5.2 (Tikanga)
and I build Erlang R11... before that.

If you install ejabberd using the binary installer from ProcessOne website, you don't need to install Erlang/OTP, because it is already included.

** Reason for termination =
** {badarg,[{erlang,port_control,
[crypto_drv02,1,"test1char:sometesthost.com:test1"]},
{crypto,control,2},

I don't know what exactly happened, it's something related to the 'crypto' erlang library included in Erlang.

ejabberd - Comments for "ejabberd-2.0.2_2 on Red Hat "

Assuming you haven't done

Erlang is included in binary installer.