-
Notifications
You must be signed in to change notification settings - Fork 67
Various "cf dev" commands report failure even though services appear to be working correctly #255
Comments
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
I tried SSHing into the VM with
From
|
Although I could access https://login.local.pcfdev.io, I could not access https://apps.local.pcfdev.io. The error message displayed is |
Are you able to If so, can you provide the full output of that process? |
Same output as before:
|
Is there anything else I can run to get more detailed logging information? How can I SSH into the instance, give that |
The SSH key is in Given that you're behind an HTTP proxy, your VM won't have internet access unless you follow these instructions. That shouldn't really cause the issue you're seeing though. If you run |
I am not running PCF Dev nested in another VM. I am running it within VirtualBox on the bare hardware of my workstation. I've confirmed that, for the PCF components that do work, it is traversing the corporate proxy correctly. In my particular setup, I have Fiddler installed and acting as a proxy proxy to automatically handle authentication challenges from the corporate proxy. I've seen traffic going in and out of PCF Dev within Fiddler. I will re-run |
Thanks for sending me the debug archive. This appears to be a bug in 0.27.0 where Apps Manager doesn't start if you don't have a working internet connection when you run Can you confirm that you've followed the instructions in the docs to provide PCF Dev with your proxy details? Starting with a working internet connection should let you workaround this issue. |
I followed the instructions here: https://docs.pivotal.io/pcf-dev/proxy.html. As you can see in the debug files, I have the following three system-level environment variables set:
I am running Fiddler and have bound it to all IP addresses on my local machine ( I am pretty sure all this means I did configure the proxy correctly. This script:
runs with the following output (truncated at the end):
After looking at Fiddler, I don't see any requests coming from PCF. However, I do see one strange request that looks like it may be from PCF or the CF CLI:
This of course fails because the proxy doesn't allow a connection to Another question for you: Does the CF CLI look only at user-level environment variables for |
I tried setting both the user-level and system-level environment variables at the same time, but it didn't seem to affect the problem. |
We're working on a follow-up release that will address the error that I found in your logs. Are you able to start 0.26.0 successfully? If so, are you able to |
Yes, I uninstalled 0.27.0 and installed 0.26.0 and everything seems to be working perfectly. I even have internet access from the VM:
|
Fixed in v0.28.0. Thanks for the report! |
Hello, can anyone help me on this. i am trying to start the PCF dev, but running into below issues in windows 10. PS C:\Users\sindh\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\TempState\Downloads> cf dev start -f .\pc Thanks |
Machine information:
Version information:
cf dev version
: PCF Dev version 0.27.0 (CLI: 01c0c2b, OVA: 0.529.0)cf version
: 6.29.0+ff886fa.2017-07-24VirtualBox: 5.1.26
I'm running into a strange situation installing and starting PCF Dev. All below commands were executed in PowerShell as an administrator.
Here is the output from
cf dev start -k
:The strange thing is that I can still access the https://login.local.pcfdev.io website and interact with PCF Dev from
cf
:However, several commands do not work, despite the services apparently running just fine:
I am not sure how to proceed. I've seen some other GitHub issues that indicate I could SSH into the VirtualBox VM, but I haven't been able to locate the credentials to use at the Linux console.
Also, a co-worker is running PCF Dev 0.26.0 and does not experience these issues. Could this be a regression in the latest version?
The text was updated successfully, but these errors were encountered: