cf dev start failed, bosh deploy -d cf succeeded, how to retry?

[Dr Nic Williams]

I'm occasionally seeing cf dev start fail, and this latest time I checked the cf deployment and it seems to have succeeded.

From deploy-cf.log:

==> /Users/drnic/.cfdev/log/deploy-cf.log <==
Task 74 Started  Thu May  2 01:10:14 UTC 2019
Task 74 Finished Thu May  2 01:30:18 UTC 2019
Task 74 Duration 00:20:04
Task 74 done

Succeeded
Setting api endpoint to api.dev.cfdev.sh...
Request error: Get https://api.dev.cfdev.sh/v2/info: EOF

Any Tips on debugging (see #96 for inability to ssh into containers)?

I was unable to "retry" cf dev start to get it to fix this.

$ cf dev start
CF Dev is already running...
$ cf login -a https://api.dev.cfdev.sh --skip-ssl-validation -u user -p pass
API endpoint: https://api.dev.cfdev.sh
FAILED
Error performing request: Get https://api.dev.cfdev.sh/v2/info: EOF

In my other log files I see a lot of (lines are produced more than once per second)

==> /Users/drnic/.cfdev/log/vpnkit.stderr.log <==
vpnkit: [ERROR] Socket.Stream: caught Socket is not connected
vpnkit: [ERROR] Socket.Stream: caught Socket is not connected
vpnkit: [ERROR] Socket.Stream: caught Socket is not connected
vpnkit: [ERROR] Socket.Stream: caught Socket is not connected

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/165757878

The labels on this github issue will be updated when the story is started.

[Anthony Emengo]

Apologies for the poor documentation on this but if you want to restart CF Dev from a clean slate, you should run cf dev stop first.