[Bug 1808766] Re: fails to start

2019-01-03 Thread Bug Watch Updater
** Changed in: erlang (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Title: fails to start To manage notifications about this bug go to: https

[Bug 1808766] Re: fails to start

2019-01-02 Thread Jeremy Bicha
** Bug watch added: Debian Bug tracker #911927 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911927 ** Also affects: erlang (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911927 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1808766] Re: fails to start

2018-12-21 Thread Launchpad Bug Tracker
This bug was fixed in the package rabbitmq-server - 3.7.8-4ubuntu2 --- rabbitmq-server (3.7.8-4ubuntu2) disco; urgency=medium * Resolve issues with startup of RabbitMQ with erlang provided epmd daemon (LP: #1808766): - d/rabbitmq-server.service: Wants/After epmd.socket, alig

[Bug 1808766] Re: fails to start

2018-12-18 Thread Launchpad Bug Tracker
This bug was fixed in the package erlang - 1:21.2+dfsg-1ubuntu1 --- erlang (1:21.2+dfsg-1ubuntu1) disco; urgency=medium * d/epmd.socket: Enable socket for all interfaces, resolving issues with startup of RabbitMQ and other clusters erlang services (LP: #1808766). -- James

[Bug 1808766] Re: fails to start

2018-12-17 Thread Christian Ehrhardt 
After validating the different options (sorry for my interim confusion) I think for now the least-invasive solution is the second suggested change. The other options are not as-good IMHO: - the first adds a lot of Delta to many packages - the third would make a package require user interaction to

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
OR rabbitmq-server installs without enabling and starting its daemon; requiring the user to reconfigure epmd (or disable it completely). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Title:

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
Alternatively we could drop the BindToDevice=lo Stanza in the @'less socket unit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Title: fails to start To manage notifications about this bug

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
List of potentially impacted packages: * averell * ejabberd * ejabberd-contrib * ejabberd-mod-cron * ejabberd-mod-log-chat * ejabberd-mod-logsession * ejabberd-mod-logxml * ejabberd-mod-message-log * ejabberd-mod-muc-log-http * ejabberd-mod-post-log * ejabberd-mod-pottymouth * ejabberd-mod-rest *

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
Proposal to resolve this issue (as I quite like the way RabbitMQ uses @'ed units). Ship @'less and @'ed epmd.{socket|service} units in the erlang packages, all installed by disable by default. So epmd does not get started by default; only when another erlang application expresses and interest in

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
Raising erlang task as well because we might want to fix things there rather than rmq. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Title: fails to start To manage notifications about this

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
RabbitMQ includes: After=network.target epmd@0.0.0.0.socket Wants=network.target epmd@0.0.0.0.socket in its systemd unit file; however the @ notation on the epmd socket is not compatible with the erlang packaging in Ubuntu and Debian (which only ships @'less versions). ** Also affects: erlang (

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
Other distro references: https://bugzilla.suse.com/show_bug.cgi?id=1003085 ** Bug watch added: bugzilla.suse.com/ #1003085 https://bugzilla.suse.com/show_bug.cgi?id=1003085 ** Bug watch added: Red Hat Bugzilla #1104843 https://bugzilla.redhat.com/show_bug.cgi?id=1104843 -- You received t

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
And https://bugzilla.redhat.com/show_bug.cgi?id=1104843 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Title: fails to start To manage notifications about this bug go to: https://bugs.launc

[Bug 1808766] Re: fails to start

2018-12-17 Thread James Page
I think this is due to the erlang-base package now enabling a shared epmd daemon by default; rabbitmq-server is unable to connect to it over the hostname of the server as it only listens on localhost by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1808766] Re: fails to start

2018-12-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rabbitmq-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Tit

[Bug 1808766] Re: fails to start

2018-12-17 Thread Christian Ehrhardt 
I can't apport to this bug (damn != reporter restriction) so I filed a duplicate to have the crash data. See bug 1808774 for crash files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808766 Title:

[Bug 1808766] Re: fails to start

2018-12-17 Thread Christian Ehrhardt 
It fails to start on install on both, although it fails differently. The logs (journald) didn't have too much info other than failing, but when I ignore the service and run the binary I get: x86: /usr/sbin/rabbitmq-server ERROR: epmd error for host d: address (cannot connect to host/port) s390x: