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.

Sign up for GitHub

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

Jump to bottom

applying configuration failed #25

Open
Dieterbe opened this issue Jul 6, 2015 · 2 comments
Open

applying configuration failed #25

Dieterbe opened this issue Jul 6, 2015 · 2 comments

Comments

@Dieterbe
Copy link
Contributor

Dieterbe commented Jul 6, 2015

just saw this during ./build_all.sh

Applying plugin configuration to rabbit@7b090dbfcf59... failed.
 * Could not contact node rabbit@7b090dbfcf59.
   Changes will take effect at broker restart.
 * Options: --online  - fail if broker cannot be contacted.
            --offline - do not try to contact broker.

is this harmless?
@woodsaj
Copy link
Contributor

woodsaj commented Jul 7, 2015

Yes this is expected and harmless. During the build we run rabbitmqctl to enable the mgmt plugin. This will enable the plugin in the config and also try to contact the running rabbit (which doesnt exist) to notify it of the change.

When the image is started the mgmt plugin will be enabled because it is enabled in the config.

@woodsaj woodsaj closed this as completed Jul 7, 2015
@woodsaj woodsaj reopened this Jul 7, 2015
@woodsaj
Copy link
Contributor

woodsaj commented Jul 7, 2015

Actually we should just pass the --offline option so rabbitmqctl doesnt try and contact the broker (rabbit server)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Dieterbe @woodsaj