| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
first error
|
| | |
|
| |
|
|
| |
* Basic checks
|
| |\
| |
| | |
Added erl call to make sure epmd is started
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| | |
rabbit_mirror_queue_sync: Pause the syncer process if memory is low
|
| |/
|
|
|
|
|
| |
If any node in the cluster is running out of memory, we pause the syncer
process. If we don't do this, this alarmed node could crash.
Fixes #616.
|
| |
|
|
|
| |
Alarms are emitted for 'disk' or 'memory' resources shortage, not
'node'.
|
| |
|
|
|
|
|
|
| |
RabbitMQ recreates it anyway so we can't pass it the escaped directory
name. Therefore, this directory must not contain any non-US-ASCII in its
name.
References #493.
|
| |\
| |
| | |
Fix action_stop for the rabbit OCF
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
The action_stop may sometimes stop the rabbitmq-server gracefully
by the PID, but leave unresponsive beam.smp processes running and
spoiling rabbits. Those shall be stopped as well. The solution is:
- make proc_stop() to accept a pid=none to use a name matching instead
- make kill_rmq_and_remove_pid() to stop by the beam process matching as well
- fix stop_server_process() to ensure there is no beam process left running
Related Fuel bug: https://launchpad.net/bugs/1541029
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
|
| |\
| |
| | |
Add emitting node info to amq.rabbitmq.log messages
|
| |/
|
|
| |
Fixes #595.
|
| |\
| |
| | |
Streamline checking for cluster partitioning
|
| |/
|
|
|
| |
Move check if we are current cluster master to earlier place in code.
That way we will avoid unnecessary operations for master case.
|
| |\
| |
| | |
Fix cluster membership check for running master
|
| | |
| |
| |
| | |
The running master is always inside of its own cluster.
Fix the cluster membership check when a node is the master.
|
| |\ \
| |/
| | |
Fix uninitialized status_master
|
| |/
|
|
|
|
|
|
| |
Fix multiple nodes may be reported in logs as the running master
Related Fuel bug https://bugs.launchpad.net/bugs/1540936
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
|
| |\
| |
| | |
Suppress curl progress indicator in rabbit OCF
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
curl is used by OCF script for fetching definitions (queues etc.), but
results of that invocation is shown as garbage in pacemaker logs -
progress indicator doesn't make any sense in logs.
According to curl manpage the following combination of options should be
used "--silent --show-error" - this will suppress only progress
indicator, errors will still be shown.
Also other short curl options are replaced with their long counterparts
- for improved readability.
|
| |\
| |
| | |
Use -r with sed on Linux
|
| |/
|
|
|
|
|
|
| |
We previously did the same change in #273 (PR: #275),
but the file in which it was done was removed in 231e90cacf3daec5f43b3307867129e61496b123.
Note that #592 recommends using `-r` unconditionally but that option
is not recognised by sed which ships with OS X.
|
| |\
| |
| |
| |
| |
| |
| |
| | |
This is only a part of what #541 is supposed to cover but
it already helped in a particular node shutdown lockup we've
observed => worth merging earlier.
Per discussion with @dcorbacho.
|
| | |\ |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
Specify hash algorithm in change_password_hash
|
| | | | |
|
| |/ / |
|
| |\ \
| |/
|/| |
Unblock receive after 15s
|
| | | |
|
| | |
| |
| |
| | |
This silences a warning logged during RabbitMQ startup.
|
| |\ \
| | |
| | | |
Ignore duplicate down_from_ch
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the directory or file does not exist before RabbitMQ starts, we can't let
RabbitMQ create it, otherwise, it's created with its short filename, not its
long one.
With this new correction, we can "escape" all variables instead of only
RABBITMQ_BASE.
Fixes #493.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that at the time of this commit, Lager does not support logging
to stdout on Windows. This commit still improves consistency between
Unix and Windows.
References #493.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Compared to the script's parent directory (stored in TDP0),
RABBITMQ_HOME is converted to a short filename to avoid non-ASCII in the
path.
Fixes #493.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Windows, cmd.exe and batch scripts do not support Uniode apparently.
However, Windows uses UTF-16 to encode filenames one disk. In batch
scripts, filenames are converted to some one-byte-wide charset. Once
passed to Erlang and RabbitMQ, those filenames are incorrect. In
particular, the management UI is unhappy because filenames obviously
contain invalid UTF-8 characters.
Using short filenames makes sure filename only contain US-ASCII
characters.
To convert them, we use "for" expansion. At the same time, filenames are
made absolute. It works even better than realpath.exe because the latter
also converts filenames to another charset again.
Fixe #493.
|
| |\ \
| | |
| | | |
Use systemd-notify(1) shell helper as fallback
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently external erlang library `sd_notify` is used to make systemd
unit with `Type=notify` to work correctly. This library contains some C
code and thus cannot be built into architecture-independent package.
But it is not actually needed, as systemd provides systemd-notify(1)
helper for shell scripts which serves exactly the same purpose.
The only thing is that you need to add `NotifyAccess=all` to your unit
file to make everything work well.
|
| |\ \
| | |
| | | |
Fix usage of uninitialized variable in OCF script
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
binarin/rabbitmq-server-ocf-list-channels-diagnostics
Improve OCF script diagnostics for timed-out 'list_channels'
|
| | | |
| | |
| | | |
timeout(1) manpage mentions 124 as another valid return code from, in addition to 128 + signal-number.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently time-out when running 'rabbitmqctl list_channels' is treated
as a sign that current node is unhealthy. But it could not be the
case, as the hanging channel could be actually on some other
node. Given that currently we have more than one bug related to
'list_channels', it makes sense to improve diagnostics here.
This patch doesn't change any behaviour, only improves logging after
time-out happens. If time-outs continue to occur (even with latest
rabbitmq versions or with backported fixes), we could switch to this
improved list_channels and kill rabbitmq only if stuck channels are
located on current node. But I hope that all related rabbitmq bugs
were already closed.
|