The steno-prettify tool may be given a try to format timestamps in human readeable dates on the vm itself . See doc I contributed at [1] for sample invocation in-situ on the vm. I haven't tested in a

Hi Matsumi, What information exactly would you like to know about the etcd events? There error message is "Got error while waiting for ETCD events: store request timed". This could be due to several

Would the community release embedding power dns to provide xip.io style impl be appliceable to your contexte and useful [1] ? This relies a DNS delegation though. I haven't tested it myself yet. [1]

Sorry, after looking at our manifests it appears we actually set it to 0 not -1. properties: request_timeout_in_seconds: 0 Then you need to set CC timeout to something else since nginx doesn't

Amit, Here are the results: https://gist.github.com/cholick/b448df07e9e493369d9e The before and after pictures look pretty similar, nothing jumps out as interesting.

Hi Mike, Could you let me know how you set timeout on gorouter to -1? Appreciate your response.

I was reading this thread, I noticed that I have the same problem and I thought that we had a problem in our network. In local I am using development from

Hi Warren and Nino, Let me update our status. Yes, the root cause was the inconsistency of a bulk user id between cc and syslog drain binder due to the bug (a hardcorded id). We confirmed

Hi, I would like to know if exist some REST API to detect if a platform has installed Diego. Reading API from Cloud Controller, I didn't recognize some method to identify Diego in CF

Hi Charles, You said the clue!!! Yesterday, I updated the development and I could deploy on PWS. From environments without Diego, the way to run a Node development is: var localPort =

Oh right I misread it I thought it was avoid application to connect to certain IP..... wrote:

Gwenn, If I'm not wrong Application sec rules are for restricting outbound traffic from application side , no? Ronak

What about https://docs.pivotal.io/pivotalcf/adminguide/app-sec-groups.html ? carlo.ferraris(a)rakuten.com> wrote:

Is there any provision for restricting the source IPs that are allowed to access a certain application (or route)? Or the only way to do this is to place a reverse proxy in front of the gorouter? In

Matt, that's awesome, thanks! Mind trying this? require 'uri' require 'net/http' require 'logger' SYSTEM_DOMAIN = '--CHANGE-ME--' u = URI.parse('http://uaa.' + SYSTEM_DOMAIN + '/login') h =

once the tcp routing work is done with the haproxy approach, you should be able to try mutual ssl using a IP/port. you should be able to test tcp routing with lattice now. however web traffic using a

Does any one have any experience using SSL mutual authentication for an app running on CF? Thanks! Anthony

Amit, Here's a run with the problem manifesting: ... 00248 [200]: ruby 26ms | curl 33ms | nslookup 21ms 00249 [200]: ruby 20ms | curl 32ms | nslookup 14ms 00250 [200]: ruby 18ms | curl 30ms |

best way around it , same as in the story. set the time zone of the UAA can to match DB vm

If you're using the common bosh lite IP of 10.244.0.34, you can also use the more-reliable *.bosh-lite.com