Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54538 - [rabbitmq] rabbitmq-env.conf is badly patched when installing/upgrading the package multiple times
Attached to Project:
Arch Linux
Opened by jonathan pigrée (jonearth42) - Thursday, 22 June 2017, 09:46 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 22 June 2017, 14:13 GMT
Opened by jonathan pigrée (jonearth42) - Thursday, 22 June 2017, 09:46 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 22 June 2017, 14:13 GMT
|
DetailsDescription:
When installing/upgrading rabbitmq more than one time, the /etc/rabbitmq/rabbitmq-env.conf is badly patched. The problem comes from the line "NODENAME=rabbit" which is changed to add the @hostname. NODENAME=rabbit -> NODENAME=rabbit@hostname However, when the file is already there with the correct hostname, another installation adds again the hostname: NODENAME=rabbit@hostname -> NODENAME=rabbit@hostname@hostname This is annoying as I always have to check this file, each time I want to use rabbitmq (since rabbitmq fails to start because of this). sudo journalctl -u rabbitmq juin 22 10:08:52 arch-jp systemd[1]: Started RabbitMQ Messaging Server. juin 22 10:08:53 arch-jp rabbitmq[675]: ERROR: epmd error for host arch-jp@arch-jp@arch-jp@arch-jp: nxdomain (non-existing domain) juin 22 10:08:53 arch-jp systemd[1]: rabbitmq.service: Main process exited, code=exited, status=1/FAILURE juin 22 10:08:54 arch-jp rabbitmq[827]: Stopping and halting node 'rabbit@arch-jp@arch-jp@arch-jp@arch-jp' ... juin 22 10:08:54 arch-jp rabbitmq[827]: Error: unable to connect to node 'rabbit@arch-jp@arch-jp@arch-jp@arch-jp': nodedown juin 22 10:08:54 arch-jp rabbitmq[827]: DIAGNOSTICS juin 22 10:08:54 arch-jp rabbitmq[827]: =========== juin 22 10:08:54 arch-jp systemd[1]: rabbitmq.service: Unit entered failed state. juin 22 10:08:54 arch-jp systemd[1]: rabbitmq.service: Failed with result 'exit-code'. I already found where and how to solve this. => https://git.archlinux.org/svntogit/community.git/tree/trunk/rabbitmq.install?h=packages/rabbitmq line 7. I added the patch in attachment. Additional info: * package version(s) rabbitmq 3.6.9-2 (but I noticed the issue since more than a year) |
This task depends upon
Closed by Levente Polyak (anthraxx)
Thursday, 22 June 2017, 14:13 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#54155
Thursday, 22 June 2017, 14:13 GMT
Reason for closing: Duplicate
Additional comments about closing:
patch