Looks like most of your VMs are fine, but one of your etcd VM's agent is unresponsive. Do "bosh cck" and resolve the unresponsive agent by recreating from the last known apply spec. wrote:

I'm pleased to announce the release of the java-buildpack, version 3.3.1. This release contains a new debug framework and ensures that the dependencies contained in the offline buildpack are up to

Hi, as I see this buildpack is for lucid64 stack. PWS now uses cflinuxfs2 stack. This inconsistency can be the source of your problem. Can you verify stack on your local CF using `cf stacks`? Alex

I have the same problem with Stacks. Changing permissions manually to openworld RW don't change a thing. Has anyone else faced such issue? {"timestamp":1445792695.6604235,"message":"run (took

Hi, you need to query UAA API instead of CC API to learn user id. GET /Users?attributes=id&filter=userName eq 'admin' UAA endpoint: $ cat ~/.cf/config.json | jq .UaaEndpoint To create user you

Hi, You can hit the /Users endpoint to create an user in the UAA. You can find more details here https://github.com/cloudfoundry/uaa/blob/master/docs/UAA-APIs.rst#create-a-user-post-users Chris

Hi, I would like to create users using REST API: http://apidocs.cloudfoundry.org/222/users/creating_a_user.html But I don't know how to get a UAA guid of the user to

Krzysztof, Thanks for the follow up. I pushed a test app and I'm seeing the same "503 Service Unavailable" from Maven. Is that what you're seeing? Dan wrote:

Do you have some hello world example to tests in local? A hello world example? Juan Antonio

Amit, I already tried that troubleshooting options, always same error. As you mentioned, I have attached the BOSH VMs and BOSH CCK REPORT. Thanks.

Mike, That sounds good. Happy to retest after that work has been done and confirm it resolves the issue here. Dan

You have an example here with node: https://github.com/jabrena/CloudFoundryLab/blob/master/Node_HelloWorld_ssl2/index.js var ssl = false; if(req.headers['x-forwarded-proto'] === "https"){

I'm actually open to adding commonly-used locales to the rootfs; though that wouldn't help anyone until they're able to upgrade. I'd like to propose that we install the debian package `locales`,

See this link. http://support.run.pivotal.io/entries/82035305-How-do-I-force-my-users-to-use-HTTPS- Dan wrote:

Hi All, I tried to push .net application [using https://github.com/cloudfoundry-community/.net-buildpack] to pivotal CF but is failing with following error. earlier same application used to run

congrats! Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Technology IBM Cloud, Open Technologies email: chrisfer@... twitter: @christo4ferris blog:

Try some of these diagnostics: https://docs.cloudfoundry.org/running/troubleshooting.html#bound-timeout Also, run "bosh vms --details" and "bosh cck --report" and share the outputs.

Actually, sorry for the previous mails. Since, I have started with CF v202 release and it thrown some error so am switched to CF v210. But, again because of some rollback issues we went back with CF

Your message has encountered delivery problems to the following recipient(s): sfpj (Was addressed to sfpj(a)listserve.uwec.edu) Delivery failed The message originator is not a list member in

Hi, Following up onto this thread initiated last year on