it looks like one of the vms is unresponsive. you can try uding bosh cck to recover. Sent from my iPhone

Hi Rafal, Packages are not stored in the database for the V2 API, that table is for experimental V3 support and wouldn't have any rows unless you are pushing apps with the V3 API. Can you tell us

then, after this problem, when i ‘bosh deploy’, another problem came, how can i continue deploy ? Deploying --------- Director task 6259 Started preparing deployment Started preparing

hello everybody, when ‘bosh deploy’ all vms looks well , after a few hours some vms state turn into ‘unknown/unknown’ , like

Try the following: ssh onto the consul VM run "sudo su -" to switch to root run "monit stop consul_agent" run "ps uwax | grep consul" to see if there are any errant consul-related processes, and kill

Hi Amit Sorry if the colors, and bolding disturbs you .. Will refrain from using that. I tried giving the static ip in consul.agent.servers.lan:10.20.0.116. But I get following error in cf-230 ==>

Yes, we do not recommend using HaProxy in production environments because of this downtime issue. I have heard of some HaProxy load balancer solutions using

Hi Dimitar, Thank you for pointing this issue out to us. I've raised a story in the CF Docs tracker to verify and correct this issue: https://www.pivotaltracker.com/story/show/115647925 Thanks

Hi Jim, So, to be clear what we're basically doing is using unicode newline character to fool loggregator (which is looking for \n) into thinking that it isn't a new log event right? Does \u2028

Hi Jim, Thank you for sharing it with us. Could you please share a link to track status of this work? So there are "first class citizen"(Java) and others (Ruby, Python etc)? Is it so rare case that

Hi Mike and Alex, Two things - for Java, we are working toward defining an enhanced metric format that will support transport of Multi Lines. The second is this workaround that David Laing suggested

Hi, According to https://docs.cloudfoundry.org/buildpacks/custom.html#release-script the config_vars section of the release output should be taken into account when starting applications. However

Using the DNS hostname of consul instead of the IP will not work in CF v230. It should work in v231. Open source Cloud Foundry does not guarantee direct upgrades between non-consecutive versions. I

+Added some more details below Sent: Monday, March 14, 2016 10:02 PM To: 'Amit Gupta' <agupta(a)pivotal.io>; Discussions about Cloud Foundry projects and the system overall.

I'll let the Loggregator team respond formally. But, in my conversations with the Loggregator team I think we're basically stuck not sure what the right thing to do is on the client side. How does

Hi All, Since upgrading to v231 were having issues with uaa redirecting to the proper url after authenticating through saml to our ping-federate identity. The normal sequence went: 1. cf login

Ben and team.. this is a major overhaul of an incredibly valuable client library. I know of companies who are already picking this up. The fact this you've built this on Reactor makes it all the more

Hmm... I suppose so. Conversely, by putting them all in one library you've added greater complexity and bloat by potentially including more transitive dependencies by default to use a given component

Hi Amit We are trying to upgrade cf-205 to cf-230. So I have checked out with the commit id of cf-230.yml and I could generate the manifest using the generate_deployment_manifest script for our

Hi guys, Are there any updates about "Multiline Log Entry" issue? How correctly deal with stacktraces? Links to the tracker to read? ---- Alex Prysmakou / Altoros Tel: (617) 841-2121 ext. 5161 | Toll