search

cloudfoundry / cli

The official command line client for Cloud Foundry
https://docs.cloudfoundry.org/cf-cli
Apache License 2.0
1.75k stars 929 forks source link

6.11.0+ error fetching logs from ER 1.3 #423

Closed wgu-zz closed 9 years ago

wgu-zz commented 9 years ago

Noticed the release log that from 6.11.0 on doppler will be added to the cli config file. Seems it will now be the default URL when fetching app logs?

sgu-home:cf-chatroom sgu$ cf target

API endpoint: https://api.system.10.10.33.11.xip.io (API version: 2.13.0) User: admin Org: system Space: dev sgu-home:cf-chatroom sgu$ cf -v cf version 6.11.0-bba7fcf-2015-04-14T16:45:03+00:00 sgu-home:cf-chatroom sgu$ cf logs riakcs-sgu FAILED Error dialing traffic controller server: websocket: bad handshake. Please ask your Cloud Foundry Operator to check the platform configuration (traffic controller is wss://doppler.system.10.10.33.11.xip.io:443)

The trace log indicated the same connection error.

6.10.0 works just fine.

cf-gitbot commented 9 years ago

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/92989748.

goehmen commented 9 years ago

Yes. This is a bug that we addressed in v6.11.1. Can you upgrade your CLI and confirm that the issue is resolved? thanks

wgu-zz commented 9 years ago

Sorry, just about to reply that 6.11.1 does not work either. Replaced the binary, logout, clean the cli config file and then login. Still the same.

sgu-home:cf-chatroom sgu$ cf logs chatter FAILED Error dialing traffic controller server: websocket: bad handshake. Please ask your Cloud Foundry Operator to check the platform configuration (traffic controller is wss://doppler.system.10.10.33.11.xip.io:443). sgu-home:cf-chatroom sgu$ cf -v cf version 6.11.1-4ef66f6-2015-04-20T21:15:38+00:00

goehmen commented 9 years ago

hmmm....ok. thanks.

Greg Oehmen Cloud Foundry Product Manager 415.205.6596

On Wed, Apr 22, 2015 at 12:20 AM, William Gu notifications@github.com wrote:

Sorry, just about to reply that 6.11.1 does not work either. Replaced the binary, logout, clean the cli config file and then login. Still the same.

sgu-home:cf-chatroom sgu$ cf logs chatter FAILED Error dialing traffic controller server: websocket: bad handshake. Please ask your Cloud Foundry Operator to check the platform configuration (traffic controller is wss://doppler.system.10.10.33.11.xip.io:443). sgu-home:cf-chatroom sgu$ cf -v cf version 6.11.1-4ef66f6-2015-04-20T21:15:38+00:00

— Reply to this email directly or view it on GitHub https://github.com/cloudfoundry/cli/issues/423#issuecomment-95057021.

simonleung8 commented 9 years ago

Seems like the doppler endpoint is not available in the env. Do you also get the same message with cf push or cf app <app_name>?

wgu-zz commented 9 years ago

Yes, I do.

nebhale commented 9 years ago

Guys, this is also demonstrable against PWS at the moment. Should we be rolling the Homebrew Tap back to the v6.10 line?

$: cf push
Using manifest file [REDACTED]/web-servlet-2-application/manifest.yml

Using stack cflinuxfs2...
OK
Updating app web-servlet-2-application in org [REDACTED] / space [REDACTED] as [REDACTED]...
OK

Uploading web-servlet-2-application...
Uploading app files from: [REDACTED]/web-servlet-2-application-1.0.0.BUILD-SNAPSHOT.war
Uploading 429.3K, 29 files
Done uploading               
OK

Stopping app web-servlet-2-application in org [REDACTED] / space [REDACTED] as [REDACTED]...
OK

Warning: error tailing logs
Loggregator endpoint missing from config file
Starting app web-servlet-2-application in org [REDACTED] / space [REDACTED] as [REDACTED]...
$: cf logs web-servlet-2-application --recent
Connected, dumping recent logs for app web-servlet-2-application in org [REDACTED] / space [REDACTED] as [REDACTED]...

FAILED
Error dialing traffic controller server: parse : empty url.
Please ask your Cloud Foundry Operator to check the platform configuration (traffic controller endpoint is ).
simonleung8 commented 9 years ago

@nebhale : Does logging out and back in solve your problem? It seems to be looking for the new doppler endpoint in the config and the field will be populated during cf api or cf login

nebhale commented 9 years ago

@simonleung8 That does seem to solve the problem, but as far as usability goes it's horrible. That logging in again fixes the problem is effectively undiscoverable by normal users.

goehmen commented 9 years ago

We're going to provide a fix in 6.11.2 which we are working on now.

Greg Oehmen Cloud Foundry Product Manager 415.205.6596

On Fri, Apr 24, 2015 at 7:51 AM, Ben Hale notifications@github.com wrote:

@simonleung8 https://github.com/simonleung8 That does seem to solve the problem, but as far as usability goes it's horrible. That logging in again fixes the problem is effectively undiscoverable by normal users.

— Reply to this email directly or view it on GitHub https://github.com/cloudfoundry/cli/issues/423#issuecomment-95953320.

goehmen commented 9 years ago

The CLI team worked through this with the LAMB team. We have a solution that we will be implementing in the next release. Basically, we need to be able to interrogate the CC API and address either the Doppler or the Loggregator endpoint based on interrogation.