[ejabberd] epam issue
holger.mickler at tu-dresden.de
Tue Feb 21 15:47:03 MSK 2012
for any file to be executed, you need to be able to read it (what would you want
-> members of the "jabber" group cannot execute the file because they are not
allowed to read its contents.
So maybe chmod g+r epam fixes your problem?
On 21.02.2012 12:07, Dennis Schridde wrote:
> Am Dienstag, 21. Februar 2012, 02:03:04 schrieb CGS:
>> Did you check the permissions/privileges to match for both? That's because
>> I noticed you used "su" + command to execute it and you didn't mention how
>> you started Ejabberd.
> I assume ejabberd is normally supposed to start epam itself? Or should I
> really start it myself, as I did for testing only?
> Anyway, these are the permissions for epam:
> -rws--x--- 1 root jabber 103288 Jan 31 17:13
> ejabberd is being started as user jabber which belongs to group jabber -
> that's what /usr/sbin/ejabberdctl says at least.
> If I read src/pam/epam.erl:init correctly, it should probably warn if it
> cannot open the file, right?
> Kind regards,
> P.S: I am now subscribed to the list.
>> On Tue, Feb 21, 2012 at 1:09 AM, Dennis Schridde <devurandom at gmx.net> wrote:
>>> Hello everyone!
>>> I am currently unable to start ejabberd, but I do not understand the
>>> It appears to be epam which cannot be started.
>>> /usr/lib/erlang/lib/ejabberd-2.1.10/priv/bin/epam exists and can be
>>> by root and by jabber via "su jabber -p -c ". It does not generate any
>>> open a network socket or any other obvious means of interaction, though.
>>> I also checked ejabberd:get_bin_path() and it points to the correct
>>> It would be nice if someone could give me a hint at what is going wrong
>>> ejabberd mailing list
>>> ejabberd at jabber.ru
More information about the ejabberd