Hi guys, How can I increase the request timeout in CF? I would like to give more time to my app to send a response to the requests before getting a timeout. Should I increase it in the buildpack? If

Hi guys, How can I increase the request timeout in CF? I would like to give more time to my app to send a response to the requests before getting a timeout. Should I increase it in the buildpack? If

- cf logs APPNAME --recent does not show any difference - i created my deployment manually because spiff templates do not work with openstack without neutron so i i update my deployment manifest with

that commit you link to is pretty old (well over a year) and is not the problem between v207 and v214. there is likely some configuration issue. i sent you a response on the other thread you opened

here are some things that should help us troubleshoot: does "cf logs APPNAME --recent" show anything different? how did you create your deployment manifest? how many availability zones do you have in

Jack, For cached buildpacks, it would not be useful to set HTTP proxying. The dependencies are bundled with the buildpack and are loaded via the local file system, not HTTP. Most of the buildpacks

Currently I see that the Java buildpack and the PHP buildpack explicitly mentioned in their doc that they can run behind a Web proxy, by setting the HTTP_PROXY and HTTPS_RPOXY environment variable.

since the upgrade from 207 to 214 i noticed 2 things 1) no more stdout and stderr in the logs/ dir off the app/container someone pointet it out that this is removed in

I think you're talking about two separate things here: If you create a user defined service and bind that to your application [1], the Java build pack should install the agent and configure it to

Thanks Gwenn. I found a link for integrating AppDynamics (agent based monitoring like Wily) with PCF, where its mentioned to create user-defined service and bind it to application, so that AppDynamic

You not should change it, this domain is use only with consul as DNS. Many component rely on it, uaa and so

Hi, I am trying to deploy diego 0.1402.0 into vShpere server to work with CF 210. However the deployment failed when creating job 'etcd' with following error. Error: cannot sync with the cluster

I think the easy way is to use the provided logs system by CF, so deaagent-> metron -> dopler -> Firehose consumer - forwarder -> Willy Will be strange that Willy agent / or server don't provide

I am getting this error while trying to deploy a test app. It fails during staging with this exception: /=================================================/ 2015-08-13 17:33:16.542443

Thanks James for your reply. So you are recommending firehose nozzles for sending logs and metrics to 3rd party application monitoring and logging tools. For product like Wily Introscope (now known

Thank you. Needed to update to make this work. uaac client update useraccount --access_token_validity 315360000

okay so no problem there the only thing now is that there is no streaming logs with the cf logs command from my APP only RTS any ideas there? -- View this message in context:

i wrote back last week, but it looks like it was swallowed and never posted? ---------- Forwarded message ---------- From: James Bayer <jbayer(a)pivotal.io> Date: Fri, Aug 14, 2015 at 6:33

Hi, Can someone help me on my query please? Thanks

i know that onsi and eric have discussed this. i've heard that eric is working on a reply. -- Thank you, James Bayer