Release Summary for 4.2.1
  Changes to 4.2 after version 4.2.0
  * [Merge pull request #3 from 2600hz/efine/use-systemd-simple  Change systemd type to &quot;simple&quot;](https://github.com/2600hz/kazoo-configs-rabbitmq/commit/b62e70cbc58189592601f792cf3769fc190d717f) by bitbashing
  * [Change systemd type to &quot;simple&quot;  Introduction ============  On CentOS, the `erlang-sd_notify` package (it&#039;s in `epel`) is used to provide communication between RabbitMQ and systemd. &quot;notify&quot; is consequently the right type to use - for CentOS.  When starting `kazoo-rabbitmq` on Debian, the &quot;notify&quot; type makes systemd block, waiting for an API notification that never comes, so it times out and kills RabbitMQ.  The quickest and easiest way to overcome this is to change the systemd service type to &quot;simple&quot;, which will work on both Debian and CentOS.  Why not just use `erlang-sd_notify` in Debian? ----------------------------------------------  It&#039;s not yet part of the official Debian distribution, although an [RFP][] was put in during early 2016 and has received little attention since then.  A Debian `.deb` package is available in a Github [repo][], but it has unfortunate dependencies and caused no end of trouble for me during installation.  Limitations -----------  A potential downside of using &quot;simple&quot; is that if RabbitMQ ever takes a long time to start up, the timeout may happen anyway, which is why `erlang-sd_notify` was created in the first place - to give status messages to systemd during startup that avoid it killing RabbitMQ prematurely.  Why not create our own build? -----------------------------  Good idea!  There is an &quot;official&quot; systemd git [repo][] for `erlang-sd_notify`, so I created a `baggage-claim` Debian build for it (surprisingly named `erlang-sd-notify`).  I did not use the upstream Debian packaging because it doesn&#039;t fit our `baggage-claim` use case very well, and, well, I don&#039;t really appreciate the way it&#039;s done.  Most annoyingly, the latest Github release is tagged as `v1.0`, which required some contortions within `baggage-claim` to keep the version with the &#039;v&#039; long enough to download the release tarball, but find a way to strip it off after that to avoid Debian build problems.  It also means that running `build.sh` requires a version of `v1 0` to work correctly (gitswitch take note).  The `erlang-sd-notify` build completes successfully, and the package installs successfully, but I have not yet tested the package functionality.  At least we have a mostly-complete Plan B if &quot;simple&quot; turns out to be, well, not so simple.  [RFP]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813634 [repo]: https://github.com/systemd/erlang-sd_notify](https://github.com/2600hz/kazoo-configs-rabbitmq/commit/9100aa0b899a8519327f6098aa917db93e6686bc) by Edwin Fine
 -- 2600Hz Official <packages@2600hz.com>  Fri, 23 Feb 2018 23:15:41 +0000
