RabbitMQ for PCF does not emit metrics after upgrade to 1.13 and 1.14
search cancel

RabbitMQ for PCF does not emit metrics after upgrade to 1.13 and 1.14

book

Article ID: 293200

calendar_today

Updated On:

Products

VMware RabbitMQ

Issue/Introduction

Symptoms:
After upgrading to version 1.13, RabbitMQ stops emitting metrics. This affects both the pre-provisioned and the on-demand instances.

Environment


Cause

There is a missing name in the Certificate required for the mutual TLS with Loggregator. We can verify if this issue is the root cause by SSH'ing into a RabbitMQ instance and checking the fileĀ /var/vcap/sys/log/service-metrics/service-metrics.log and look for an error like this:
{"timestamp":"1543852918.753087044","source":"service-metrics","message":"service-metrics.Error while flushing: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: authentication handshake failed: x509: certificate is valid for metron_tls_cert, not metron\"","log_level":1,"data":{}}

Resolution

This is a known bug and it is resolved in tile versions 1.13.12, 1.14.5 and 1.15. There is no workaround and the recommended solution is to upgrade.