[Bug 1337216] New: p1_pam fails to start - ejabberd barfs

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1337216

            Bug ID: 1337216
           Summary: p1_pam fails to start - ejabberd barfs
           Product: Fedora
           Version: rawhide
         Component: ejabberd
          Severity: high
          Assignee: lemenkov(a)gmail.com
          Reporter: alan.milligan(a)last-bastion.net
        QA Contact: extras-qa(a)fedoraproject.org
                CC: erlang(a)lists.fedoraproject.org, jeremy(a)jcline.org,
                    lemenkov(a)gmail.com, martin(a)laptop.org,
                    rbarlow(a)redhat.com



Description of problem:
p1_pam fails to start because ejabberd is looking in the incorrect place for
epam.beam (in ejabberd file path instead of p1_pam) - sorry haven't looked at
code to provide patch


Version-Release number of selected component (if applicable):
Rawhide 16.04


How reproducible:
Always

Steps to Reproduce:
1. Ensure PAM turned on in ejabberd.yml
2. start ejabberd
3. it fails: check /var/log/ejabberd/server.log

Actual results:
/var/log/ejabberd/server.log
2016-05-18 23:40:47.128 [info] <0.38.0>@cyrsasl_digest:start:60 FQDN used to
check DIGEST-MD5 SASL authentication: jenkins-dev.last-bastion.net
2016-05-18 23:40:47.154 [error] <0.392.0> Can't open file
"/usr/lib64/erlang/lib/ejabberd/priv/bin/epam": enoent
2016-05-18 23:40:47.154 [error] <0.392.0> CRASH REPORT Process epam with 0
neighbours exited with reason: bad return value: error in gen_server:init_it/6
line 356
2016-05-18 23:40:47.154 [error] <0.391.0> Supervisor epam_sup had child epam
started with epam:start_link() at undefined exit with reason bad return value:
error in context start_error
2016-05-18 23:40:47.154 [error] <0.389.0> CRASH REPORT Process <0.389.0> with
0
neighbours exited with reason:
{{shutdown,{failed_to_start_child,epam,{bad_return_value,error}}},{epam_app,start,[normal,[]]}}
in application_master:init/4 line 134
2016-05-18 23:40:47.154 [critical] <0.38.0>@ejabberd:exit_or_halt:133 failed to
start application 'p1_pam': {error,
                                       {{shutdown,
                                         {failed_to_start_child,epam,
                                          {bad_return_value,error}}},
                                        {epam_app,start,[normal,[]]}}}
2016-05-18 23:40:47.155 [info] <0.7.0> Application p1_pam exited with reason:
{{shutdown,{failed_to_start_child,epam,{bad_return_value,error}}},{epam_app,start,[normal,[]]}}

Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.