Community Packages

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!
Tasklist

FS#54155 - [rabbitmq] Upgrade or reinstall breaks rabbitmq-env.conf

Attached to Project: Community Packages
Opened by Jon Bergli Heier (snakebite) - Monday, 22 May 2017, 09:44 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 22 June 2017, 14:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
When upgrading or reinstalling the rabbitmq package, the current hostname is appended to the HOSTNAME variable in rabbitmq-env.conf. If HOSTNAME is set to rabbit@host, after reinstall it will be set to rabbit@host@host, which will then cause the service to fail to start. This has to be manually fixed by editing rabbitmq-env.conf after each upgrade.

Additional info:
* rabbitmq 3.6.9-2

Steps to reproduce:
* Upgrade or reinstall the rabbitmq package.
This task depends upon

Closed by  Levente Polyak (anthraxx)
Thursday, 22 June 2017, 14:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.6.10-1
Comment by Platon Pronko (Rogach) - Thursday, 08 June 2017, 10:05 GMT
Possible fix: in rabbitmq.install, replace

sed -e "/NODENAME/s/rabbit/rabbit@$(hostname -s)/" -i /etc/rabbitmq/rabbitmq-env.conf

with

sed -e "/NODENAME/s/rabbit$/rabbit@$(hostname -s)/" -i /etc/rabbitmq/rabbitmq-env.conf

Loading...