Error dialing loggregator server: unexpected EOF


ramonskie
 

i just created a new cloudfoundry deployment for testing purposes
and i can push a application but the the following error

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint is wss://loggregator.cf.dev.eden.klm.com:4443).

cf logs trace http://pastebin.com/KkpAJ8x0

doppler/loggeragor logs http://pastebin.com/c8giCvua

deployment manifest http://pastebin.com/XQMfWqDJ

can maby someone point me in the right direction?
i think im missing something


Rohit Kumar
 

Hi Ramon,

Can you confirm if your installation has the 4443 port open for
loggregator? One quick way of finding out would be to issue a curl to the
traffic controller. Can you run the following command and tell us what you
see?

curl -kv https://loggregator.cf.dev.eden.klm.com:4443

If you can reach the traffic controller, you will get a 404 response.

Rohit

On Fri, Feb 12, 2016 at 4:24 AM, Ramon Makkelie <ramon.makkelie(a)klm.com>
wrote:

i just created a new cloudfoundry deployment for testing purposes
and i can push a application but the the following error

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform configuration
(loggregator endpoint is wss://loggregator.cf.dev.eden.klm.com:4443).

cf logs trace http://pastebin.com/KkpAJ8x0

doppler/loggeragor logs http://pastebin.com/c8giCvua

deployment manifest http://pastebin.com/XQMfWqDJ

can maby someone point me in the right direction?
i think im missing something


Felix Friedrich
 

Hello Ramon,

I think I remember having seen this message when we used an Local
Traffic Manager (F5) as the entrypoint. I could not figure out the root
cause, but there obviously went something wrong with the websocket
connection which is used to fetch the logs. If you also use another
entrypoint than ha_proxy, you could use ha_proxy for these kind of
websocket connections by adding a DNS entry for
{loggregator,doppler}.your.cf.installation.com which point to ha_proxy
rather than the entrypoint used for all other traffic.


Felix

On Fri, 12 Feb 2016, at 12:24, Ramon Makkelie wrote:
i just created a new cloudfoundry deployment for testing purposes
and i can push a application but the the following error

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform
configuration (loggregator endpoint is
wss://loggregator.cf.dev.eden.klm.com:4443).

cf logs trace http://pastebin.com/KkpAJ8x0

doppler/loggeragor logs http://pastebin.com/c8giCvua

deployment manifest http://pastebin.com/XQMfWqDJ

can maby someone point me in the right direction?
i think im missing something


ramonskie
 

my issue was a faulty dns server
there was one dns server that did not responded or responded really slow