RabbitMQ is a complete and highly reliable Enterprise Messaging
system. The RabbitMQ client libraries and broker daemon can be used
together to create an AMQP network, or used individually to bring
the benefits of RabbitMQ to established networks.
In preparation for upgrading to future RabbitMQ releases, users *must*
enable all feature flags before upgrading to v4.0.4, and subsequently,
enable all feature flags *again* directly after upgrading.
See https://www.rabbitmq.com/docs/upgrade for details.
For install:
First-time users will want to run:
sudo -u rabbitmq rabbitmq-plugins enable rabbitmq_management
sudo -u rabbitmq rabbitmqctl enable_feature_flag --experimental khepri_db
and restart, to enable the web admin console at http://localhost:15672/
with a default username and password of guest:guest. You should change it..
See https://www.rabbitmq.com/docs for install help, and
https://www.rabbitmq.com/docs/configure for further options.
Reason:
In preparation for upgrading to future RabbitMQ releases, users *must*
enable all feature flags before upgrading stepwise to v3.12.13, to be
able to migrate later to v3.13.0 when it is released in 2024Q2.
See https://www.rabbitmq.com/docs/upgrade for details.
Number of commits found: 167 (showing only 100 on this page) #
*/*: Use C.UTF-8 locale
Ports 02f27a83b44d fixed the ports tree to the C locale so it would work
correctly in environments where users use a locale that isn't compatible
with the C locale, e.g. xx_YY.UTF-8 where [A-Z] includes more than just
upper case letters. USE_LOCALE was introduced to let ports use another
locale if they needed it. The C.UTF-8 locale was created later on to be
mostly compatible with the C locale.
Switch the ports tree locale to C.UTF-8 and remove USE_LOCALE. The
world has moved to Unicode so all ports either require it or know how to
build correctly in a Unicode environment.
PR: 295945
Exp-run by: antoine
net/rabbitmq: Update 3.13.6 → 3.13.7
This upgrade is highly recommended to all users currently on earlier
3.13.x series and in particular between 3.13.3 and 3.13.5, inclusive.
Changelog:
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.13.7
PR: 281094
Approved by: erlang (maintainer, timeout > 14 days)
MFH: 2024Q3
net/rabbitmq: update to v3.12.13 and new tarball
Summary:
RabbitMQ has long provided a generic unix tarball which is better
suited for a FreeBSD port. There should be no functional changes
for this approach, and it simplifies build and release by aligning
better with upstream deployment, removing dependency on lang/elixir
releases.
Once the 2024Q2 branch is created, the next RabbitMQ release will
be updated, as users need to migrate from 3.11 -> 3.12 -> 3.13
without skipping in between versions.
https://rabbitmq.com/install-generic-unix.html
Differential Revision: https://reviews.freebsd.org/D43954
PR: 275838
net/rabbitmq: Fix `rabbitmq` rc.d script to use `%%_ERLANG_LIB%%`
[Why]
In commit c9033971719dc098b34276f11b8e5a5e22b966fd, the variable was
renamed from `ERLANG_LIB` to `_ERLANG_LIB`. However the rc.d script was
not updated to reflect that change.
Therefore the script didn't use the expected version of Erlang. This
meant that it could use `lang/erlang` if it was installed (which could
be incompatible) or not start at all.
[How]
The rc.d script is simply updated to use the new variable name. The port
revision is bumped to note the change.
PR: 271269
Reported by: Miroslav Lachman <000.fbsd@quip.cz>
net/rabbitmq: rc.d improvements
This commit creates a separate directory at /var/run/rabbitmq to
host the RabbitMQ pid file. Previously, the pid file was not being
created properly (it was empty) and this was causing issues with
the process of waiting for pids (as the pid file existed, but had
no value and was considered "garbage"). With this change the pid
file is created with the correct value, enabling the process of
waiting for pids to complete successfully; now the startup script
returns exit code 0.
Additionally, this commit exports the variables RABBITMQ_HOME,
RABBITMQ_LOG_BASE, and RABBITMQ_PID_FILE so that the RabbitMQ process
can properly locate the pid file.
These changes resolve PR 264062.
PR: 264062
Reported by: FiLiS <freebsdbugs@filis.org>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net/rabbitmq: add new /sbin/ tools for migrations
- add upgrade helper scripts
- cuttlefish is needed for handling some config settings
- pet port order while here
Reviewed by: olgeni
Sponsored by: SkunkWerks, GmbH
Differential Revision: https://reviews.freebsd.org/D22310
net/rabbitmq: Import patch to make it compatible with Elixir 1.9.0
To be exact, they are two patches:
- one to mark rabbitmq_cli compatible with Elixir 1.9.x
- one to make mix(1) work offline (without accessto Hex.pm) again
Reported by: olgeni@
Reviewed by: olgeni@, dch@
Differential Revision: https://reviews.freebsd.org/D20781
Update net/rabbitmq to version 3.7.15.
- Fix manpage paths.
- Move the installed code away from the default ERL_LIBS as it has no
purpose there and could lead to conflicts.
Differential Revision: https://reviews.freebsd.org/D19913
Force using erlang-runtime19 for net/rabbitmq: the current version is NOT
COMPATIBLE with Erlang 20 and can lead to data corruption during upgrades.
The proper solution would be to build a release with a bundled runtime, but
this will have to do for now.
net/rabbitmq: add full path to the daemon(8) call in rc script.
This allows the script to work in crontab, where /usr/sbin is not
in PATH.
Submitted by: Dmitriy Simakov
MFH: 2017Q1
multimedia ... sysutils: Remove redundant dependency on unzip
A dependency on unzip will never be registered since unzip is available
on all supported platforms (since FreeBSD 8.0).
Note that it's pulled in by a non-default option.
Approved by: infrastructure blanket (removal of redundant deps)
Update net/rabbitmq to version 3.6.1.
From the release notes:
This release fixes a number of bugs in 3.6.0 and earlier versions,
as well as one security issue (CVE-2015-8786) in the management
plugin. It also contains usability improvements.
CVE 2015-8786 has not been publicly announced yet.
Security: CVE-2015-8786
Remove custom stderr formatting from net/rabbitmq.
From upstream commit fecd0e5 in rabbitmq/rabbitmq-common:
Opening several ports for single fd is considered undefined behaviour
in erlang. It's safe to replace this whole function with 'io:format'.
Because writing to standard_error with io:format is synchronous - after
this call has returned data was definitely sent to the port. And
`erlang:halt` guarantees that this data will be flushed afterwards.
See also ba531a1 in erlang/otp:
Instead of outputting a formatted message showing errors found, a core
was (often) created.
(Only the first 15 lines of the commit message are shown above )
Avoid calling "rabbitmqctl status" in a loop to make sure that RabbitMQ is
started.
"rabbitmqctl wait" alone should suffice, and the loop seems to cause some
kind of race condition that causes a segfault in the Erlang VM.
RabbitMQ would start anyway, but users would get a segmentation fault
message on the console.
We also wait on daemon(8)'s pid to make sure that restarts are synchronized
(i.e. daemon(8) is stopped before starting it again with the same pidfile).
PR: 204147
Submitted by: elofu17@hotmail.com
Switch default python_CMD used by shebangfix to ${PYTHON_CMD} for ports
using python
PR: 201077
Reviewed by: mat
With hat: portmgr
Differential Revision: https://reviews.freebsd.org/D2955
Upgrade to version 3.5.4.
- Make sure that all content of /var/db/rabbitmq is owned by rabbitmq
at startup.
- Only set HOME when actually starting the rabbitmq process.