guillaume, you're right. the CNAME approach won't work if the host header doesn't match the route advertised from the CCs. -- Thank you, James Bayer

James, would'nt a second domain (even if resolving to the same IP than the primary domain, thanks to a CNAME), still be mentionned in http requests in their original "Host:", header and would

Hi There! On behalf of the CF Core Services team I am pleased to announce v20 of cf-mysql-release <https://github.com/cloudfoundry/cf-mysql-release>. -- cf-mysql-release

There's a known issue that occurs when an app starts and fails in rapid succession and results in the log entries being missed. If you add a couple second pause into the app, it will give the system

I'm trying to push an executable JAR to a bosh-lite instance, on the logs I see CF trying many times to restart the app and eventually fail. I can't find out why the app crashes as there is no app

Loggregator listens for the "old"[1], loggregator message format on 3456, and the newer dropsonde messages on 3457. We're actively working to mark the old loggregatorlib as deprecated. "Do you know

Hello, I post some more info: Kernel logging is enabled because inside the DEA, i can see: cat /etc/rsyslog.conf [...] $IncludeConfig /etc/rsyslog.d/*.conf cat

I can't open the Chinese doc website http://cndocs.cloudfoundry.com.Is this website closed?Is there any other substitute?

it appears as though the cloud controller only supports advertising a single domain: https://github.com/cloudfoundry/cf-release/blob/master/jobs/cloud_controller_ng/spec#L62-L63 i wonder if a CNAME

Hi there, how can I add a second domain to my API endpoint? I know how to add a shared domain for apps. But looking at the router /routes, the api.<domain> maps directly to the cloudcontroller. How

Yes he also listens to udp4. By allowing udp 3456 and 3457, it worked. Do you know why 3457 is used when the incoming listening port for loggregator is specified as 3456? Sent from my iPhone

Yes, I do recall that the feature did not work on bosh-lite but that was when kernel logging was disabled on the trusty stemcell. Michael, could you send the json for the application security group

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