Pivotal Knowledge Base

Follow

Error Filling in Template, "rabbitmq.config.erb' invalid base64 for rabbitmq.config"

Environment

RabbitMQ for Pivotal Cloud Foundry

Symptom

If you provide a rabbitmq.config file in the RabbitMQ configuring section and it is not base64 encoded, you will get the following error while applying changes:

Deployment name: `p-rabbitmq-1f6f456915554157e448.yml'
Director name: `microbosh-6d032da84fed11813ca4'

Director task 700
  Started preparing deployment
  Started preparing deployment > Binding deployment. Done (00:00:00)
  Started preparing deployment > Binding releases. Done (00:00:00)
  Started preparing deployment > Binding existing deployment. Done (00:00:00)
  Started preparing deployment > Binding resource pools. Done (00:00:00)
  Started preparing deployment > Binding stemcells. Done (00:00:00)
  Started preparing deployment > Binding templates. Done (00:00:00)
  Started preparing deployment > Binding properties. Done (00:00:00)
  Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
  Started preparing deployment > Binding instance networks. Done (00:00:00)
     Done preparing deployment (00:00:00)

Started preparing package compilation > Finding packages to compile. Done (00:00:00)
Started preparing dns > Binding DNS. Done (00:00:00) Started preparing configuration > Binding configuration. Failed: Error filling in template `rabbitmq.config.erb' for `rabbitmq-server-partition-null-az/0' (line 2: invalid base64) (00:00:00) Error 100: Error filling in template `rabbitmq.config.erb' for `rabbitmq-server-partition-null-az/0' (line 2: invalid base64) Task 700 error For a more detailed error report, run: bosh task 700 --debug {"type": "step_finished", "id": "bosh.deploying.p-rabbitmq-1f6f456915554157e448"} Exited with 1.

Resolution

Take the configuration and base64 and encode it. There is an online tool here that can be used www.base64encode.org or install a tool locally to do it offline.

 

Comments

  • Avatar
    Neil Watson

    Please provide an example of this in the documentation. Base64 for a config file is very odd, and in my tests this does not work.

Powered by Zendesk