(This is not the other bug where it could be solved with a softlink.) When starting ejabberd, I get the following error: <0.361.0> Can't open file "/usr/lib/erlang/lib/ejabberd/ejabberd-16.01/priv/bin/epam": enoent But here, the only epam binary to be found, resides in: /usr/lib/erlang/lib/ejabberd/p1_pam-1.0.0/priv/bin/epam So no surprise ejabberd can’t find it. I don’t know how to progress, or what’s the right way to fix this. Otherwise I would have added the solution here.
Workaround would be to copy this epam file and set permissions as documented in here: https://docs.ejabberd.im/admin/guide/configuration/#pam-authentication It looks like p1_pam needs to be treated differently: instead of installing it in p1_pam/priv it should be installed in ejabberd/priv and have set correct permissions. But what in case if p1_pam is a separate dependency? Would it be still OK to copy epam from an already installed package?
(In reply to Amadeusz Żołnowski from comment #1) > But what in case if p1_pam is a separate dependency? > Would it be still OK to copy epam from an already installed package? This is long ago. I have no clue anymore. That whole Erlang setup is rather confusing and weird to me. I’d just like it to start as expected after the next update… So no idea what to say here, in case you asked me that question.
(In reply to Navid Zamani from comment #2) > This is long ago. I have no clue anymore. That whole Erlang setup is rather > confusing and weird to me. I’d just like it to start as expected after the > next update… So no idea what to say here, in case you asked me that question. This question is rather directed to other devs which are on CC. I am working on debundling ejabberd (it's 30 packages) and I hope new ebuild will come with fixes for most of reported bugs.
It should be fixed in 16.04. It works for me. Please reopen if issue still persists.
