Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rabbitmq-env: Check the Mnesia dir. is not shared with the PID file or the plugins expand dir. #120

Closed
dumbbell opened this issue Apr 20, 2015 · 1 comment
Assignees
Milestone

Comments

@dumbbell
Copy link
Member

If the Mnesia directory is used to store the PID file or the expaneded plugins, auto-clustering will not work. The rabbitmq-env could issue a warning about this.

@dumbbell dumbbell self-assigned this Apr 20, 2015
@dumbbell dumbbell added this to the 3.5.2 milestone Apr 20, 2015
dumbbell added a commit that referenced this issue Apr 20, 2015
If this is the case, log a warning to stderr.

Here is an example with the plugins expansion directory:
    WARNING: RABBITMQ_PLUGINS_EXPAND_DIR is located inside RABBITMQ_MNESIA_DIR
             => Auto-clustering will not work ('cluster_nodes' in rabbitmq.config)

And with the log directory:
    WARNING: RABBITMQ_LOG_BASE is equal to RABBITMQ_MNESIA_DIR
             RABBITMQ_LOGS is located inside RABBITMQ_MNESIA_DIR
             RABBITMQ_SASL_LOGS is located inside RABBITMQ_MNESIA_DIR
             => Auto-clustering will not work ('cluster_nodes' in rabbitmq.config)

Fixes #120.
@dumbbell
Copy link
Member Author

The test is expanded to all files and directories configurable in rabbitmq-env.

dcorbacho pushed a commit that referenced this issue Jul 5, 2023
Add small backoff when doing replica port scans.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant