doppler issue which fails to emit logs with syslog protocol on CFv212

Masumi Ito

Hi, I am investigating the doppler issue on CFv212 that sending logs to the
external logging service with syslog protocol fails.

As my understanding, the following messages are supposed to be recorded in
the "doppler.stdout.log" if the doppler got the syslog drain url from etcd
However it is actually missing.

- Missing log messages which is expected to be shown
Sink syslog://xx.xx.xx.xx:xxxx:
Sink syslog://xxxxxx:xxxxxx: successfully

Instead, there are a lot of etcd error events found as follows.

Got error while waiting for ETCD events: store request timed

I have two question about this.

Q1) Does anyone know what this event indicates and how it affects the CF
In the normal envrionment, is this event still triggered (In other
words, can we ignore this error event messages?)

Q2) If the etcd got some trouble at the moment, which cf component is also
made an influence on?

I guess at the least the following cf components could be affected. Do we
have anyting else?
- router : to support routing api
- hm9000 : to support health check
- doppler: to get syslog drain urls from etcd
- syslog-binder to get syslog drain urls from cc and then store them to
- trafficcontroller, metron agents : to find healthy dopplers to access

Note that I am also doubting the following errors in the
This message indicates that syslog_drain_binder failed to get syslog drain
urls from cc.
when polling cloud controller: Remote server error:

Therefore I have not yet concluded the etcd mainly caused the issue, however
need to understand the exact meaning of the error event message above as
well as any impact on the cf envrionment if there is something wrong with
the behaviour of etcd.


View this message in context:
Sent from the CF Dev mailing list archive at

Join to automatically receive all group messages.