| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
As we are mapping over queues in search of their consumers, actual
result for every queue could be zero or more consumers. We need to take
that into account while printing.
Closes #701
|
| |\
| |
| | |
Increase IO async to 64 for windows
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Rabbit ocf ra travis
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Add a CI job which triggers only if there are changes
to the scripts/rabbitmq-server-ha.ocf
* Add a script to setup a cluster by the pacemaker OCF RA
and issue a simple smoke test for the cluster membership.
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
|
| |\ \ \
| | | |
| | | | |
Fix logrotate / systemd incompatibility
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
On systemd-enabled hosts `/sbin/service` just proxies commands to
`systemctl`, which doesn't understand funny commands like
`rotate-logs`. So `rabbitmqctl rotate_logs` is a better alternative.
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | |
| | | |
This slightly improves rabbitmq/rabbitmq-server#584
Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Erlang does not support kernel polling on Windows: there is no need to
confuse users about this.
Fixes #695.
|
| |\ \
| | |
| | | |
"rabbitmqctl stop" exits with 0 if it fails to contact the node
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If rabbitmqctl fails to contact the node to ask it to stop, it still
displays an error message. However, now it exits with 0; it was
EX_UNAVAILABLE before.
There are two main reasons it can happen:
o The node is stopped, so that's ok to exit with 0 because the end
result is the same.
o The Erlang cookie is incorrect. The error message is here to help
but this situation is quite rare compared to the other one.
There is no way to distinguish both, so let's assume the common
situation.
This helps in the case of systemd in particular: if one stops RabbitMQ
using "rabbitmqctl stop" instead of "service rabbitmq-server stop",
systemd tries to call "rabbitmqctl stop" again. Before this change, it
failed and put the service in a "failed" state.
Fixes #693.
|
| |\ \
| |/
|/| |
Systemd improvements
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Before that it happened implicitly due to the death of the controlling
process. But it's better to make it explicit.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hopefully this patch will fix all systemd-related problems:
- Proxy shell process (which converts signals to `rabbitmqtl stop`) will
no longer be started under systemd. There is no need in it, as systemd
unit already contains instructions for graceful shutdown.
- Ready notification for systemd will be sent with the help of `socat`,
as `systemd-notify` is currently broken for non-root users. `socat` is
the most lightweight way to do it (other options are using NIF or some
external helper in Perl).
- epmd will not be able to interfere by sending it's own ready
notifications.
- systemd journal will contain some additional messages about startup
and shutdown sequence, just to be sure that everything is working
correctly.
Fixes #664
|
| |\ \
| |/
|/| |
Revert "Private attributes usage in rabbitmq script"
|
| |/
|
|
|
|
| |
This reverts commit 4aeaa79bc566c81bc7f5c20d7afbe39c32771aba.
Related Fuel bug https://bugs.launchpad.net/fuel/+bug/1556123
|
| |\
| |
| | |
Verify that mandatory environment variables are (pre)set
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Disable erlang break handler in rabbitmqctl
|
| |/ /
| |
| |
| |
| | |
So rabbitmq operator will not be baffled by erlang break handler when he
tries to interrupt some long-running `rabbitmqctl` command by `Ctrl-C`.
|
| |\ \
| | |
| | | |
Create rabbitmq.config on windows installation
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
[OCF HA] Log process id in RabbitMQ OCF script
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Several OCF calls might run simultaneously. For example, it often
happens that two monitor calls intersect. Logging current process id
for each line helps distinguish logs of different calls.
Also aligned get_status() logging with format used in all other
parts of the script.
|
| |\ \ \ \
| |_|_|/
|/| | | |
Avoid hipe compile versioned modules
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Move auth_backend and types modules to rabbitmq-common.
|
| |/ / / /
| | | |
| | | |
| | | | |
* Delete these modules from rabbitmq-server and add them to rabbitmq-common.
|
| |\ \ \ \
| | | | |
| | | | | |
Restart option for windows service.
|
| | | | | | |
|
| |\ \ \ \ \ |
|