Pivotal Knowledge Base

Follow

Loggregator trafficcontroller error message: "failed to convert log message TranslateDropsondeToLegacyLogMessage..."

Environment

Product Version
Pivotal Cloud Foundry® (PCF) 1.6.x

Symptoms

The action of running cf logs <app_name> can trigger the following error messages in the loggregator traffic controller component log files:

{"timestamp":1463676294.606717110,"process_id":3091,"source":"loggregator
trafficcontroller","log_level":"error","message":"WebsocketListener.Start:
failed to convert log message TranslateDropsondeToLegacyLogMessage:
Envelope contained HttpStartStop instead of
LogMessage","data":null,"file":"/var/vcap/data/compile/loggregator_trafficcontroller/loggregator/src/trafficcontroller/listener/websocket_listener.go","line":50,"method":"trafficcontroller/listener.(*websocketListener).listenWithTimeout"}

Another variant of the error message:

{"timestamp":1463676294.606717110,"process_id":3091,"source":"loggregator
trafficcontroller","log_level":"error","message":"WebsocketListener.Start:
failed to convert log message TranslateDropsondeToLegacyLogMessage:
Envelope contained ContainerMetric instead of
LogMessage","data":null,"file":"/var/vcap/data/compile/loggregator_trafficcontroller/loggregator/src/trafficcontroller/listener/websocket_listener.go","line":50,"method":"trafficcontroller/listener.(*websocketListener).listenWithTimeout"}

Cause

The message actually means that the endpoint detected metric message whereas it is expecting to transport only log message. Though it is listed as an error message, actually it is harmless and can be ignored. Also, application logging is not affected by this.

Resolution

Loggregator project went through some changes with logging endpoints and translation in the trafficcontroller component. This error message is in the legacy translator and it is removed from there recently as this is actually not an error message. So this message should never occur in the future PCF versions.  

If you are using a PCF 1.6.x version and see this log message in trafficcontroller log, you can safely ignore this as per above explanation.

Additional Information

Comments

Powered by Zendesk