[Bug 1315047] New: Incorrect ExecStop= directive in ejabberd.service

[Red Hat Bugzilla]

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

            Bug ID: 1315047
           Summary: Incorrect ExecStop= directive in ejabberd.service
           Product: Fedora
           Version: 22
         Component: ejabberd
          Assignee: lemenkov(a)gmail.com
          Reporter: rbarlow(a)redhat.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: arcfi(a)aetera.net, erlang(a)lists.fedoraproject.org,
                    extras-qa(a)fedoraproject.org, jeremy(a)jcline.org,
                    lemenkov(a)gmail.com, martin(a)laptop.org,
                    rbarlow(a)redhat.com
        Depends On: 1314753
            Blocks: 1315046



+++ This bug was initially created as a clone of Bug #1314753 +++

Description of problem:
Incorrect ExecStop= directive in ejabberd.service resulting in unit stop
failing.
The correct directive is:
ExecStop=/usr/bin/bash /usr/bin/ejabberdctl stop

Version-Release number of selected component (if applicable):
ejabberd-14.07-6.fc22.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. systemctl stop ejabberd.service
2. systemctl status ejabberd.service

Actual results:
systemd[1]: Stopping A distributed, fault-tolerant Jabber/XMPP server...
ejabberdctl[3067]: Refusing to render service to dead parents.
systemd[1]: ejabberd.service: Control process exited, code=exited status=127
systemd[1]: Stopped A distributed, fault-tolerant Jabber/XMPP server.
systemd[1]: ejabberd.service: Unit entered failed state.
systemd[1]: ejabberd.service: Failed with result 'exit-code'.

Expected results:
# grep ExecStop= /usr/lib/systemd/system/ejabberd.service 
ExecStop=/usr/bin/bash /usr/bin/ejabberdctl stop

--- Additional comment from Randy Barlow on 2016-03-06 01:48:08 EST ---

This is easy to fix in Fedora 24, but unfortunately the SRPM does not build
anymore on F22 or F23 with this build error:

Compiling
/builddir/build/BUILD/ejabberd-14.07/deps/jiffy/c_src/double-conversion/bignum.cc
/builddir/build/BUILD/ejabberd-14.07/deps/jiffy/c_src/double-conversion/bignum.cc:
In member function 'void
double_conversion::Bignum::AssignDecimalString(double_conversion::Vector<const
char>)':
/builddir/build/BUILD/ejabberd-14.07/deps/jiffy/c_src/double-conversion/bignum.cc:101:6:
error: assuming signed overflow does not occur when assuming that (X + c) < X
is always false [-Werror=strict-overflow]
 void Bignum::AssignDecimalString(Vector<const char> value) {
      ^
cc1plus: all warnings being treated as errors

I will have an F24 fix out shortly, but I don't have time to investigate these
build failures this weekend.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1314753
[Bug 1314753] Incorrect ExecStop= directive in ejabberd.service
https://bugzilla.redhat.com/show_bug.cgi?id=1315046
[Bug 1315046] Incorrect ExecStop= directive in ejabberd.service
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1315047] Incorrect ExecStop= directive in ejabberd.service

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1315047
Bug 1315047 depends on bug 1314753, which changed state.

Bug 1314753 Summary: Incorrect ExecStop= directive in ejabberd.service
https://bugzilla.redhat.com/show_bug.cgi?id=1314753

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|---                         |RAWHIDE



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

[Bug 1315047] Incorrect ExecStop= directive in ejabberd.service

[Red Hat Bugzilla]

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

Peter Lemenkov <lemenkov(a)gmail.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |EOL
        Last Closed|                            |2016-06-06 09:56:39



--- Comment #1 from Peter Lemenkov <lemenkov(a)gmail.com&gt; ---
I don't think we're going to fix anything in F22. If anyone is affected by this
change then please upgrade at least to Fedora 24 which is very much supported.

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