The cf-release v211 was released on June 4th, 2015 - IMPORTANT: This release removes lucid64 stack, please ensure apps are migrated prior to upgrade - IMPORTANT: If using the postgres

Hello Supraja, Did you delete the service broker with `cf delete-service-broker`? Then you registered the broker again with `cf create-service-broker`? Then you tried to make the service plans

i seem to remember something about app security group logging having an issue with bosh-lite that isn't present when you have a DEA in a VM. i remember something about that. i'll see if dieu

Hello,  as you suggested, I looked deeper in this matter, and I can see that on the DEA VM:  I get the right iptables rules, but I still can not see the logs on /var/log/messages [Im using

Copying contents of notes here. ---- Runtime PMC Meeting 2015-06-02 <https://github.com/cloudfoundry/pmc-notes/blob/master/Runtime/2015-06-02-runtime.md#agenda> Agenda 1. Proposed Runtime

Fix Confirmed, for the record, it was the issue when running ./update and failure to retrieve HM9000 git submodules. --- Armin ranjbar

Replying myself :I i think it was due the fact that something was messed up during updating git sub modules before creating release, recreating to make sure it's ok. --- Armin ranjbar

Hello, when trying to deploy CF, i get this error during build process of HM9000. CF RELEASE : 210+dev.2 , commit hash: c6f46acd bosh-openstack-kvm-ubuntu-trusty-go_agent v2978 Started compiling

I am sorry that I was no help to you 2015-06-05 13:12 GMT+09:00 Guangcai Wang <guangcai.wang(a)gmail.com>:

+1 -- Duncan Johnston-Watt CEO | Cloudsoft Corporation +44 777 190 2653 | @duncanjw Sent from my iPhone -- Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. Registered Office:

He also probably listens for udp4 connections. Have you tried to allow udp4 traffic to ports 3456-3457 and check if loggregator collects the logs after it? -- Lev Berman Altoros - Cloud Foundry

Hi, We had a meeting for the Runtime PMC earlier this week. Notes available here: > https://github.com/cloudfoundry/pmc-notes/blob/master/Runtime/2015-06-02-runtime.md -Dieu

i'm very happy to see this work delivered as the 60 second limit has come up so often as a pain point in the past. great job to all who contributed! -- Thank you, James Bayer

Finally, it works after I changed the configuration related to memory and disk for dea. < disk_mb: 2048 --- 1025c1029 < memory_overcommit_factor: 3 --- 1028c1032 < staging_disk_limit_mb:

We found the loggregator was listening on port 3456 and 3457 with upd6. udp6 0 0 [::]:3457 [::]:* But we can’t use ipv6 in our env. So is there any way to force

debug log sample

On the Password Score feature, I haven't yet received any updates on whether its being used at all. Please let us know if anyone is using the same. Thank you Nick/Steve/Josh for the feedback !! I

Joseph, Double checking after a good night of sleep, my last check was wrong (reviewing the diff, I had checked for presence of jobs properties, and missed at the bottom of the file for the presence

I got the nats message on 'staging.advertise'. It has the enough resource. but it seems not correct. And it also cannot explain the error - Server error, status code: 400, error code: 170001,

There's not currently a way to determine this exactly. As Takeshi suggests the api version is the closest thing, but it does not get bumped every cf-release. -Dieu CF Runtime PM