cf dev start: Failed to deploy services: Failed to deploy PAS: exit status 1

[guicey]

cf dev start: Failed to deploy services: Failed to deploy PAS: exit status 1

[cf-gitbot]

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

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

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

[aemengo]

Are you perhaps running CF Dev on an external hard drive? It's possible that you might be seeing resource constraints because of "not quite" flash storage.

[guicey]

Are you perhaps running CF Dev on an external hard drive? It's possible that you might be seeing resource constraints because of "not quite" flash storage.

I'm running on 1TB SSD from MacBook Pro 2019.

[aemengo]

And you’re repeatedly seeing this issue on subsequent runs of CF Dev? What happens if you do a cf dev stop and then start again?

[guicey]

And you’re repeatedly seeing this issue on subsequent runs of CF Dev? What happens if you do a cf dev stop and then start again?

Yes i did that 3 times and it didn't work probably because of:

Silk-Release IPTables logging not effective in BOSH Lite
When using BOSH Lite, iptables logging between deployed applications on the same diego-cell does not log to /var/log/kern.log. Due to this, the iptables-logger job is unable to read and generate the logging statements in /var/vcap/sys/log/iptables-logger/iptables.log.
Link: https://github.com/cloudfoundry/cf-networking-release/blob/develop/docs/known-issues.md

Should this incompatible silk-release be packaged into extra asset pcfdev-v1.2.0 for PAS 2.4.4 (darwin) while cf dev is using BOSH Lite?

I unpacked pcfdev-v1.2.0-darwin.tgz modified the configuration file by commenting out the iptables-logger job. Repacked it again and started cf dev again. Took me several hours to figure out what was wrong but please repack a compatible silk release into the extra asset cf dev package. If you got cf dev working than it is pretty cool stuff to play with.

[aemengo]

I appreciate the extra digging that you did, but I fail to see how the iptables-logger issue you mentioned would cause CF Dev to crash on startup for just you. cf dev start -f pcfdev-v1.2.0-darwin.tgz routinely works for me (and others) regardless of that logging issue.

[guicey]

@aemengo It works on mine machine is generally not a helpful answer. Can you post the versions of extra assets and particularly the Silk-Release with the IPTables logging you are using. I guess there is a discrepancy accross versions.

[aemengo]

Please consider giving the newest release of CF Dev a try and see if that helps this issue.

New Release

• v0.0.18 (plugin) - https://plugins.cloudfoundry.org/#cfdev
• v1.3.0 (Service Assets) - https://network.pivotal.io/products/pcfdev/#/releases/685614
• v1.3.1 (Service Assets) - https://network.pivotal.io/products/pcfdev#/releases/690049